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=13282>. 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=13282 Xerces2-J 2.2.0 make tomcat 4.1.12 failed at init ------- Additional Comments From [EMAIL PROTECTED] 2002-11-19 16:22 ------- I've just attached a couple of items; one is a stand-alone test case to replicate the problem and the other is a potential fix. I think that the problem might be down to xerces talking to a particular type of input stream. The behaviour shows up if the input stream performs partial reads (eg you ask it to fill in 20 bytes, it actually only fills in 15 and tells you so). This doesn't mean that there's no more data available, just that you have to call read() again to get the rest of it. In this case I think that the parser is treating it as the end of the stream and thinking the comment has finished before it actually has done. The test case uses a custom ChunkyInputStream to demonstrate this behaviour, but I've seen it with a java.util.zip.ZipInputStream as well. Hope this helps! T --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
