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

[Lakshmi Chaparala]

Hi JayaChandra,   Any insight into the issue I have generating from WSDL2JAVA? I am once again including WSDL and XSD files. This time XSD has a DataObjectSet definition in it which was previously missing. It generates exact same code that would not compile.     Thanks   Lakshmi Chaparala Software Engineer Intelligent Software Solutions Phone:(719)234-0682 Email:[EMAIL PROTECTED]   From: jayachandra [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 14, 2005 6:07 AM To: [EMAIL PROTECTED] Cc: Ajith Ranabahu Subject: Re: AXIS2-199 Jira Issue-Non-compilable data binding code generated - duplicate 'toOM(...)' method   Yes Ajith, you are right. I smelled the same.   @Lakshmi, As requested earlier, can you give DataObjectSet element definition in your xsd and run the wsdl2Java once again and let us know if it fails?   Thanks Jaya   On 9/14/05, Ajith Ranabahu <[EMAIL PROTECTED]> wrote: Hi, Have a look at the following lines from the WSDL <wsdl:message name="CompositeQueryResponse">         <wsdl:part name="dataObjectSet" element="types:DataObjectSet"/>     </wsdl:message>     <wsdl:message name="GetRelationshipsRequest">         <wsdl:part name="DataObjectSet" element="types:DataObjectSet"/>     </wsdl:message>     <wsdl:message name="GetRelationshipsResponse">         <wsdl:part name="dataObjectsWithRelationships" element="types:DataObjectSet"/>     </wsdl:message> The referenced type DataObjectSet is missing in the XSD and that's what's breaking the code generator. Unfortunately we don't have a validation yet :(   On 9/14/05, Ajith Ranabahu <[EMAIL PROTECTED] > wrote: Hi, I'll have to run the WSDL for myself to see whether it works (rather not work!) but here's a bit of info about the possible scenario. 1. I need to change this one of these days but right now the default object is OMElement. Say the code generator finds a parameter that it cannot match in the typemapper, it puts OMElement there. So in this case that's what probably happened. (The code generator did not pick up a proper QName !!!). 2. The code generator (Actually the WOM) does not handle fault (wsdl:fault) properly. I need to fix that too. However it's unlikely that it's the cause of this problem. Will invetigate this further and let you guys know. On 9/13/05, jayachandra <[EMAIL PROTECTED] > wrote: 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 -- Ajith Ranabahu -- Ajith Ranabahu -- -- Jaya

GWQuery.xsd
Description: Binary data

GWQuery.wsdl
Description: Binary data