You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Mike Lenner (JIRA)" <ji...@apache.org> on 2008/09/05 21:26:44 UTC
[jira] Created: (CXF-1786) wsdl2java utility throws exception on
naming collision - "Two declarations cause a collision in the ObjectFactory
class"
wsdl2java utility throws exception on naming collision - "Two declarations cause a collision in the ObjectFactory class"
------------------------------------------------------------------------------------------------------------------------
Key: CXF-1786
URL: https://issues.apache.org/jira/browse/CXF-1786
Project: CXF
Issue Type: Bug
Components: Tooling
Affects Versions: 2.1.2
Environment: RHEL 4.x
Reporter: Mike Lenner
wsdl2java utility throws exception on naming collision. I've isolated which part of the WSDL causes this error. Using the below <schema> excerpt, the tool will through the exception referenced in the title of this issue.
wsdl excerpt:
<wsdl:types>
<xsd:schema ...>
<xsd:element name="accountID">
<xsd:simpleType>
<xsd:restriction base="xsd:string"/>
</xsd:simpleType>
</xsd:element>
<xsd:complexType name="Account">
<xsd:sequence>
<xsd:element minOccurs="0" name="ID" nillable="true" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
</wsdl:types>
Seems there is some issue when an element 'accountID' and an element 'Account' with a sub element 'ID' are both present. The following exception is thrown:
WSDLToJava Error: Thrown by JAXB : Two declarations cause a collision in the ObjectFactory class.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-1786) wsdl2java utility throws exception on
naming collision - "Two declarations cause a collision in the ObjectFactory
class"
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp resolved CXF-1786.
------------------------------
Resolution: Invalid
Fix Version/s: Invalid
This is a JAXB issue. You need to use a jaxb binding file to remap duplicate things to new names. That's completely per jaxb/jaxws spec.
> wsdl2java utility throws exception on naming collision - "Two declarations cause a collision in the ObjectFactory class"
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: CXF-1786
> URL: https://issues.apache.org/jira/browse/CXF-1786
> Project: CXF
> Issue Type: Bug
> Components: Tooling
> Affects Versions: 2.1.2
> Environment: RHEL 4.x
> Reporter: Mike Lenner
> Fix For: Invalid
>
>
> wsdl2java utility throws exception on naming collision. I've isolated which part of the WSDL causes this error. Using the below <schema> excerpt, the tool will through the exception referenced in the title of this issue.
> wsdl excerpt:
> <wsdl:types>
> <xsd:schema ...>
> <xsd:element name="accountID">
> <xsd:simpleType>
> <xsd:restriction base="xsd:string"/>
> </xsd:simpleType>
> </xsd:element>
> <xsd:complexType name="Account">
> <xsd:sequence>
> <xsd:element minOccurs="0" name="ID" nillable="true" type="xsd:string"/>
> </xsd:sequence>
> </xsd:complexType>
> </xsd:schema>
> </wsdl:types>
> Seems there is some issue when an element 'accountID' and an element 'Account' with a sub element 'ID' are both present. The following exception is thrown:
> WSDLToJava Error: Thrown by JAXB : Two declarations cause a collision in the ObjectFactory class.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.