asked on

JAX-RPC error

I'm testing a JAX-RPC call running in Sun App Server. All of the methods are working properly except for the method which uses a user-definied object, the stack trace is:

javax.xml.rpc.soap.SOAPFaultException: JAXRPCTIE01: caught exception while handling request: deserialization error: deserialization error: unexpected XML reader state. expected: END but found: START: contentType

at com.sun.xml.rpc.client.StreamingSender._raiseFault(StreamingSender.java:528)

at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:307)

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.sun.xml.rpc.client.dii.CallInvocationHandler.doCall(CallInvocationHandler.java:121)

at com.sun.xml.rpc.client.dii.CallInvocationHandler.invoke(CallInvocationHandler.java:85)

Any idea what could be causing this?

Mayank S

Perhaps the definition of the object on the other side has changed.

CEHJ

You need to define a custom serializer

jjacksn

ASKER

CEHJ, why/how. Do I just need to override a method or something?

ASKER CERTIFIED SOLUTION

CEHJ

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

jjacksn

ASKER

I'm using JAX-RPC, I was under the impression the generation of the WSDL and the Java wrappers would take care of the serializaiton and deserialization of the object. Am I mistaken?

Mayank S

If you have used WSDL 2 Java from Axis, it should.

jjacksn

ASKER

sorry, what is that? i'm using JAX-RPC which is a bit older, but shoul still be capable of this.

SOLUTION

Mayank S

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial