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 2002/02/04 21:22:33 UTC

DO NOT REPLY [Bug 6231] New: - DocumentImpl should use createEvent() to create mutation events, rather than just newing them

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

DocumentImpl should use createEvent() to create mutation events, rather than just newing them

           Summary: DocumentImpl should use createEvent() to create mutation
                    events, rather than just newing them
           Product: Xerces2-J
           Version: 2.0.0 [beta 4]
          Platform: All
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: DOM
        AssignedTo: xerces-j-dev@xml.apache.org
        ReportedBy: david.robertson@gefedmonton.ge.com


Our understanding of the DOM Events API is that the createEvent() method in the 
DocumentEvent interface can be used as a hook to create derived event classes.

Grep for "new MutationEvent" in DocumentImpl - should these be replaced with 
calls to createEvent()?

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