Re: AXIS2-199 Jira Issue-Non-compilable data binding code generated - duplicate 'toOM(...)' method

[jayachandra]

Hi,

I've just quickly gone through the wsdl and xsd, and I see no definition for DataObjectSet inside the xsd file. You sure, with this xsd file Axis 1.2 worked without throwing an error that reads something like {"http://www.issinc.com/gateway/services"}DataObjectSet is referenced but not defined
 

Jaya

P.S:: Provide this element definition in the schema and once run Axis2 wsdl2java you would surely get a XMLBeans object in place of org.apache.axis2.om.OMElement type param as input to toOM() method
 

On 9/13/05, Lakshmi Chaparala <[EMAIL PROTECTED]> wrote:

Hi

 

 I am seeing other errors, other than duplicate toOM metods(). I understand that input parameters are different, but the second toOM() method that takes OMElement param input does not have param. newXMLStreamReader() method and so it would not compile.

 

Here is my WSDL and the XSD that worked as they are in Axis 1.2 version.

 

Also I have attached the DataBindingSupporter class that was generated from WSDL2JAVA and would not compile as those methods do not exist in OMElement. All generated supporter classes have similar errors; I just attached one such class.

 

Appreciate your time.

 

Thanks

 

 

Lakshmi

 

---

From: jayachandra [mailto: [EMAIL PROTECTED]]
Sent: Tuesday, September 13, 2005 7:54 AM
To: axis-user@ws.apache.org
Subject: Re: AXIS2-199 Jira Issue-Non-compilable data binding code generated - duplicate 'toOM(...)' method

 

As per my understanding of how databinding works in Axis2, there would usually be multiple toOM(...) methods generated. But none of them is a duplicate of the other. The input parameter type varies for each method. You sure you got a *duplicate* pair of toOM(...) method signatures?

If so, a wsdl to replicate the issue can help the Axis2 folks to fix it.
 

Thanks

jaya
 

On 9/13/05, Lakshmi Chaparala < [EMAIL PROTECTED]> wrote:

Hi,

I still see the same bug when I run WSDL2JAVA, your JIRA site shows that this bug has been fixed and checked in and affected version is 0.91. I got the latest code from SVN. What version has this bug fix checked into?

 

Thanks

Lakshmi

--
-- Jaya

--
-- Jaya