Hi Amila,
I'm currently using Axis2 1.3 version, is this bug fixed in that or do I need to get nightly build for the fix. And what is the fix? If I define a parameter type as xsd:anyType in my WSDL, does WSDL2Java convert it as java.lang.Object in the generated sources or does it convert to org.apache.axiom.om.OMElement? Thanks Raghu ________________________________ From: Amila Suriarachchi [mailto:[EMAIL PROTECTED] Sent: Thursday, August 16, 2007 9:36 PM To: axis-user@ws.apache.org Subject: Re: OMElement Vs java.lang.Object for (xsd:anyType) - Axis 1.3 Vs Axis 2 code generation this is a bug in Axis2. It has fixed in the trunk. please have a look at with a nightly build. On 8/11/07, Raghu Upadhyayula < [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > wrote: Hi, In my webservices, I have a method which has a parameter defined as type="xsd:anyType" in the WSDL. In Axis 1.3, when I did WSDL2Java for my WSDL that parameter got converted to java.lang.Object. But in Axis2 1.2, when I did WSDL2Java for the same WSDL, that parameter got converted to org.apache.axiom.om.OMElement. My question is, if I need to pass a Java Object to my webservice method, how do I convert it to OMElement and pass it to the method from the client code & how do I convert OMElement back to java.lang.Object in my server code? Thanks Raghu -- Amila Suriarachchi, WSO2 Inc.
