The Axis2 way of dealing with this (BTW we call it 'data binding' :)) is through a well known framework like XMLbeans. The current implementation has the XMLBeans integrated and should generate the proper code (classes) for the complex types. These classes however would NOT look like the usual java beans you'll see. These are inside-out XMl beans things with a whole lot of XBeans specific stuff but they'll be properly generated and included in the stubs/skeletons :)
On 9/8/05, [EMAIL PROTECTED] <
[EMAIL PROTECTED]> wrote:
Hi all,
if your service return a complex type like 'MyType', which is build up of
Java Beans, Axis 1.x is able to generate the service code automatically by
using 'BeanSerializerFactory' in conjunction with 'WSDL2Java'.
Is axis2 able to generate the complete service code automatically
(WSDL2Java) if you are working with Java Beans, too?? Or do you always have
to fill the OMElements by your own?
Thx,
Chris
--
Ajith Ranabahu
