That is not true. If the element is named "string" and part of a
sequence, ADB doesn't generate anything called String, but only
methods called setString and getString. There is no conflict here. If
the element is a root element, ADB will indeed generate a class called
String, but since it is in a different package than java.lang and the
ADB generated code uses fully qualified class names everywhere, there
is again no conflict here. For names that match a Java primitive type,
ADB is smart enough to add an underscore to avoid name collisions. It
seems that the only case that is not addressed is collision with the
getClass method.

Andreas

On Wed, Aug 12, 2009 at 16:42, Asen<[email protected]> wrote:
> Excuse my jumping into this, but the same would happen if the the element
> name is as
> <xs:element name="string" ... /> and the generated 'String' extending the
> ADB binding will conflict
> with the java.lang.String class.
> I think this is a limitation of the ADB binding.
> I have not experienced this problem when using the JiBX bindings with Axis2.
> I have not tried that yet,  but you may try to tweak the ADB binding as per
> [1].
>
> [1] http://ws.apache.org/axis2/1_5/adb/adb-tweaking.html
>
>
> On Wed, Aug 12, 2009 at 9:22 AM, <[email protected]> wrote:
>>
>> Hi folks,
>> I am generating from a wsdl Client Server Java code, by using the
>> axis2-wsdl2code-maven-plugin.
>> The wsdl file contains the following element:
>> <xs:complexType name="ErrorReportType">
>> <xs:sequence>…  <xs:element name="Class" form="unqualified"
>> type="xs:string"/>… </xs:sequence>
>> </xs:complexType>
>>
>> While compilation phase a class named  “ErrorReporType” containing a field
>> named “Class”,  and the getter and setter methods are tried to be generated,
>> without success. The compilation of the stub failures with the message
>> “…myPackage.MyStub.ErrorReportType cannot override getClass()”
>>
>> The problem is the wsdl element "Class" as shown above and final declared
>> method getClass()on java side. Is there any chance to solve this problem?
>>
>>
>> I would appreciate any hints…
>>
>> Thanks
>> Ike
>
>

Reply via email to