Re: XSLT 2.0 has arrived
actually I'm rather surprised by the comment that the interface is
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-[expletive deleted]-lutely.
Just maybe this will finally be addressed in Java 7 in 2008. I'm not holding my breath.
-- o;?Elliotte Rusty Harold elharo@xxxxxxxxxxxxxxx Java I/O 2nd Edition Just Published! http://www.cafeaulait.org/books/javaio2/ http://www.amazon.com/exec/obidos/ISBN=0596527500/ref=nosim/cafeaulaitA/
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format