Bug 49692 - xmlsec 1.4.3 not compatible with xmlbeans 2.4.0
Summary: xmlsec 1.4.3 not compatible with xmlbeans 2.4.0
Status: RESOLVED FIXED
Alias: None
Product: Security - Now in JIRA
Classification: Unclassified
Component: Encryption (show other bugs)
Version: Java 1.4.2
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: XML Security Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-03 06:23 UTC by coheigea
Modified: 2010-08-03 06:36 UTC (History)
0 users


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description coheigea 2010-08-03 06:23:21 UTC 
See this bug for details:

https://issues.apache.org/jira/browse/WSS-235

IdResolver.java was refactored from release xmlsec/1.3.0 to xmlsec/1.4.3.

Symptoms:
java.lang.NullPointerException
    at org.apache.xml.security.utils.IdResolver.isElement(Unknown Source)
    at org.apache.xml.security.utils.IdResolver.getEl(Unknown Source)
    at org.apache.xml.security.utils.IdResolver.getElementBySearching(Unknown Source)
    at org.apache.xml.security.utils.IdResolver.getElementById(Unknown Source)
    at org.apache.xml.security.utils.resolver.implementations.ResolverFragment.engineResolve(Unknown Source)
    at org.apache.xml.security.utils.resolver.ResourceResolver.resolve(Unknown Source)

Problem:
Under certain circumstances, the ID attribute of an XML node in the XMLBeans DOM implementation is treated as !nodeCanHavePrefixUri