Hi again,
The problem seems to come from the client, because on the server side, the
bean is correctly deserialized, and serialized for the response. Is there a
way to configure a client according to a set of WSDD file ?
Regards
Stephane.
> -----Original Message-----
> From: Stephane Lecercle
> Sent: Wednesday, February 26, 2003 6:22 PM
> To: '[EMAIL PROTECTED]'
> Subject: Serialization/Deserialization issue with Axis 1.1 RC1
>
> Hi everybody,
>
> I am using Axis 1.1 RC1, and I have met a strange issue on
> serializartion/deserialization of custom types (such as a bean).
> I get the following exception, while invoking a service having a custom
> bean type :
>
> - Exception:
> org.xml.sax.SAXException: Deserializing parameter 'myMethodReturn': could
> not find deserializer for type {urn:wstk_sample_MyHelloWorld}MyBigData
> at
> org.apache.axis.message.RPCHandler.onStartChild(RPCHandler.java:297)
> at
> org.apache.axis.encoding.DeserializationContextImpl.startElement(Deseriali
> zationContextImpl.java:921)
> at
> org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:19
> 8)
> at
> org.apache.axis.message.MessageElement.publishToHandler(MessageElement.jav
> a:699)
> at
> org.apache.axis.message.RPCElement.deserialize(RPCElement.java:224)
> at
> org.apache.axis.message.RPCElement.getParams(RPCElement.java:331)
> at org.apache.axis.client.Call.invoke(Call.java:2200)
> at org.apache.axis.client.Call.invoke(Call.java:2099)
> at org.apache.axis.client.Call.invoke(Call.java:1622)
> at
> com.bo.wstk.proxy.WSTKSmartProxy.invoke(G:/cc_views/common_as_kernel_rtm/w
> stk/modules/wstk_java/src/com/bo/wstk/proxy/WSTKSmartProxy.java:74)
> at
> com.bo.wstk.test.client.MyHelloWorldClient.main(G:/cc_views/common_as_kern
> el_rtm/wstk/samples/client_java/src/com/bo/wstk/test/client/MyHelloWorldCl
> ient.java:95)
>
> In the Axis archive, I have seen that several persons have got the same
> problem. I have resolved it, by using the Call.registerTypeMapping,
> setting explicitely the serializer and deserializer for my custom type.
> But, I can't understand why the deserializer is not found. Indeed, in the
> WSDD file, there is the class to use. Why the client doesn't find the
> correspondance between the serializer and the type ?
>
> Regards,
>
> Stephane.
