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=26506>.
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=26506

ignorableWhitespace is broken for XML schemas

           Summary: ignorableWhitespace is broken for XML schemas
           Product: Xerces2-J
           Version: 2.6.0
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Major
          Priority: Other
         Component: XML Schema Structures
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]


When validating against an XML schema, whitespace in element content is returned by 
calling org.xml.sax.ContentHandler.characters() instead of 
org.xml.sax.ContentHandler.ignorableWhitespace().

This bug has been reported before (e.g., 13543, 19475, probably others), but so far 
the 
Xerces developers have refused to fix it.  I'm resubmitting it in the hopes that 
somebody 
will see the forest for the trees here.

Certain developers have argued in the past that there are deficiencies in the XML 
Schema or Infoset or DOM specs that preclude the parser from recognizing ignorable 
whitespace as such.  Others have argued that providing whitespace to the application 
through ignorableWhitespace() somehow does not constitute passing the characters to 
the application (?!).

This is hair-splitting.  The *intent* of element-only content, from XML 1.0 thru XML 
schemas, is indisputably clear: the point of the element-only content model is to be 
able 
to work with information as a data structure, i.e., independent of particular 
formatting.  
Returning insignificant whitespace as text significantly breaks this model.  But for 
applications that are interested in such information, there's always the 
ignorableWhitespace() method.  So there's really nothing lost here.

*Please* fix this!

Thanks, -Greg

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to