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=24278>. 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=24278 Incorrect SAXException about bad integral value of a character to be written out. ------- Additional Comments From [EMAIL PROTECTED] 2004-06-09 08:02 ------- The patch for bug 29234 solves my problem too. I agree that toStream should be responsible for keeping its internal state consistent, so you can disregard my patch for this issue. However, I still think it should be of some concern that the serializers init method (called by setOutputFormat) doesn't seem to be called with XSLTC. There is a lot other stuff than just the "m_maxCharacter = Encodings.getLastPrintable(encoding)" going on there, and the method documentation states that init "must be called before calling any of the serialize methods". So this might be the place to look if XSLTC behaviour is different from Xalan in other stream serialization issues. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
