Hi,
I believe this is a known issue[1], which is already fixed by cxf
2.3.3 and 2.4, could you use latest released version?
[1]https://issues.apache.org/jira/browse/CXF-3353
Freeman
On 2011-5-2, at 下午5:45, swastb wrote:
Hi,
We have used Exception as ComplexType in XSD,
<xsd:complexType name="Exception">
<xsd:sequence>
<xsd:element name="message" nillable="true"
type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="ws_Test" type="tns:ws_Test/>
<xsd:element name="ws_TestResponse" type="tns:ws_TestResponse"/>
<xsd:element name="Exception" type="tns:Exception"/>
</xsd:schema>
<wsdl:fault name="Exception">
<soap:fault name="Exception" use="literal"/>
</wsdl:fault>
When we use wsdl2java, a class named Exception_Exception is getting
generated which extends Exception.Now this class should extend
java.lang.Exception. But since one class called Exception is also
getting
generated we are getting compile error in Exception_Exception. Any
idea why
the classes are getting generated like this? I am using apache cxf
2.3.2.
--
View this message in context:
http://cxf.547215.n5.nabble.com/Exception-used-as-ComplexType-name-tp4364282p4364282.html
Sent from the cxf-user mailing list archive at Nabble.com.
---------------------------------------------
Freeman Fang
FuseSource
Email:[email protected]
Web: fusesource.com
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com
Connect at CamelOne May 24-26
The Open Source Integration Conference
