[
https://issues.apache.org/jira/browse/CXF-3906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Melloware closed CXF-3906.
--------------------------
Resolution: Fixed
Fix Version/s: Invalid
Discovered the reason was due to my XMlRootElement having the same name as my
WebResult. THis caused it to generate ref= instead of type =
> Java First WSDL Generation Incorrect in 2.4.3 vs 2.1.10
> -------------------------------------------------------
>
> Key: CXF-3906
> URL: https://issues.apache.org/jira/browse/CXF-3906
> Project: CXF
> Issue Type: Bug
> Components: JAXB Databinding
> Affects Versions: 2.4.3
> Environment: Java 6,7 on Windows 7 and Suse Linux 11
> Reporter: Melloware
> Labels: cxf, java2wsdl, jaxb
> Fix For: Invalid
>
> Attachments: cxf-3906.zip
>
>
> I have been using CXF since 2008 version 2.1.x branch. It generated the same
> WSDL every time which I have attached and labeled wsdl-211.wsdl. I recently
> upgraded to 2.4.3 and did not touch the interface and now CXF is generating
> the WSDL differently that is now breaking all my test clients.
> The major difference being it is generating ref= instead of type= which is
> then causing the client generation to generate SoapStyle.BARE in both my Java
> and .NET clients.
> 2.1.10:
> <xs:complexType name="getAllAceResponse">
> <xs:sequence>
> <xs:element minOccurs="0" name="collectionActualValueData"
> type="tns:collectionActualValueData" />
> </xs:sequence>
> </xs:complexType>
> 2.4.3:
> <xs:complexType name="getAllAceResponse">
> <xs:sequence>
> <xs:element minOccurs="0" ref="tns:collectionActualValueData"/>
> </xs:sequence>
> </xs:complexType>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
