Elliottee,
SERIALIZER DOES NOT DEPEND ON XALAN
===================================
In previous releases the code to do the serialization of the output
result tree was in the same jar as the code to do the XSL transformation,
in xalan.jar. That code was pulled out of xalan.jar and put into
serializer.jar. Its package, org.apache.xml.serializer and its
documented public APIs have not changed.
However, between 2.6 and 2.7 the dependancies in the serializer
code in the other direction, namely on the rest of Xalan were cut.
In order to cut that dependancy an new package was introduced,
org.apache.xml.serializer.utils, which is in serializer.jar but
is internal code with no public APIs.
XALAN DEPENDS ON SERIALIZER
===========================
Unfortunately there is no standard Java API for serialization like
there is for XSL transformation (JAXP), so xalan.jar has dependancies
on code in serializer.jar.
The dependancies of Xalan on the serialization code are the same as
they were before. You just see that dependancy explicitly now that
the serializer.jar exists. Perhaps the code in Xalan can be reworked to
not load any serializer classes if serialization code is never used
at runtime. This could be a JIRA feature.
USING STAND ALONE SERIALIZER
============================
serializer.jar can be used on its own through its public,
documented APIs without needing xalan.jar at all. See the Javadoc APIs
for the org.apache.xml.serializer package at:
http://xml.apache.org/xalan-j/apidocs/index.html
The Javadoc API of the class
org.apache.xml.serializer.Serializer
is a good place to start. It describes how to create and use a
serializer.
- Brian
- - - - - - - - - - - - - - - - - - - -
Brian Minchau
XSLT Development, IBM Toronto
e-mail: [EMAIL PROTECTED]
Elliotte Harold
<[EMAIL PROTECTED]
nc.edu> To
Xalan-dev
08/18/2005 08:54 <[email protected]>
AM cc
Subject
Please respond to Dependence on Serailizer
xalan-dev
I replaced my old 2.6.2 xalan.jar with the new 2.7.0 xalan.jar and
everything promptly broke. The reason is that I didn't have
serializer.jar in my classpath. Easy enough to fix, but the next
question is why I need this? i.e. what depends on serializer.jar, and
why should anything so depend? I am not invoking any of the Serializer
methods directly in my code. Probably relevant is that I'm using a
SAXSource and a SAXResult for the transforms launched via TrAX. (I am
not using StreamSource or StreamResult.)
I need to investigate further and work through the Xalan source code to
figure out what's going on. However in the meantime does this sound
familiar to anyone? Can anyone explain why I need serializer.jar in my
class path? is there any chance the bundles can be reorganized so this
is no longer necessary?
-- 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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
