[
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.
