complex types as parameters

[Lloyd Smith <sm...@san.rr.com>]

If I define a complex type in my WSDL and use it later on as a parameter, muse emits a method signature of Element for that parameter.  I guess I expected to see a generated proxy class and an explicit type in the parameter.  Is that the expected behavior?  If so, what's a good toolkit for manually generating the proxy class - jaxb?

Re: complex types as parameters

[Daniel Jemiolo <da...@us.ibm.com>]

wsdl2java generates an Element because it doesn't know what the Java class 
should be and doesn't generate beans for complex types; if you want to 
have it generate code with the name of a Java class, you can do so if your 
muse.xml file has the <custom-serializer/> mappings in it for the type. 
This will only generate code that references the class, though - you still 
have to provide the class, either by coding it yourself or using something 
like JAXB/JiBX/Castor/XMLBeans.

assuming you've added the <custom-serializer/> mapping to muse.xml, you 
can generate your whole project (client and server) like so:

        wsdl2java -wsdl MyResource.wsdl -axis2 -proxy -descriptor muse.xml

you can get the muse.xml file by running the tool once (as you've already 
done) and adding the <custom-serializer/> tag. or you can generate a 
skeleton muse.xml file as described here:

 http://ws.apache.org/muse/docs/2.1.0/manual/tools/wsdl2java.html#usage

Dan


"Lloyd Smith" <sm...@san.rr.com> wrote on 02/10/2007 05:52:49 AM:

> If I define a complex type in my WSDL and use it later on as a 
parameter, muse
> emits a method signature of Element for that parameter.  I guess I 
expected to
> see a generated proxy class and an explicit type in the parameter.  Is 
that 
> the expected behavior?  If so, what's a good toolkit for manually 
generating 
> the proxy class - jaxb?

---------------------------------------------------------------------
To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-user-help@ws.apache.org