Hi all,
Well first is not the case, I have done the type mapping part
through and not through the client-config.wsdd. i don't see the necessity to
Write custom serializers, because the bean-serializers when registered with
Types it doesn't seem to throw any problems, but only upon calling the
invoke() method ,it throws up the error.
Hope iam making sense with my reasoning.
Regards,
jana
-----Original Message-----
From: egemen kalyoncu [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 24, 2004 2:32 PM
To: [EMAIL PROTECTED]
Subject: RE: interface typemapping
i think you didn't configure your stub typemapping on the client.
if you want to use custom serializer you must configure deploy.wsdd on
server-side and stub class on client to do type mapping.
look at this link for more info
http://www-106.ibm.com/developerworks/library/ws-castor/
_________________________________________________________________
Protect your PC - get McAfee.com VirusScan Online
http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
-----Original Message-----
From: jana [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 24, 2004 2:32 PM
To: [EMAIL PROTECTED]
Subject: interface typemapping
Hi people,
I have this situation, where when I try to send a soapmessage
,with data objects added in the message body, it results in
{http://xml.apache.org/axis/}stackTrace: java.io.IOException: No serializer
found for class a.b.c
Would there be any suggestion about how to say implementation information
For the interface references present in the WSDL.
Regards,
jana
