Re: OMElement Vs java.lang.Object for (xsd:anyType) - Axis 1.3 Vs Axis 2 code generation
On 8/28/07, Raghu Upadhyayula [EMAIL PROTECTED] wrote: Hi Amila, I tried this with the nightly build jars from *axis2-1.3-SNAPSHOT-bin.zip*( adb.jar adb-codegen.jar) of Aug. 27 2007 09:33 and in this xsd:anyType is converted into OMElement, not java.lang.Object, but it worked with the nightly build jars from *axis2-SNAPSHOT-bin.zip* (adb.jar adb-codegen.jar) of Aug. 27 2007 07:44 Which version of the jars should I use? *axis2-1.3-SNAPSHOT-bin.zip *is refered to axis2 1.3 branch. axis2-SNAPSHOT-bin.zip is for the trunk. so you have to use the axis2-SNAPSHOT-bin.zip Thanks Raghu -- *From:* Amila Suriarachchi [mailto:[EMAIL PROTECTED] *Sent:* Tuesday, August 21, 2007 10:54 PM *To:* axis-user@ws.apache.org *Subject:* Re: OMElement Vs java.lang.Object for (xsd:anyType) - Axis 1.3Vs Axis 2 code generation basically you are asking when is the Axis2 1.4. we have just release Axis2 1.3 so it would be from another 3 or 4 months time. Amila. On 8/22/07, *Raghu Upadhyayula* [EMAIL PROTECTED] wrote: Hi Amila, It worked with the nightly build jars (adb.jar adb-codegen.jar). When will this change be moved to the main release (I mean which Axis2 version)? Thanks Raghu -- *From:* Amila Suriarachchi [mailto:[EMAIL PROTECTED] *Sent:* Monday, August 20, 2007 9:36 PM *To:* axis-user@ws.apache.org *Subject:* Re: OMElement Vs java.lang.Object for (xsd:anyType) - Axis 1.3Vs Axis 2 code generation On 8/17/07, *Raghu Upadhyayula* [EMAIL PROTECTED] wrote: 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. it is only available in trunk. you can try this, get a nighly build and replace adb-codgen.jar and adb.jar with the nightly build jars. Then it should work. 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 yes, if you use nighly build jars. 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.3Vs 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] 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. -- Amila Suriarachchi, WSO2 Inc. -- Amila Suriarachchi, WSO2 Inc. -- Amila Suriarachchi, WSO2 Inc.
RE: OMElement Vs java.lang.Object for (xsd:anyType) - Axis 1.3 Vs Axis 2 code generation
Hi Amila, I tried this with the nightly build jars from axis2-1.3-SNAPSHOT-bin.zip (adb.jar adb-codegen.jar) of Aug. 27 2007 09:33 and in this xsd:anyType is converted into OMElement, not java.lang.Object, but it worked with the nightly build jars from axis2-SNAPSHOT-bin.zip (adb.jar adb-codegen.jar) of Aug. 27 2007 07:44 Which version of the jars should I use? Thanks Raghu From: Amila Suriarachchi [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 21, 2007 10:54 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 basically you are asking when is the Axis2 1.4. we have just release Axis2 1.3 so it would be from another 3 or 4 months time. Amila. On 8/22/07, Raghu Upadhyayula [EMAIL PROTECTED] wrote: Hi Amila, It worked with the nightly build jars (adb.jar adb-codegen.jar). When will this change be moved to the main release (I mean which Axis2 version)? Thanks Raghu From: Amila Suriarachchi [mailto:[EMAIL PROTECTED] Sent: Monday, August 20, 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 On 8/17/07, Raghu Upadhyayula [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: 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. it is only available in trunk. you can try this, get a nighly build and replace adb-codgen.jar and adb.jar with the nightly build jars. Then it should work. 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 yes, if you use nighly build jars. 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. -- Amila Suriarachchi, WSO2 Inc. -- Amila Suriarachchi, WSO2 Inc.
RE: OMElement Vs java.lang.Object for (xsd:anyType) - Axis 1.3 Vs Axis 2 code generation
Hi Amila, It worked with the nightly build jars (adb.jar adb-codegen.jar). When will this change be moved to the main release (I mean which Axis2 version)? Thanks Raghu From: Amila Suriarachchi [mailto:[EMAIL PROTECTED] Sent: Monday, August 20, 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 On 8/17/07, Raghu Upadhyayula [EMAIL PROTECTED] wrote: 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. it is only available in trunk. you can try this, get a nighly build and replace adb-codgen.jar and adb.jar with the nightly build jars. Then it should work. 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 yes, if you use nighly build jars. 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. -- Amila Suriarachchi, WSO2 Inc.
Re: OMElement Vs java.lang.Object for (xsd:anyType) - Axis 1.3 Vs Axis 2 code generation
basically you are asking when is the Axis2 1.4. we have just release Axis2 1.3 so it would be from another 3 or 4 months time. Amila. On 8/22/07, Raghu Upadhyayula [EMAIL PROTECTED] wrote: Hi Amila, It worked with the nightly build jars (adb.jar adb-codegen.jar). When will this change be moved to the main release (I mean which Axis2 version)? Thanks Raghu -- *From:* Amila Suriarachchi [mailto:[EMAIL PROTECTED] *Sent:* Monday, August 20, 2007 9:36 PM *To:* axis-user@ws.apache.org *Subject:* Re: OMElement Vs java.lang.Object for (xsd:anyType) - Axis 1.3Vs Axis 2 code generation On 8/17/07, *Raghu Upadhyayula* [EMAIL PROTECTED] wrote: 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. it is only available in trunk. you can try this, get a nighly build and replace adb-codgen.jar and adb.jar with the nightly build jars. Then it should work. 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 yes, if you use nighly build jars. 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.3Vs 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] 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. -- Amila Suriarachchi, WSO2 Inc. -- Amila Suriarachchi, WSO2 Inc.
Re: OMElement Vs java.lang.Object for (xsd:anyType) - Axis 1.3 Vs Axis 2 code generation
On 8/17/07, Raghu Upadhyayula [EMAIL PROTECTED] wrote: 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. it is only available in trunk. you can try this, get a nighly build and replace adb-codgen.jar and adb.jar with the nightly build jars. Then it should work. 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 yes, if you use nighly build jars. 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.3Vs 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] 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. -- Amila Suriarachchi, WSO2 Inc.
RE: OMElement Vs java.lang.Object for (xsd:anyType) - Axis 1.3 Vs Axis 2 code generation
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.
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] 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.
