DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=29651>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=29651

Xalan's Serailizer should have its own message file.





------- Additional Comments From [EMAIL PROTECTED]  2004-08-18 17:18 -------
Please ignore earlier attachments except for the most recent ones: 
12470 - a sample MANIFEST.SERIALZIZER file
12471 - a patch that only move the serializer messages into the serializer
12472 - a patch that moves an interface from DOM2DTM to TreeWalker
12473 - a patch to temporarily add a build target of serializer.jar to build.xml

For the moment the MANIFEST.SERIALIZER is not used, so 12470 is not of great 
interest.  12471 is the key one, and when it is applied so should 12473.

12472 is some code clean up of an interface that ought to be in TreeWalker, 
however in the long run the serializer might drop the implementation of the
org.apache.xml.dtm.ref.dom2dtm.DOM2DTM.CharacterNodeHandler interface. Whether 
the interface is in org.apache.xml.dtm.ref.dom2dtm.DOM2DTM.CharacterNodeHandler 
or in org.apache.xml.utils.TreeWalker.CharacterNodeHandler doesn't matter so 
much, the key sore point here is that the serializer has dependancies on 
org.apache.xml.util package.  As the serializer moves into its own build target 
we need to cut dependancies on this package for "packaging" purposes.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to