Hi,
Yeah, we also need address it in client/server main process class,
created CXF-3491[1] to track this issue, the fix is coming soon.
Btw, the issue comes from that you use same namespace both for wsdl
and type, and in the type use Exception for the fault, IMHO both are
not good practice, you should use more meaningful name for the fault
and also should use different namespace for wsdl and type, so that
the client/server main class and fault class won't be in same
package, which in turn this conflict won't happen.
[1]https://issues.apache.org/jira/browse/CXF-3491
Freeman
On 2011-5-5, at 下午1:00, swastb wrote:
Hi,
I have added the CXF path correctly to the Env variable. Because in
the
generated code I can see Apache CXF 2.3.4 is being used.
/**
* This class was generated by Apache CXF 2.3.4
* 2011-05-05T10:20:54.199+05:30
* Generated source version: 2.3.4
*
*/
Even the CXF-3353 is also partially resolved. The problem occours
only when
any we try to generate stub along with server or client code. For
reference
i have attached the generated
WspLookUpPortType_DNBWebServicesProvidersLookUpWspLookUpPort_Server
.java
file along with the WSDL. Your help is really appreciated.
http://cxf.547215.n5.nabble.com/file/n4371941/wsdl_Server.zip
wsdl_Server.zip
--
View this message in context:
http://cxf.547215.n5.nabble.com/Exception-used-as-ComplexType-name-tp4364282p4371941.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
