[
https://issues.apache.org/jira/browse/XERCESJ-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mukul Gandhi resolved XERCESJ-1762.
-----------------------------------
Resolution: Fixed
I'm resolving this issue as fixed. The fix for this were committed with
following XercesJ svn commits,
svn id 1915327 : on xercesj dev repos trunk
svn id 1915328, 1915329 : on xercesj dev repos branch xml-schema-1.1-dev
> Implementation for XML DOM documents, a new method 'isEqualNodeWithQName'
> similar to 'isEqualNode' to compare two XML element nodes
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: XERCESJ-1762
> URL: https://issues.apache.org/jira/browse/XERCESJ-1762
> Project: Xerces2-J
> Issue Type: New Feature
> Components: DOM (Level 3 Core)
> Affects Versions: 2.12.2
> Reporter: Mukul Gandhi
> Assignee: Mukul Gandhi
> Priority: Major
> Fix For: 2.12.3
>
>
> There's a need for XalanJ's XPath 3.1 fn:deep-equal's method implementation,
> to have XercesJ's java class org.apache.xerces.dom.ElementImpl provide a new
> method (with name like 'isEqualNodeWithQName'), that can check equality of
> two XML element nodes only on following criteria : localName and namespaceUri.
> The XML DOM standard node comparison method 'isEqualNode' does few extra
> checks wrt node's name (majorly, that XML node's nodeName i.e
> prefix:localName and also prefix have to be same for two equal XML element
> nodes) that is not suitable for what XPath 3.1 fn:deep-equal method requires.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
