As Amila pointed out your WSDL is invalid, hence I don't think you can do anything about it other than changing your WSDL.
Thanks, Keith. On Mon, Feb 2, 2009 at 6:33 AM, Thallapragada, Sowmi <[email protected]>wrote: > Can anyone please help me with this issue? > > ------------------------------ > *From:* Thallapragada, Sowmi > *Sent:* Thu 1/29/2009 10:42 AM > *To:* [email protected] > *Subject:* [Axis2 1.4.1] WSDL2Java difference Vs. Axis2 1.3 > > I notice that in Axis2 1.3 the WSDL2Java allowed duplicate element > definitions by renaming (by appending a number at the end), but 1.4.1 just > generates methods with the same name. This is causing compilation errors & > causing backward compatibility issues. > > > > Eg. > > > > *<xsd:element name="averageSpeed" type="xsd:int" />* > > <xsd:element name="postedSpeed" type="xsd:int" /> > > <xsd:element name="slowestSpeed" type="xsd:int" /> > > *<xsd:element name="averageSpeed" type="xsd:int" />* > > > > In 1.3 this generated 2 methods called "getAverageSpeed()" & > "getAverageSpeed0()", but in 1.4.1 it generates two methods called > "getAverageSpeed()" and so the compilation fails. > > > > Can you confirm this? Is there an option I can pass to 1.4.1 WSDL2Java to > allow the duplicate element definition? > > > > At this point, changing the schema to eliminate the duplicate element is > not an option, so I am looking forward to your help. > > > > Regards, > > Sowmi > > > -- Keith Chapman Senior Software Engineer WSO2 Inc. Oxygenating the Web Service Platform. http://wso2.org/ blog: http://www.keith-chapman.org
