In the past I've merged the serizlizers of Xalan-J interpretive and XSLTC
into one package (org.apache.xml.serializer). It was a lot more than just
moving code into that package.
The state of affairs is that this package does not depend on either Xalan-J
interpretive or on XSLTC. Both serializers did depend on each of their
respective clients before the merge.
Unfortunately there are dependancies in the other direction. Xalan-J
interpretive depends on this particular serializer package, as does XSLTC.
If you want to plug in your own class that implements ContentHandler you
can do so by modifying a property in one of the serializers
output_xxx.properties files (xxx is one of html,text or xml). But you
don't want the serializer at all.
This sounds good to me, but I'm not aware of any official serializer
interface that a serializer should implement, or of any vendor neutral way
to load such a serializer. If there were a vendor neutral interface we
could have a weak reference, like a String holding a class name, to the
current serializer.
Suggestions?
Brian Minchau
XSLT Development, IBM Toronto
e-mail: [EMAIL PROTECTED]
"The voices in your head are so loud that even I can hear them."
Elliotte Rusty
Harold To: [EMAIL PROTECTED]
<[EMAIL PROTECTED] cc:
nc.edu> Subject: Modular Xalan
10/20/2003 10:16
AM
Please respond to
xalan-dev
Is it possible to cut down the size of the Xalan Jar archive by
removing pieces? In particular I don't need the serializer package.
Will anything else break if I pull it out? Is there anything else I
might be able to get rid of if I just need a basic TrAX
implementation?
--
Elliotte Rusty Harold
[EMAIL PROTECTED]
Processing XML with Java (Addison-Wesley, 2002)
http://www.cafeconleche.org/books/xmljava
http://www.amazon.com/exec/obidos/ISBN%3D0201771861/cafeaulaitA
