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 Michael Glavassevich <mr...@ca.ibm.com> on 2011/08/05 20:08:59 UTC

Re: DOM mutation events

Hi Vlad,

Xerces implemented what was required by the DOM Level 2 Events
specification. I've never heard of DocumentObserver, but can tell you that
there are currently no plans to make enhancements above what is specified
by the standard.

Thanks.

Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org

Vlad Arkhipov <ar...@dc.baikal.ru> wrote on 07/22/2011 08:23:25 AM:

> Using of DOM mutation events often leads to enormous performance issues
> (because events for not owned nodes are not dispatched to the document,
> the only way to track these changes is to add a listener to every node
> in the document). Also they are not very convenient to use in Java code.
> Are there any plans to provide a simple interface to track DOM
> mutations? There are notification methods in CoreDocumentImpl class but
> all of them are with package-level modifier. These methods seem to be
> good candidates for some interface like DocumentObserver.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
> For additional commands, e-mail: j-dev-help@xerces.apache.org