Hi Deepal, Is this a known issue? Currently, a null is returned without any error even when there is a value in the SOAP response.
I was able to workaround this problem by using my own version of the beanutil.deserialize() method. Thanks, Ken -----Original Message----- From: Deepal jayasinghe [mailto:[EMAIL PROTECTED] Sent: Friday, August 03, 2007 12:09 AM To: [email protected] Subject: Re: xs:anyType deserialize problem in Axis2 version 1.2 Ken Tam wrote: > Hi all, > > I've exposed a POJO web service with a method which returns another > POJO containing a member of type Object. This translates to xs:anyType > in the WSDL. I wrote an AXIS2 client to consume this web service. The > value of the Object is null after the deserialization process. The > actual value of the Object member is a simple type (String, Float and > Integer). Is there another way to instruct the WSDL generation process > to use a different value? Is this a deserialization issue? At the moment there is no way to configure that. Thanks Deepal --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
