aspose file tools
The moose likes Web Services and the fly likes deserialization error: unexpected XML reader state. Big Moose Saloon
  Search | Java FAQ | Recent Topics
Register / Login
JavaRanch » Java Forums » Java » Web Services
Reply Bookmark "deserialization error: unexpected XML reader state." Watch "deserialization error: unexpected XML reader state." New topic
Author

deserialization error: unexpected XML reader state.

Vinod Awar
Ranch Hand

Joined: Nov 06, 2006
Posts: 125
Hii all,

iam accessing a webservice from a dynamic proxy client.The client can invoke the operations. when i run this client program it blows up this error:


I used Charles web debugging proxy to monitor the request/response.
The request is ok but the response contains the header content-length:0 .
Any ideas on this ?

Thanks and Regards,

Vinod


The biggest bankruptcy is the loss of enthusiasm
William Brogden
Author and all-around good cowpoke
Rancher

Joined: Mar 22, 2000
Posts: 12271
    
    1
The request is ok but the response contains the header content-length:0 .


If there is in fact no XML content in the response, the exact error from the XML reader is meaningless.

Aside from the content-length:0 - what other response headers are sent?

Why are you sure that the request is "ok"?

Bill


Java Resources at www.wbrogden.com
Vinod Awar
Ranch Hand

Joined: Nov 06, 2006
Posts: 125
Response Headers:

HTTP/1.1 302 Found
Date: Thu, 21 Jun 2007 13:24:42 GMT
Server: IBM_HTTP_SERVER
Content-Length: 0
Content-Type: text/html; charset=ISO-8859-1
Content-Language: en-US

There was Location header also.


Why are you sure that the request is "ok"?



Because i tried by passing invalid parameters and i got AuthenticationException.

Thanks and Regards,
Vinod
Vinod Awar
Ranch Hand

Joined: Nov 06, 2006
Posts: 125
Does this have anything to do with wsdl?
William Brogden
Author and all-around good cowpoke
Rancher

Joined: Mar 22, 2000
Posts: 12271
    
    1
Content-Type: text/html; charset=ISO-8859-1


This suggests to me that the request is not in fact getting through to the web service at all. Either the service is down or your addressing is incorrect. The 302 code supposedly indicates that the resource has temporarily been moved - see the Javadocs for HttpServletResponse for a list of http status codes.

Bill
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: deserialization error: unexpected XML reader state.
 
Similar Threads
Excpetion deserialization error while creating XML for sending via web service
deserialization error: unexpected XML reader state. expected: END but found
JAX-RPC - deserialization error: unexpected XML reader state.
Webservice client using JAX-WS RI 2.1.7
How to get SOAP response as XML in Client Struts or Servlet. ?