This seems like a bug .. did you generate code from a WSDL and is the
generated code not working? Or is it for a POJO service?
Please give more info and file a bug so this can be fixed for the next
release.
Thanks,
Sanjiva.
On Wed, 2007-01-24 at 17:56 -0500, Sathija Pavuluri wrote:
> Hello,
>
> I was surprised by what I found recently while trying to serialize an object
> along with its super class' fields.
>
> TheParent {
> a;
> b;
> }
>
> TheChild {
> c;
> d;
> }
>
> My service class returns an object of TheChild. The generated wsdl defined
> the complex type TheChild with elements
> a,b,c,d.
> Now, when I invoked the web service and inspected the response, a and b
> (which are from the parent) are totally
> missing in the response.
> Looks like the super class fields are not being serialized.
> I thought (wishfully expected) axis would handle class hierarchy. Its not to
> be so.
> If the serializer didnt handle this, the generated wsdl probably should not
> generate a single complex type because it
> is misleading.
>
> Is there a different approach to this or am I off track?
> I would hate for the client to have to invoke multiple service calls for each
> object and put them together to achieve
> the desired result.
>
> Thanks,
> Sathija.
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
--
Sanjiva Weerawarana, Ph.D.
Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
Director; Open Source Initiative; http://www.opensource.org/
Member; Apache Software Foundation; http://www.apache.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
