[ http://nagoya.apache.org/jira/browse/XERCESC-620?page=history ]
Alberto Massari resolved XERCESC-620:
-------------------------------------
Assign To: (was: Xerces-C Developers Mailing List)
Resolution: Fixed
Fix is in CVS. Please verify.
Alberto
> On NODE_DELETED the UserData should be released only after all Handlers have
> been notified
> ------------------------------------------------------------------------------------------
>
> Key: XERCESC-620
> URL: http://nagoya.apache.org/jira/browse/XERCESC-620
> Project: Xerces-C++
> Type: Bug
> Components: DOM
> Versions: 2.0.0
> Environment: Operating System: All
> Platform: All
> Reporter: Thomas Blatter
>
> Actually DOMDocumentImpl::callUserDataHandlers removes the UserData
> immediately
> after the UserDataHandler was notified.
> In my opinion it would be better to release the UserData only after all
> Handlers
> have been notified: in my case it can happen that one 'key' of UserData knows
> about another key. In the actual situation on NODE_DELETED notification i
> can't
> safely access other keys anymore.
> I know this can be a hairy issue, and unfortunately up until now the DOM
> Level 3
> Core doesn't specify anything about it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.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]
