David Carlisle wrote:
actually I'm rather surprised by the comment that the interface is
difficult, there are pros and cons of using any system if course, but
a command line of
java -jar saxon8.jar source.xml style.xsl
That's still more complex than "xsltproc style.xsl source.xml" and in
practice you have to do quite a bit more than that. You can't rely on
having saxon8.jar in the current working directory, nor should you have
to. 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.
Does this cause massive problems for everyone using Java from beginners
just learning to experts trying to set up application servers?
Abso-fucking-lutely.
Just maybe this will finally be addressed in Java 7 in 2008. I'm not
holding my breath.
--
Elliotte Rusty Harold elharo(_at_)metalab(_dot_)unc(_dot_)edu
Java I/O 2nd Edition Just Published!
http://www.cafeaulait.org/books/javaio2/
http://www.amazon.com/exec/obidos/ISBN=0596527500/ref=nosim/cafeaulaitA/
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--