Hmm... That's not good. I more or less expected that to work. Not sure
why it wouldn't be..
Ok. Couple questions:
1) Are you throwing this from your impl, and interceptor, or a jaxws
handler?
2) Are you using the JAXWS frontend or the simple frontend?
3) Any chance you could try 2.0.4 (released today)?
If it's jaxws, you COULD try building up and throwing a
javax.xml.ws.soap.SOAPFaultException, but that kind of sucks.
Dan
On Monday 28 January 2008, Azazelus wrote:
> dkulp wrote:
> > Can you try the SOAP specific subclass of Fault:
> >
> > org.apache.cxf.binding.soap.SoapFault
> >
> > The SOAP binding converts generic "Fault"s into SoapFaults and I
> > think it specifically maps generic faults to either soap:Server or
> > soap:Client. If you need to manipulate the SOAP fault stuff, you
> > need to use the specific subclass.
> >
> > Dan
>
> It seems it doesn't work either. I am extending
> org.apache.cxf.binding.soap.SoapFault and calling its constructor:
>
> public IndexResultSetFaultMessage(String faultInfo, String
> faultCode) { super(faultInfo, new QName(faultCode));
> }
>
> As a result faultInfo is set properly but faultCode remains
> soap:Server unchanded.
> Any other thoughts?
> az
--
J. Daniel Kulp
Principal Engineer, IONA
[EMAIL PROTECTED]
http://www.dankulp.com/blog
