The objects generated by wsdl2java for faults seem unnecessarily clumsy.
I get a POJO + annotations that corresponds to the fault type. Call it
'X'.
Then I get XFault.
To construct an XFault over a Throwable, I need to provide a message ---
(String message, X x, Throwable cause)
Hi,
The artifacts generated by wsdl2java is JAX-WS 2.0 compliant, so
everything generated by the tool is defined in the spec.
Not really know the exact request here.
Do you mind send your sample wsdl, and tell us what kind of artifacts
you're looking for
If there's bug to fix or improvements
es Mao [mailto:[EMAIL PROTECTED]
> Sent: Thursday, August 30, 2007 10:43 PM
> To: cxf-user@incubator.apache.org
> Subject: Re: wsdl2java and faults
>
> Hi,
>
> The artifacts generated by wsdl2java is JAX-WS 2.0 compliant, so
> everything generated by the tool is defined in
Hi Benson ,
This class is generated as per Jaxws spec 2.5 .
I think the string message in constructor is useful if there is no
message in X to tell us what the fault is or where throw this fault .
The below is the sample we use the message to indicate where cause this
error :
thro
gt; Sent: Thursday, August 30, 2007 10:43 PM
> > To: cxf-user@incubator.apache.org
> > Subject: Re: wsdl2java and faults
> >
> > Hi,
> >
> > The artifacts generated by wsdl2java is JAX-WS 2.0 compliant, so
> > everything generated by the tool is defined in the spe
cranky at 11pm.
> -Original Message-
> From: Daniel Kulp [mailto:[EMAIL PROTECTED]
> Sent: Friday, August 31, 2007 12:13 PM
> To: cxf-user@incubator.apache.org
> Cc: Benson Margulies
> Subject: Re: wsdl2java and faults
>
>
> Benson,
>
> The "
