cxf-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Freeman Fang <>
Subject Re: Exception used as ComplexType name
Date Thu, 05 May 2011 06:20:45 GMT

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.


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.
> --
> View this message in context:
> Sent from the cxf-user mailing list archive at

Freeman Fang

Twitter: freemanfang
Connect at CamelOne May 24-26
The Open Source Integration Conference

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message