Subject: Re: [xsl] XSLT 2.0 has arrived From: Abel Braaksma <abel.online@xxxxxxxxx> Date: Wed, 24 Jan 2007 10:23:05 +0100 |
In reality, it's usually something like
$ java -jar saxon8.jar source.xml style.xsl Unable to access jarfile saxon8.jar $ java -jar /User/elharo/lib/saxon8.jar source.xml style.xsl Unable to access jarfile saxon8.jar $ java -jar /Users/elharo/lib/saxon8.jar source.xml style.xsl ...
Of course, you could put saxon8.jar into your jre/lib/ext directory, but which one? There are usually several. You can also pretty much guarantee that after you do that, you're going to break some other program that conflicts with saxon.
Can I eventually make this work? Yes?
Is it a pain in the ass? Yes.
Should I have to deal with this? No.
Is this far more complex than a traditonal Windows or Unix executable? You better believe it.
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] XSLT 2.0 has arrived, Jay Bryant | Thread | Re: [xsl] XSLT 2.0 has arrived, Elliotte Harold |
Re: [xsl] Output multiple files wit, George Cristian Bina | Date | Re: [xsl] empty namespace declarati, David Carlisle |
Month |