You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Sidhartha Priye (JIRA)" <ji...@apache.org> on 2010/03/20 17:17:27 UTC
[jira] Created: (CXF-2725) "local part cannot be "null" when
creating a QName"
"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.0.12
Environment: Websphere 6.1, CXF 2.0-incubator, OpenSAML libraries, Spring 2.0.4 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.
[jira] Commented: (CXF-2725) "local part cannot be "null" when
creating a QName"
Posted by "Sidhartha Priye (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848691#action_12848691 ]
Sidhartha Priye commented on CXF-2725:
--------------------------------------
Dan,
I am just curious what was the issue that was causing this and what did you fix. Should I look for this in the release notes.
thanks
Sid
> "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
> Assignee: Daniel Kulp
> Priority: Critical
> Fix For: 2.2.7
>
> Attachments: bpm-servicesCXF.zip, SpringClientWithSAMLToken.zip
>
>
> 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.
[jira] Commented: (CXF-2725) "local part cannot be "null" when
creating a QName"
Posted by "Sidhartha Priye (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848524#action_12848524 ]
Sidhartha Priye commented on CXF-2725:
--------------------------------------
I got this..Some kind of version mismatch
---- Begin backtrace for Nested Throwables
java.lang.VerifyError: org/w3c/dom/Node.setUserData(Ljava/lang/String;Ljava/lang/Object;Lorg/w3c/dom/UserDataHandler;)Ljava/lang/Object;
at org.apache.cxf.staxutils.StaxUtils.addLocation(StaxUtils.java:951)
at org.apache.cxf.staxutils.StaxUtils.startElement(StaxUtils.java:809)
at org.apache.cxf.staxutils.StaxUtils.readDocElements(StaxUtils.java:878)
at org.apache.cxf.staxutils.StaxUtils.read(StaxUtils.java:765)
at org.apache.cxf.wsdl11.WSDLManagerImpl.loadDefinition(WSDLManagerImpl.java:219)
at org.apache.cxf.wsdl11.WSDLManagerImpl.getDefinition(WSDLManagerImpl.java:179)
at org.apache.cxf.wsdl11.WSDLServiceFactory.<init>(WSDLServiceFactory.java:91)
at org.apache.cxf.jaxws.ServiceImpl.initializePorts(ServiceImpl.java:205)
at org.apache.cxf.jaxws.ServiceImpl.<init>(ServiceImpl.java:148)
at org.apache.cxf.jaxws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:65)
at javax.xml.ws.Service.<init>(Service.java:36)
at javax.xml.ws.Service.create(Service.java:116)
at com.syscom.hsc.security.saml.soap.SpringWSClient.invokeWebService(SpringWSClient.java:42)
I have the stax2-api-3.0.1 and woodstox jars in my web-inf/lib. Not sure if they are JDK 6 compliant only. Do I need to take them out?
thanks
Sid
> "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
> Attachments: bpm-servicesCXF.zip, SpringClientWithSAMLToken.zip
>
>
> 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.
[jira] Commented: (CXF-2725) "local part cannot be "null" when
creating a QName"
Posted by "Sidhartha Priye (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848544#action_12848544 ]
Sidhartha Priye commented on CXF-2725:
--------------------------------------
The class "org/w3c/dom/UserDataHandler" is in xmlbeans-2.0.4.jar. The version mismatch went away when I restarted the server.
Now I am seeing similar behaviour that I have seen in the past with the original issue. Here are some tests with SAAJ libraries.
1. Do not endorse the saaj-api and saaj-impl libraries, I get the following error - HIERARCHY_REQUEST_ERR: An attempt was made to insert a node where it is not permitted.
2. If I endorse saaj-impl1.3.2 and saaj-api1.3 jars on WAS 6.1,
I get the following error -
[Servlet Error]-[com.sun.xml.messaging.saaj.soap.SOAPDocumentImpl]: java.lang.NoClassDefFoundError: com.sun.xml.messaging.saaj.soap.SOAPDocumentImpl
at com.sun.xml.messaging.saaj.soap.SOAPPartImpl.<init>(SOAPPartImpl.java:119)
at com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl.getSOAPPart(Message1_1Impl.java:109)
at org.apache.cxf.binding.soap.saaj.SAAJOutInterceptor.handleMessage(SAAJOutInterceptor.java:119)
at org.apache.cxf.jaxws.handler.soap.SOAPHandlerInterceptor.handleMessage(SOAPHandlerInterceptor.java:119)
This means WAS 6.1 does not understand SAAJ1.3 libraries since the class is there in the impl jar and endorsed as well (+parent-last classloader)
2. If I endorse saaj-impl and saaj-api.jars (SAAJ1.2 spec)
I get the original error on the service end -
[3/23/10 1:00:45:097 EDT] 0000001f SystemErr R java.lang.IllegalArgumentException: local part cannot be "null" when creating a QName
[3/23/10 1:00:45:097 EDT] 0000001f SystemErr R at javax.xml.namespace.QName.<init>(Unknown Source)
[3/23/10 1:00:45:097 EDT] 0000001f SystemErr R at javax.xml.namespace.QName.<init>(Unknown Source)
On the client side I get -
java.lang.NoSuchMethodError: javax/xml/soap/SOAPFault.setFaultCode(Ljavax/xml/namespace/QName;)V
at org.apache.cxf.binding.soap.saaj.SAAJInInterceptor.handleMessage(SAAJInInterceptor.java:155)
at org.apache.cxf.jaxws.handler.soap.SOAPMessageContextImpl.getMessage(SOAPMessageContextImpl.java:78)
at org.apache.cxf.jaxws.handler.soap.SOAPHandlerInterceptor.createProtocolMessageContext(SOAPHandlerInterceptor.java:244)
which clearly indicates CXF 2.2.7 requires SAAJ1.3 (which WAS 6.1 does not support.).
However for the error on the service end - Local Name Cannot be Null...Do you think this is because of the SAAJ1.2 + WAS 6.1 +JDK 1.5 nexus.
Dan - It appear JDK 1.6 will not find a shelf-life on WAS 6.1. Is it possible to put a patch in CXF to retrofit SAAJ1.2.
I came across a similar request in this link.
http://old.nabble.com/CXF-failing-on-Websphere-while-using-Handlers-td16851517.html
thanks
Sid
> "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
> Attachments: bpm-servicesCXF.zip, SpringClientWithSAMLToken.zip
>
>
> 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.
[jira] Commented: (CXF-2725) "local part cannot be "null" when
creating a QName"
Posted by "Sidhartha Priye (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848594#action_12848594 ]
Sidhartha Priye commented on CXF-2725:
--------------------------------------
Dan,
With the help of this link -
http://cwiki.apache.org/confluence/display/CXF20DOC/Application+Server+Specific+Configuration+Guide
I can now endorse SAAJ1.3.2 libraries on WAS 6.1. The trick is to add the jsr173_api-1.0.jar. So for any one's reference here are the jars
in WAS endorsed directory. Make sure your application and webapp-classloaders are parent-last
saaj-impl-1.3.2.jar
saaj-api-1.3.jar
jsr173_api-1.0.jar
jaxp-ri-1.4.2.jar
Once I got this then I copied CXF2.2.7 jars on both the client app and the server app (both deployed on the same node). Restarted the server and that was it. For anyone who run
into this problem, here are the list of jars I have assembled that gave me a working solution -
Apache Commons Jars:
commons-codec-1.3.jar commons-collections-3.2.1.jar commons-logging-1.1.1.jar commons-pool-1.5.2.jar commons-configuration-1.5.jar
commons-lang-2.4.jar
CXF jars/supporting jars:
geronimo-activation_1.1_spec-1.0.2.jar geronimo-annotation_1.0_spec-1.1.1.jar geronimo-javamail_1.4_spec-1.6.jar
geronimo-jaxws_2.1_spec-1.0.jar geronimo-stax-api_1.0_spec-1.0.1.jar geronimo-ws-metadata_2.0_spec-1.1.2.jar
jaxb-api-2.1.jar jaxb-impl-2.1.12.jar jaxb-xjc-2.1.12.jar
cxf-2.2.7.jar FastInfoset-1.2.7.jar jetty-6.1.21.jar
jetty-util-6.1.21.jar stax2-api-3.0.1.jar velocity-1.6.2.jar
woodstox-core-asl-4.0.7.jar wss4j-1.5.8.jar wstx-asl-3.2.9.jar
xmlbeans-2.4.0.jar xml-resolver-1.2.jar XmlSchema-1.4.5.jar
xmlsec-1.4.3.jar xmltooling-1.2.1.jar
if you are using OpenSAML then you would need:
opensaml-2.3.0.jar
openws-1.3.0.jar
slf4j-api-1.5.10.jar
slf4j-jdk14-1.5.10.jar
velocity-1.6.2.jar
xmlsec-1.4.3.jar
xmltooling-1.2.1.jar
My endorsed library on WAS6.1 (<WAS_ROOT>/java/jre/lib/endorsed) is:
jaxp-ri-1.4.2.jar
jsr173_api-1.0.jar
resolver-2.9.1.jar
saaj-api-1.3.jar
saaj-impl-1.3.2.jar
serializer-2.9.1.jar
wsdl4j-1.6.2.jar
xalan-2.7.1.jar
xercesImpl-2.9.1.jar
xml-apis-2.9.1.jar
Thank you very much for the fix to 2.2.7. Hope to stay in touch!!!
thanks
Sid
> "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
> Attachments: bpm-servicesCXF.zip, SpringClientWithSAMLToken.zip
>
>
> 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.
[jira] Commented: (CXF-2725) "local part cannot be "null" when
creating a QName"
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848517#action_12848517 ]
Daniel Kulp commented on CXF-2725:
----------------------------------
My web-inf/lib probably has too much in it. I pretty much copied everything from the cxf distro:
{code}
BPMCore.jar commons-configuration-1.5.jar jettison-1.2.jar serializer-2.7.1.jar velocity-1.5.jar
ECMBPMCommon.jar commons-lang-2.4.jar joda-time-1.6.jar slf4j-api-1.5.10.jar velocity-1.6.2.jar
FastInfoset-1.2.7.jar commons-logging-1.1.1.jar jra-1.0-alpha-4.jar slf4j-jdk14-1.5.10.jar woodstox-core-asl-4.0.7.jar
Jace.jar commons-pool-1.5.2.jar js-1.7R1.jar spring-beans-2.5.6.jar wsdl4j-1.6.2.jar
WHICH_JARS cxf-bundle-2.2.6.jar jsr311-api-1.1.jar spring-context-2.5.6.jar wss4j-1.5.8.jar
XmlSchema-1.4.5.jar geronimo-javamail_1.4_spec-1.6.jar log4j.jar spring-context-support-2.5.6.jar xalan-2.7.1.jar
aopalliance-1.0.jar geronimo-jms_1.1_spec-1.1.1.jar mina-core-2.0.0-M6.jar spring-core-2.5.6.jar xml-resolver-1.2.jar
asm-2.2.3.jar geronimo-servlet_2.5_spec-1.2.jar neethi-2.0.4.jar spring-jms-2.5.6.jar xmlbeans-2.4.0.jar
bcprov-jdk15-145.jar jaxb-impl-2.1.12.jar opensaml-2.3.0.jar spring-tx-2.5.6.jar xmlsec-1.4.3.jar
commons-codec-1.3.jar jaxb-xjc-2.1.12.jar openws-1.3.0.jar spring-web-2.5.6.jar xmltooling-1.2.1.jar
commons-collections-3.2.1.jar jaxen-1.1.jar oro-2.0.8.jar stax2-api-3.0.1.jar
{code}
All I endorsed were:
{code}
serializer-2.7.1.jar xalan-2.7.1.jar xercesImpl-2.9.1.jar
{code}
which I still had to do due to the opensaml check that they do.
> "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
> Attachments: bpm-servicesCXF.zip, SpringClientWithSAMLToken.zip
>
>
> 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.
[jira] Commented: (CXF-2725) "local part cannot be "null" when
creating a QName"
Posted by "Sidhartha Priye (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848522#action_12848522 ]
Sidhartha Priye commented on CXF-2725:
--------------------------------------
I see....Will have to check if WAS 6.1 is JDK6 compliant or not. I know I needed them for IBM JDK 5 which is what I am using currently.
Thanks again..I am trying the test now. Will keep you posted.
> "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
> Attachments: bpm-servicesCXF.zip, SpringClientWithSAMLToken.zip
>
>
> 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.
[jira] Updated: (CXF-2725) "local part cannot be "null" when
creating a QName"
Posted by "Sidhartha Priye (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sidhartha Priye updated CXF-2725:
---------------------------------
Attachment: SpringClientWithSAMLToken.zip
SpringClientWithSAMLToken.zip - Project Interchange file for the SOAP Client that constructs a SAML token and inserts into the SOAP Header using a JAX WS Handler. This can be directly imported into Eclipse.
I have left out cxf2.2.6 jar and Spring 2.5.6 jars out of the WEB_INF/lib directory so that the size remains under 10MB. They will need to be included back in.
These are the jars I have under the endorsed directory on WAS
resolver-2.9.1.jar
saaj-api.jar
saaj-impl.jar
serializer-2.9.1.jar
wsdl4j-1.6.2.jar
xalan-2.7.1.jar
xercesImpl-2.9.1.jar
xml-apis-2.9.1.jar
Limitations using libraries:
1. Cannot use SUN's JAXP libraries with OpenSAML 2.0. OpenSAML does a validation check and throws an error if it finds SUN's JAXP jar. As per them SUN's JAXP libraries are broken so instead they recommend using latest Xerces and Xalan in WAS endorsed directory.
2. Cannot endorse saaj-1.3.2 api and impl jars on WAS 6.1. WAS 6.1 does not recognize any of those classes. So forced to use saaj-impl and saaj-api jars in the endorsed directory.
> "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
> Attachments: SpringClientWithSAMLToken.zip
>
>
> 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.
[jira] Commented: (CXF-2725) "local part cannot be "null" when
creating a QName"
Posted by "Sidhartha Priye (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848518#action_12848518 ]
Sidhartha Priye commented on CXF-2725:
--------------------------------------
Thanks!!! Yup looks like you have everything in there.. Do I need the saaj-api1.3 and saaj-impl1.3.2 jars. I do not see them here on your list.
I was earlier have to endorsing them on WAS 6.1 to override WAS own SAAJ implementation.
> "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
> Attachments: bpm-servicesCXF.zip, SpringClientWithSAMLToken.zip
>
>
> 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.
[jira] Resolved: (CXF-2725) "local part cannot be "null" when
creating a QName"
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp resolved CXF-2725.
------------------------------
Resolution: Fixed
Fix Version/s: 2.2.7
Assignee: Daniel Kulp
> "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
> Assignee: Daniel Kulp
> Priority: Critical
> Fix For: 2.2.7
>
> Attachments: bpm-servicesCXF.zip, SpringClientWithSAMLToken.zip
>
>
> 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.
[jira] Updated: (CXF-2725) "local part cannot be "null" when
creating a QName"
Posted by "Sidhartha Priye (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (CXF-2725) "local part cannot be "null" when
creating a QName"
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848507#action_12848507 ]
Daniel Kulp commented on CXF-2725:
----------------------------------
I just tried your example with tomcat and both CXF 2.3.0-SNAPSHOT and 2.2.7 (now released) after removing the reference to your logger (which seems to be WebSphere specific) and it worked fine. The service through a ECMBPMException, but that means the message got there and the saml was processed.
The log contains:
{code}
Signature VALIDATED with Subjectmbrendish
********Inside Business Delegate: Value of Subject*******mbrendish
[HSC Logger] [getLogger] Initializing Logger for com.syscom.hsc.BpmServices
[HSC Logger] [getLogger] Initializing Logger for com.syscom.hsc.ecmbpm.exception.ECMBPMException
Mar 22, 2010 10:44:12 PM org.apache.cxf.phase.PhaseInterceptorChain doDefaultLogging
INFO: Application {http://web.hsc.syscom.com/}BPMWebService#{http://web.hsc.syscom.com/}findTaskListUsingLoginCreds has thrown exception, unwinding now: com.syscom.hsc.ecmbpm.exception.ECMBPMException: Unhandled exception
{code}
which looks like it was properly processed.
Thus, can you try using 2.2.7 instead of 2.2.6?
> "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
> Attachments: bpm-servicesCXF.zip, SpringClientWithSAMLToken.zip
>
>
> 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.
[jira] Commented: (CXF-2725) "local part cannot be "null" when
creating a QName"
Posted by "Sidhartha Priye (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848515#action_12848515 ]
Sidhartha Priye commented on CXF-2725:
--------------------------------------
Dan,
First of all thanks for looking into this. Really appreciate your time.
That is great news. I think I tried with the 2.2.7-snapshot version that you had released specifically for this issue couple of weeks and it failed.
Let me try with the stable 2.2.7 version that works for you.
Also if its ok can you send me list of jars that is in your web-inf/lib. as well any that you may have to endorse.
I am assuming since you are running of Tomcat, you didnt have to endorse anything that I have to with WAS 6.1
> "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
> Attachments: bpm-servicesCXF.zip, SpringClientWithSAMLToken.zip
>
>
> 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.
[jira] Commented: (CXF-2725) "local part cannot be "null" when
creating a QName"
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848511#action_12848511 ]
Daniel Kulp commented on CXF-2725:
----------------------------------
Note, I AM able to reproduce it with 2.2.6, but not with 2.2.7. Thus, it looks like this is now fixed with 2.2.7.
> "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
> Attachments: bpm-servicesCXF.zip, SpringClientWithSAMLToken.zip
>
>
> 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.
[jira] Updated: (CXF-2725) "local part cannot be "null" when
creating a QName"
Posted by "Sidhartha Priye (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sidhartha Priye updated CXF-2725:
---------------------------------
Description:
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.
was:
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.
Exception being thrown is -
[3/20/10 11:22:29:456 EDT] 00000024 SystemErr R java.lang.IllegalArgumentException: local part cannot be "null" when creating a QName
[3/20/10 11:22:29:456 EDT] 00000024 SystemErr R at javax.xml.namespace.QName.<init>(Unknown Source)
[3/20/10 11:22:29:456 EDT] 00000024 SystemErr R at javax.xml.namespace.QName.<init>(Unknown Source)
[3/20/10 11:22:29:456 EDT] 00000024 SystemErr R at org.opensaml.xml.util.XMLHelper.constructQName(XMLHelper.java:433)
[3/20/10 11:22:29:456 EDT] 00000024 SystemErr R at org.opensaml.xml.util.XMLHelper.getNodeQName(XMLHelper.java:171)
[3/20/10 11:22:29:456 EDT] 00000024 SystemErr R at org.opensaml.xml.io.AbstractXMLObjectUnmarshaller.unmarshallAttribute(AbstractXMLObjectUnmarshaller.java:215)
[3/20/10 11:22:29:456 EDT] 00000024 SystemErr R at org.opensaml.xml.io.AbstractXMLObjectUnmarshaller.unmarshall(AbstractXMLObjectUnmarshaller.java:107)
[3/20/10 11:22:29:456 EDT] 00000024 SystemErr R at com.syscom.hsc.security.saml.service.SAMLTokenProcessor.unmarshall(SAMLTokenProcessor.java:191)
[3/20/10 11:22:29:456 EDT] 00000024 SystemErr R at com.syscom.hsc.security.saml.service.SAMLTokenProcessor.validateSAMLSignature(SAMLTokenProcessor.java:78)
[3/20/10 11:22:29:456 EDT] 00000024 SystemErr R at com.syscom.hsc.web.soap.ServiceSAMLHandler.handleMessage(ServiceSAMLHandler.java:115)
[3/20/10 11:22:29:456 EDT] 00000024 SystemErr R at com.syscom.hsc.web.soap.ServiceSAMLHandler.handleMessage(ServiceSAMLHandler.java:1)
[3/20/10 11:22:29:456 EDT] 00000024 SystemErr R at org.apache.cxf.jaxws.handler.HandlerChainInvoker.invokeHandleMessage(HandlerChainInvoker.java:335)
[3/20/10 11:22:29:456 EDT] 00000024 SystemErr R at org.apache.cxf.jaxws.handler.HandlerChainInvoker.invokeHandlerChain(HandlerChainInvoker.java:253)
[3/20/10 11:22:29:456 EDT] 00000024 SystemErr R at org.apache.cxf.jaxws.handler.HandlerChainInvoker.invokeProtocolHandlers(HandlerChainInvoker.java:131)
[3/20/10 11:22:29:456 EDT] 00000024 SystemErr R at org.apache.cxf.jaxws.handler.soap.SOAPHandlerInterceptor.handleMessageInternal(SOAPHandlerInterceptor.java:152)
[3/20/10 11:22:29:456 EDT] 00000024 SystemErr R at org.apache.cxf.jaxws.handler.soap.SOAPHandlerInterceptor.handleMessage(SOAPHandlerInterceptor.java:119)
[3/20/10 11:22:29:456 EDT] 00000024 SystemErr R at org.apache.cxf.jaxws.handler.soap.SOAPHandlerInterceptor.handleMessage(SOAPHandlerInterceptor.java:69)
[3/20/10 11:22:29:456 EDT] 00000024 SystemErr R at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:243)
[3/20/10 11:22:29:456 EDT] 00000024 SystemErr R at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:109)
[3/20/10 11:22:29:456 EDT] 00000024 SystemErr R at org.apache.cxf.transport.servlet.ServletDestination.invoke(ServletDestination.java:98)
[3/20/10 11:22:29:456 EDT] 00000024 SystemErr R at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:406)
[3/20/10 11:22:29:456 EDT] 00000024 SystemErr R at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:178)
[3/20/10 11:22:29:456 EDT] 00000024 SystemErr R at org.apache.cxf.transport.servlet.AbstractCXFServlet.invoke(AbstractCXFServlet.java:142)
[3/20/10 11:22:29:456 EDT] 00000024 SystemErr R at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:179)
[3/20/10 11:22:29:456 EDT] 00000024 SystemErr R at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:103)
[3/20/10 11:22:29:456 EDT] 00000024 SystemErr R at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
[3/20/10 11:22:29:456 EDT] 00000024 SystemErr R at org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:159)
[3/20/10 11:22:29:456 EDT] 00000024 SystemErr R at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1096)
[3/20/10 11:22:29:456 EDT] 00000024 SystemErr R at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:570)
[3/20/10 11:22:29:456 EDT] 00000024 SystemErr R at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:478)
[3/20/10 11:22:29:456 EDT] 00000024 SystemErr R at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:90)
[3/20/10 11:22:29:456 EDT] 00000024 SystemErr R at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:748)
[3/20/10 11:22:29:456 EDT] 00000024 SystemErr R at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1466)
[3/20/10 11:22:29:471 EDT] 00000024 SystemErr R at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:119)
[3/20/10 11:22:29:471 EDT] 00000024 SystemErr R at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:458)
[3/20/10 11:22:29:471 EDT] 00000024 SystemErr R at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:387)
[3/20/10 11:22:29:471 EDT] 00000024 SystemErr R at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:267)
[3/20/10 11:22:29:471 EDT] 00000024 SystemErr R at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214)
[3/20/10 11:22:29:471 EDT] 00000024 SystemErr R at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113)
[3/20/10 11:22:29:471 EDT] 00000024 SystemErr R at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
[3/20/10 11:22:29:471 EDT] 00000024 SystemErr R at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
[3/20/10 11:22:29:471 EDT] 00000024 SystemErr R at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
[3/20/10 11:22:29:471 EDT] 00000024 SystemErr R at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136)
[3/20/10 11:22:29:471 EDT] 00000024 SystemErr R at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:195)
[3/20/10 11:22:29:471 EDT] 00000024 SystemErr R at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:743)
[3/20/10 11:22:29:471 EDT] 00000024 SystemErr R at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:873)
[3/20/10 11:22:29:471 EDT] 00000024 SystemErr R at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1473)
> "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.0.12
> Environment: Websphere 6.1, CXF 2.0-incubator, OpenSAML libraries, Spring 2.0.4 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.
[jira] Commented: (CXF-2725) "local part cannot be "null" when
creating a QName"
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848520#action_12848520 ]
Daniel Kulp commented on CXF-2725:
----------------------------------
You may or may not need them. I'm using Java6 which has a correct version of SAAJ built into it. Thus, I didn't need it. Couple others like activation, stax-api, jaxws-api, etc.... are also part of java6.
> "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
> Attachments: bpm-servicesCXF.zip, SpringClientWithSAMLToken.zip
>
>
> 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.