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=27422>. 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=27422 XInclude processor treats malformed bytes sequences as resource errors. Summary: XInclude processor treats malformed bytes sequences as resource errors. Product: Xerces2-J Version: 2.6.2 Platform: All OS/Version: All Status: NEW Severity: Major Priority: Other Component: Other AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] While parsing a resource at an include location (both parse=xml and parse=text), the XInclude processor is unable to detect whether the resource it was parsing contained malformed byte sequences [1]. This is because the IOException thrown by the Reader does not provide enough information to determine the cause of the exception. It may very well have been something else such as not being able to open an input stream. Instead of reporting a fatal error, the processor treats it as a resource error and then looks for a fallback. If a fallback exists the resulting stream will be malformed. See Bug #27083, it's somewhat related to this problem. Although we cannot change the behaviour of Java's readers, we should at least catch malformed byte sequences with our own UTF8Reader and ASCIIReader and report them as with other well-formedness violations. [1] http://www.w3.org/TR/2004/REC-xml-20040204/#charencoding --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
