Skip to main content

deserialization error: XML reader error: unexpected character content

1 reply [Last post]
priyavelayoudam
Offline
Joined: 2005-10-07

Hi -

I have developed a simple web service using JAXRPC-1.6 and deployed on to Tomcat 5.0 for JWSDP.

My Client is of DII type and one of the service endpoint interface operation returns a ArrayList which contains String elements.
When my client program invokes this operation I get the following stack trace-

Exception thrown :deserialization error: XML reader error: unexpected character content: "Temp1"
stack trace :deserialization error: XML reader error: unexpected character content: "Temp1"
at com.sun.xml.rpc.encoding.SOAPDeserializationContext.deserializeMultiRefObjects(SOAPDeserializationContext.java:90)
at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:239)
at com.sun.xml.rpc.client.dii.CallInvokerImpl.doInvoke(CallInvokerImpl.java:103)
at com.sun.xml.rpc.client.dii.BasicCall.invoke(BasicCall.java:492)
at com.polaris.pgportals.poc.model.client.ProxyClient.invokeDIIService(ProxyClient.java:276)
at com.polaris.pgportals.poc.model.client.ProxyClient.main(ProxyClient.java:47)

Please note as JAX-RPC1.6 implementation provides for deserializer and serializers for Collection and its type interfaces, I have not written one.

WebService was created using define attribute of wscompile with config.xml containing the service information.

Anyone out there any clue on what is missed out, please advise...please!!

thanks for your help.
priya

p.s: if this is not the right forum please let know.

Reply viewing options

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

Hi-

I hope that you have received the email that I sent
out to the mailing list.

At any rate,
Jaxrpc 1.X and dII were intended for use with very simple types. There is a way to work around the problem
you are finding by registering custom serializers and deserializers, however, this would negate the portability
benefit of using DII. I suggest that you try static stub
generation to get around this problem.

Thanks,
Kathy