[
https://issues.apache.org/jira/browse/XERCESJ-1345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ludger Bünger updated XERCESJ-1345:
-----------------------------------
Attachment: Xerces-Eventlistener-Count-patch2.txt
Since the Xerces repository evolved since I provided the patch, the first patch
does not merge anymore without conflicts.
So I herewith provide an updated functionally equivalent patch solving the
merge conflicts of the older patch.
It would be nice if this issue could be solved soon.
> Listener Count datastructure in DocumentImpl should be a document variable
> and not static.
> ------------------------------------------------------------------------------------------
>
> Key: XERCESJ-1345
> URL: https://issues.apache.org/jira/browse/XERCESJ-1345
> Project: Xerces2-J
> Issue Type: Bug
> Components: DOM (Level 2 Events)
> Affects Versions: 2.9.1
> Reporter: Ludger Bünger
> Assignee: Michael Glavassevich
> Attachments: Xerces-Eventlistener-Count-patch.txt,
> Xerces-Eventlistener-Count-patch2.txt
>
>
> The listener count datastructure is currently a static global hashtable.
> This has the disadvantage of not being thread-safe even across otherwise
> totally independent document instances since each uses the same static
> hashtable to keep track of the number of event listeners registered upon the
> document.
> A second effect of this is:
> Deserializing a document with listeners registered upon it in a freshly
> created virtual machine (with a fresh static listener table having no
> listener count data inside) causes the document to believe no event listeners
> are registered upon it and thus not causing dom events to be fired even
> though listeners are registered.
> Thus serialisation/deserialisation of documents having listeners registered
> upon them is factually broken since the very first implementation of event
> listeners using the static listener counters (which is if I did not get it
> wrong since event listeners have been implemented in xerces).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
