[
https://issues.apache.org/jira/browse/CXF-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sidhartha Priye updated CXF-2725:
---------------------------------
Environment: Websphere 6.1, CXF 2.2.6 OR 2.2.7-snapshot, OpenSAML
libraries, Spring 2.5.6 libraries, JAX WS Client (was: Websphere 6.1, CXF
2.0-incubator, OpenSAML libraries, Spring 2.0.4 libraries, JAX WS Client )
Affects Version/s: (was: 2.0.12)
2.2.6
After discussions with OpenSAML folks, it appears that CXF is using a DOMParser
which is not namespace-aware and thus when the OpenSAML libraries try to
unmarshall the SAML token in the SOAP Header, it runs into a local part of the
namespace to be null. As per Scott Cantor of OpenSAML, the DOMparser could be
using a Level 1.0 parser instead of DOM Level 2.0 or 3.0.
So essentially whatever is creating the SOAPHeader DOM is not namespace-aware.
I tried with Dan's fix using 2.2.7-snapshot
http://github.com/apache/cxf/commit/6cadc8e0a238c3ec2037bd2c856d2de0574db48d
and it still did not work. So far I have tried with cxf-2.0-incubator, cxf2.2.6
and cxf2.2.7-snapshot.
> "local part cannot be "null" when creating a QName"
> ---------------------------------------------------
>
> Key: CXF-2725
> URL: https://issues.apache.org/jira/browse/CXF-2725
> Project: CXF
> Issue Type: Bug
> Components: JAXB Databinding
> Affects Versions: 2.2.6
> Environment: Websphere 6.1, CXF 2.2.6 OR 2.2.7-snapshot, OpenSAML
> libraries, Spring 2.5.6 libraries, JAX WS Client
> Reporter: Sidhartha Priye
> Priority: Critical
>
> The entire discussion on this issue can be read here
> http://old.nabble.com/local-part-cannot-be-%22null%22-when-creating-a-QName-td27714287.html#a27872480
> On Dan's suggestion, I am entering this track item as he mentioned he will
> take a shot at it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
