You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-dev@xerces.apache.org by bu...@apache.org on 2002/07/12 15:14:02 UTC

DO NOT REPLY [Bug 10732] - JAXP1.1

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

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10732

JAXP1.1





------- Additional Comments From keshlam@us.ibm.com  2002-07-12 13:14 -------
This appears to be a usage question, not a bug report...

Actually, I'm surprised the output is as good as it is. Last I looked, the 
.toString methods were provided as a debugging tool, not as a serious XML 
generator. If you want the latter, you should probably be looking at the 
serializer classes.

I don't know whether the serializers have a mode that will suppress the 
conversion of & to &amp; (which would be incorrect XML, by the way). An XSLT 
processor can do this since it sometimes needs to "hand-assemble" XML syntax or 
generate non-XML output, so using Xalan as your serializer might be worth 
trying.

---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org