[
https://issues.apache.org/jira/browse/XERCESC-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513277
]
Boris Kolpackov commented on XERCESC-1722:
------------------------------------------
Hi Alberto,
Don't you think that because when the document is cloned all its elements are
being cloned, the cloning event should
be triggered on all elements? What happens when I make a deep (i.e., with
sub-elements) clone of an element? The fact that the even is triggered only on
the top-level entity that is being cloned even though the contained elements
are being cloned as well appears very counter-intuitive to me (this "bug" was
first mentioned to me on our mailing list so I am not alone thinking this is
strange). Also if we consider what happens when we release the document (which
triggers release of all its elements), I am sure the release events are
triggered on all sub-elements.
Regarding signature of the handle function: the test is for the current SVN
(aka 3.0.0) where the signature of that function has (rightfully) changed to
strip the second const.
thanks,
-boris
> DOMUserDataHandler events are not triggered when cloning documents
> ------------------------------------------------------------------
>
> Key: XERCESC-1722
> URL: https://issues.apache.org/jira/browse/XERCESC-1722
> Project: Xerces-C++
> Issue Type: Bug
> Components: DOM
> Affects Versions: Nightly build (please specify the date)
> Environment: any
> Reporter: Boris Kolpackov
> Priority: Critical
> Attachments: clone.cxx
>
>
> The attached test case shows that the data handler "clone" event is not
> triggered when the complete document is being cloned. This test case is for
> the 3.0.0 branch and expects a file named "test.xml" to be present in the
> working directory. The contents of
> test.xml are no important as long as it is a valid XML file.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
