Thanks for the information.
I am using ant to generate webservies with the following command....
<target name="Generate_WSDL_WSDD_Proxies" depends="ConfigPreparation">
<echo message="**** Generating WSDL for
${servicePackage}.${serviceClass} ****"/>
<java fork="true" failonerror="true"
classname="org.apache.axis.wsdl.Java2WSDL">
<classpath refid="project.class.path"/>
<arg line="-o ${CONFIG_GEN_DIR}\${serviceClass}.wsdl"/>
<arg line="-l ${urlBase}/${serviceClass}"/>
<arg line="-n ${namespace}"/>
<arg line="-m ${methodsName}"/>
<arg line="-a"/>
<arg line="-y ${encoding}"/>
....
....
....
</java>
Where in I am invoking Java2WSDL command along with some parameters
defined. How will define which serializer/deserializer to use with the
options provided in Java2WSDL.
-----Original Message-----
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: 17 March 2005 18:40
To: [email protected]; jayachandra
Subject: Re: Java2WSDL.....
See samples/ejb/ant-build.xml for example:
<axis-java2wsdl classname="samples.ejb.NiceThingsBean"
methods="sayHello,findNiceThingsFor,updateNiceThingsFor"
output="nicethings.wsdl"
location="http://localhost:8080/axis/services/NiceThingsBean";
namespace="http://localhost:8080/axis/services/NiceThingsBean";
namespaceImpl=
"http://localhost:8080/axis/services/NiceThingsBean";>
<complextype classname="samples.ejb.NiceThings"
namespace="urn:NiceThingsBean"/>
<!-- You can also pass in another serializer/deserializer if you don't
want to use the default
BeanSerializerFactory for a particular complextype
serializer="org.apache.axis.encoding.ser.BeanSerializerFactory"
deserializer="org.apache.axis.encoding.ser.BeanDeserializerFactory"
-->
</axis-java2wsdl>
On Thu, 17 Mar 2005 18:10:01 +0530, jayachandra <[EMAIL PROTECTED]>
wrote:
> 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
>
--
Davanum Srinivas - http://webservices.apache.org/~dims/
