The following issue has been updated:
Updater: Michael Glavassevich (mailto:[EMAIL PROTECTED])
Date: Fri, 23 Apr 2004 8:46 AM
Changes:
description changed from 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 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
environment changed from Operating System: All
Platform: All to Operating System: All
Platform: All
priority changed to Blocker
Component changed to XInclude 1.0
Component changed from Other
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.apache.org/jira/browse/XERCESJ-909?page=history
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/XERCESJ-909
Here is an overview of the issue:
---------------------------------------------------------------------
Key: XERCESJ-909
Summary: XInclude processor treats malformed bytes sequences as resource errors.
Type: Bug
Status: Resolved
Priority: Blocker
Resolution: FIXED
Project: Xerces2-J
Components:
XInclude 1.0
Versions:
2.6.2
Assignee: Michael Glavassevich
Reporter: Michael Glavassevich
Created: Wed, 3 Mar 2004 11:20 PM
Updated: Fri, 23 Apr 2004 8:46 AM
Environment: Operating System: All
Platform: All
Description:
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
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
