The following issue has been updated:
Updater: nddelima (mailto:nddelima@xxxxxxxxxx)
Date: Thu, 15 Apr 2004 8:40 AM
Comment:
Patch to override cloneNode in PSVIDocumentImpl. If you see similar problems
with importNode or adoptNode, can you please post a test case?
Changes:
Attachment changed to PSVIDocumentImpl.java.diff
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.apache.org/jira/browse/XERCESJ-923?page=history
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/XERCESJ-923
Here is an overview of the issue:
---------------------------------------------------------------------
Key: XERCESJ-923
Summary: PSVIDocumentImpl is not returned consistently from DOM
implementation when activated
Type: Bug
Status: Open
Project: Xerces2-J
Components:
DOM
Versions:
2.6.2
Assignee: Xerces-J Developers Mailing List
Reporter: Patrick Decker
Created: Mon, 22 Mar 2004 1:23 PM
Updated: Thu, 15 Apr 2004 8:40 AM
Environment: Operating System: All
Platform: All
Description:
After replacing the document implementation by PSVIDocumentImpl via the
DOMParser property "http://apache.org/xml/properties/dom/document-class-name",
PSVIDocumentImpl is not returned from everywhere in the DOM implementation.
E.g. calling cloneNode() in a PSVIDocumentImpl instance falls back to
DocumentImpl.cloneNode() which returns a new DocumentImpl() instance. Instead
it
should better return a new PSVIDocumentImpl() instance. Possible fix would be
to
override cloneNode() and importDocument() in PSVIDocumentImpl accordingly.
adoptNode() might has to be changed, too.
There might be other places in implementation which I could have missed.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.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
|