You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@xerces.apache.org by "Alberto Massari (JIRA)" <xe...@xml.apache.org> on 2007/07/18 10:57:04 UTC
[jira] Reopened: (XERCESC-1722) DOMUserDataHandler events are not
triggered when cloning documents
[ https://issues.apache.org/jira/browse/XERCESC-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alberto Massari reopened XERCESC-1722:
--------------------------------------
Assignee: Alberto Massari
Yes, I think you are right; when cloning a DOMElement the notifications are sent for all the children, so I guess this is what the DOMDocument should do too.
As for the 'const' in the DOMUserDataHandler interface, the only change that has been done in 3.0 is the removal of the 'const' qualifier from the DOMNode* for the destination node, while the key is still a 'const XMLCh* const'
Alberto
> 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
> Assignee: Alberto Massari
> 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: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org