cxf-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Kulp <>
Subject Re: cxf codegen custom bindings for exception message parts
Date Wed, 02 May 2012 17:24:05 GMT

First off, the WSDL would be invalid.   If the fault is "literal" (which you 
would want it to be), then the <wsdl:part> in the message MUST be an 
element, not a type.   This wsdl should likely be completely rejected.

If you fix that and it's still an issue, can you file a JIRA with a small 
test case?  It definitely should either display an error at code generation 
time of generated compilable code.


On Wednesday, May 02, 2012 08:11:21 AM utuba wrote:
> I have the following situation I cannot seem to resolve a way of
> customising the bindings when using the plugin to generate a wsdl.  The
> fragment which I'm trying to customise is:
> Which is used in the wsdl port type:
> and specificed in the wsdl binding:
> The problem I'm having is that the generated exception type for this does
> not compile as several of the constructors have a duplicate parameter,
> e.g.:
> I'm unable to edit the wsdl to change the parameter name, but cannot work
> out how to change the name of the generated parameter with jaxws bindings
> so it is not a duplicate.  Any suggestions as to whether this is possible
> would be much appreciated.
> Thanks.
> --
> View this message in context:
> -message-parts-tp5680813.html Sent from the cxf-user mailing list archive
> at
Daniel Kulp -
Talend Community Coder -

View raw message