Not sure if this is helpful but we've used this approach to get the
detailed exception coming back over the wire from the service side.

http://io.typepad.com/eben_hewitt_on_java/2009/07/using-soap-faults-and-exceptions-in-java-jaxws-web-services.html

Mark *
*


On Thu, Sep 19, 2013 at 12:23 PM, James Green <[email protected]>wrote:

> This along the lines you are referring to?
>
> http://i-proving.com/2008/11/03/adding-an-interceptor-to-the-cxf-fault-chain/
>
>
>
> On 19 September 2013 16:45, Daniel Kulp <[email protected]> wrote:
>
> >
> > A simple interceptor at the beginning of the  FaultOutChain on the server
> > side can grab the exception from the Message, log it, and replace that
> > exception with a new Exception with a new message.
> >
> > Dan
> >
> >
> >
> > On Sep 19, 2013, at 6:10 AM, James Green <[email protected]>
> wrote:
> >
> > > We have a Spring XML-config powered application that includes a CXF
> > powered
> > > JAX-WS service.
> > >
> > > The trouble is, the service currently intercepts RuntimeExceptions and
> > > throws them as SoapFaultException with the message passed through. This
> > may
> > > be the spec, but it's certainly not helpful to us.
> > >
> > > So I'd like to change this behaviour thus:
> > >
> > > 1. I want to log the fault on the server
> > > 2. I want SoapFaultException messages to read more along the lines of
> > > "Temporary fault. Please try again later."
> > >
> > > I really don't want us airing dirty laundry like database connection
> > faults
> > > or SQL faults in public. Unfortunately, catching Exception inside our
> > > service methods does not work.
> > >
> > > So reading around CXF has interceptors. What I don't see is how to use
> > this
> > > to override the default behaviour. Is there a tutorial that I'm
> missing?
> > >
> > > I'm having trouble imagining this default behaviour is desired by many
> > > companies so I'm slightly surprised this isn't a hot topic...
> > >
> > > TIA
> > >
> > > JAmes
> >
> > --
> > Daniel Kulp
> > [email protected] - http://dankulp.com/blog
> > Talend Community Coder - http://coders.talend.com
> >
> >
>

Reply via email to