Yash Talwar wrote:
Hi Elliotte, Prior to release 2.7, xalan.jar file included the code for serializer. In release 2.7, the serializer code is bundled in serializer.jar file. So, when you used older versions, you included xalan.jar file in the classpath. Xalan code make use of serializer code to output the result tree. I hope this answer your question.
Not really. I'm not using the Serializer in my own code. I'm not outputting a result tree (at least not through Serializer). And yet I can't actually run a non-serialized transform without having serializer.jar in my classpath. The separation doesn't seem to be as clean as it should be. I'd like a xalan.jar that can run without having an extra jar file in the classpath. Two jar files is more to distribute, version, and screw up than one jar file. the fewer I can work with the better.
Looking at the code, it doesn't seem like serializer.jar is really a necessary component of the basic parts of Xalan I'm using, but if it is; then they should be one jar file, not two. It seems to me that the cut between the two was made in the wrong place, or not made thoroughly enough if I can't use Xalan without pulling in serializer.jar too.
-- Elliotte Rusty Harold [EMAIL PROTECTED] XML in a Nutshell 3rd Edition Just Published! http://www.cafeconleche.org/books/xian3/ http://www.amazon.com/exec/obidos/ISBN=0596007647/cafeaulaitA/ref=nosim --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
