WSDL2Java: Different class mappings of nested complex types with identical names with JDKs of different vendors

we ran in to some problems developing an Axis2 webservice client in SUN JDK and trying to build the same in IBM JDK
The WSDL of the Web service contains following nested type definitions with
identical names:

<xsd:complexType name="NameDetails">
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="NameDetails">
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="0" name="xxx" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="0" name="yyy" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>

In Sun jDK,
<xsd:complexType name="NameDetails"> is created as NameDetails_type0 and
<xsd:element maxOccurs="unbounded" minOccurs="0" name="NameDetails"> is created as NameDetails_type1

In IBM JDK,
<xsd:complexType name="NameDetails"> is created as NameDetails_type1 and
<xsd:element maxOccurs="unbounded" minOccurs="0" name="NameDetails"> is created as NameDetails_type0

As a result source code that accesses these classes is affected and has to be adapted for the JDKs of
both vendors.

Is there any fix for this? or any workaround?