You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-dev@xerces.apache.org by bu...@apache.org on 2001/11/24 03:43:02 UTC

DO NOT REPLY [Bug 5058] New: - Documentation of XMLDTDHandler.start/endEntity incorrect

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

Documentation of XMLDTDHandler.start/endEntity incorrect

           Summary: Documentation of XMLDTDHandler.start/endEntity incorrect
           Product: Xerces2-J
           Version: 2.0.0 [beta 2]
          Platform: Other
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: XNI
        AssignedTo: xerces-j-dev@xml.apache.org
        ReportedBy: jjc@jclark.com


(This is beta3, but Bugzilla doesn't recognize that)

org.apache.xerces.xni.XMLDTDHandler.start/endEntity has a note

     * <p>
     * <strong>Note:</strong> Since the DTD is an entity, the handler
     * will be notified of the end of the DTD entity by calling the
     * endEntity method with the entity name "[dtd]" <em>after</em> calling
     * the endDTD method.

This should be deleted. A DTD is not an entity it potentially has both an 
internal subset and an external subset.  The methods should get called as 
follows:

startDTD()
calls for internal subset
startEntity("[dtd]")
calls for external subset
endEntity("[dtd]")
endDTD()

Fortunately this is what Xerces already appears to do.

---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org