axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Davanum Srinivas <dava...@gmail.com>
Subject Re: Complex type / Javabean design
Date Wed, 15 Jun 2005 15:41:16 GMT
hehehe...WSDL First! :)

-- dims

On 6/15/05, Ephemeris Lappis <ephemeris.lappis@gmail.com> wrote:
> Hello.
> 
> This is a simple, perhaps stupid, question about how to design some kind of
> javabeans to be good complex types for the wsdl and soap translation.
> 
> I have done some basic tests with simple flat, structure like javabeans with
> primitive or 1-1 aggregated complex types. All this seems to work with Axis.
> 
> Now, i'm looking for more complex types with 1-n agregations. For instance
> an "Order" and "Product line". The javabean convention let the bean designer
> provide both agregate getter and setter, and indexed properties ones. In my
> previous example, operations on my Order object could be something like :
> 
>         ProductLine[] getProductLines()
>         void setProductLines(ProductLine[] pl)
> 
> to set or get the whole agregate. But indexed properties style methods could
> also be :
> 
>         ProductLine getProductLine(int index)
>         void setProductLine(ProductLine pl, int index)
> 
> I've tested something like that with axis (1.2 final), and the java2wsdl
> produces a strange result. The Order type references two pseudo-attributes :
> one for the array, mapping the first setter/getter set, and another one for
> the indexed property...
> 
> In this case, or similar cases, does it make sense to design (or reuse) such
> javabeans. If yes, is there any way to use the standard java2wsdl
> translation (I know someone is going to quickly answer to wsdl it first !),
> and standard serializers ?
> 
> Thanks for your comments.
> 
> --
> Ephemeris Lappis
> 
> 


-- 
Davanum Srinivas -http://blogs.cocoondev.org/dims/

Mime
View raw message