One work around is to manually (or through some script) modify in the .wsdd file the typemapping or bean mapping declaration that gets generated by default with the custom (de)serializer classes when you run WSDL2Java. I don't think there is any such way to incorporate into wsdl itself, the serializer/deserialzer information of involved types. wsdl is meant to be just the 'abstract' plain way of describing datatypes the way they would be transacted 'on the wire'. Any (de)serialization stuff need to be described seperately through configuration files (.wsdd) only. Well, just my thought!
Bye jayachandra On Wed, 16 Mar 2005 08:24:31 -0500, Nanda, Anshuman <[EMAIL PROTECTED]> wrote: > > Does anyone know how can I specify custom serializer/de-serializer to be > used for a given webservice when generating the WSDL and the .wsdd file > using Java2WSDL tool. > > Regards > Anshuman Nanda > > -----Original Message----- > From: Chad Woolley [mailto:[EMAIL PROTECTED] > Sent: 16 March 2005 18:51 > To: [email protected] > Subject: Can Wsdl2Java make the stub implement a specified interface? > > Hi, > > I would like Wsdl2Java to make the generated class implement an > interface. This would save a ton of effort and duplication during > testing, where I currently have to duplicate a lot of stub-generation > and test code for both classes. > > Is there any support for this planned? Has anyone else requested this > (I didn't find anything in the archives)? Would a patch to allow this > be considered? > > Thanks, > Chad > > -- -- Jaya
