Skip to main content

Exception Thrown During Fault Decoding

1 reply [Last post]
aneilson
Offline
Joined: 2005-08-16
Points: 0

I'm having problems handling a fault coming back from my service using JAX-WS EA2. The fault is being generated from a service implementing using .NET and WSE 3.0. This fault is handled by .NET/WSE 3.0 clients correctly. The fault appears to be well-formed. The only thing that appears in the fault that is beyond a standard SOAP fault is the Properties element that appears in the details. A Properties element is defined in the WSDL.

The message in the exception seems a bit odd. It would suggest that the XML isn't well-formed, but it certainly is.

Is there something basic difference in how JAX-WS handles SOAP faults as compared with .NET/WSE? This doesn't seem to bode well from the point of view of interoperability.

unexpected XML reader state. expected: END_ELEMENT but found: START_ELEMENT
at com.sun.xml.ws.streaming.XMLStreamReaderUtil.verifyReaderState(XMLStreamReaderUtil.java:154)
at com.sun.xml.ws.client.SOAP12XMLDecoder.decodeFault(SOAP12XMLDecoder.java:105)
at com.sun.xml.ws.encoding.soap.SOAPDecoder.decodeBodyContent(SOAPDecoder.java:213)
at com.sun.xml.ws.encoding.soap.SOAPDecoder.decodeBody(SOAPDecoder.java:192)
at com.sun.xml.ws.encoding.soap.SOAPDecoder.decodeEnvelope(SOAPDecoder.java:125)
at com.sun.xml.ws.client.SOAPXMLDecoder.toInternalMessage(SOAPXMLDecoder.java:172)
at com.sun.xml.ws.client.SOAPMessageDispatcher.receive(SOAPMessageDispatcher.java:195)
at com.sun.xml.ws.client.SOAPMessageDispatcher.doSend(SOAPMessageDispatcher.java:116)
at com.sun.xml.ws.client.SOAPMessageDispatcher.send(SOAPMessageDispatcher.java:69)
at com.sun.xml.ws.encoding.soap.internal.DelegateBase.send(DelegateBase.java:65)
at com.sun.xml.ws.client.EndpointIFInvocationHandler.implementSEIMethod(EndpointIFInvocationHandler.java:122)
at com.sun.xml.ws.client.EndpointIFInvocationHandler.invoke(EndpointIFInvocationHandler.java:76)
at $Proxy22.serverInfo(Unknown Source)
at com.xxx.titan.service._2004._04.TestJAXWSClient.main(TestJAXWSClient.java:22)

<?xml version="1.0" encoding="utf-8"?>

http://schemas.xmlsoap.org/ws/2004/08/addressing/fault
uuid:1c22ecd9-7fc8-454b-ad10-b0041b393f79
uuid:310b5947-2afa-4e40-a26b-d02175165884
http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous

2005-08-17T18:41:41Z
2005-08-17T18:46:41Z

soap:Sender

System.Web.Services.Protocols.SoapException: The security token could not be authenticated or authorized

/xxx/service/titanservice.asmx

Message
The security token could not be authenticated or authorized

Code
-1

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
vivekp
Offline
Joined: 2003-06-10
Points: 0

This could be a bug with JAXWS. Can you send the WSDL/Schema that defines the Properties element and this operation?

I will take a look at it in new few days.

thanks,

-vivek.