Mailing-List: contact users-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cxf.apache.org
Received-SPF: pass (nike.apache.org: domain of ashakirin@talend.com designates
 64.95.72.241 as permitted sender)
From: Andrei Shakirin <ashakirin@talend.com>
To: "users@cxf.apache.org" <users@cxf.apache.org>
CC: "mandys.inbox@gmail.com" <mandys.inbox@gmail.com>
Subject: RE: How to handle exceptions from a SOAP webservice in a single
 point
Thread-Topic: How to handle exceptions from a SOAP webservice in a single
 point
Thread-Index: AQHOtXrEKjhbnlsbZUGCRuismr0ER5nNzwgAgAAKU4CAALmHUA==
Date: Fri, 20 Sep 2013 12:46:53 +0000
Message-ID: <D225CD69196F3F4A9F4174B2FCA06F8811C0394C@S10BE002.SH10.lan>
References: 
 <CAMdPgUL1Z=r61snU+XJSdxUTi9RYL2dVP8kBwPgpu0feSTkMug@mail.gmail.com>
 <523B6642.8060305@gmail.com> <78FFB0F9-8F0A-44C5-B256-063C8295DB65@gmail.com>
In-Reply-To: <78FFB0F9-8F0A-44C5-B256-063C8295DB65@gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Hi,

Regarding the first question you can do something like:

			fault =3D (SOAPFactory.newInstance()).createFault();
			fault.setFaultString(BUSINESS_FAULT_STRING);
			String errorString =3D businessException.getMessage();
			try {
				// 2. Parse exception string and add it as SOAPFault Details
				Document faultDoc =3D builder.parse(new ByteArrayInputStream(
						errorString.getBytes()));
				Detail detail =3D fault.addDetail();
				Document owner =3D detail.getOwnerDocument();
				Node details =3D owner.importNode(faultDoc.getDocumentElement(), true);
				detail.appendChild(details);
			} catch (SAXException e) {
				// 3. If exception string is not XML, set is as fault string
				fault.setFaultString(errorString);
			}
			return new SOAPFaultException(fault);


Regards,
Andrei.

> -----Original Message-----
> From: Mandy Warren [mailto:mandys.inbox@gmail.com]
> Sent: Donnerstag, 19. September 2013 23:39
> To: users@cxf.apache.org
> Subject: Re: How to handle exceptions from a SOAP webservice in a single
> point
>=20
> Many thanks again for such a fast reply! So I have written an
> AbstractSoapInterceptor and managed to retrieve the exception from the
> message via
>=20
> Exchange exchange =3D message.getExchange;
>=20
> exchange.get(Exception.class);
>=20
> Pls can you explain how I then create a Fault with the info I want and se=
nd it
> back?
>=20
> Also because I want to use local transport I was looking at using
> SOAPHandlers instead of in interceptors to pull out some header info I ne=
ed,
> is there a way to get / change the exception info from the handler instea=
d of
> via an interceptor?
>=20
> Many thanks
>=20
> Sent from a mobile device
>=20
> On 19 Sep 2013, at 22:01, Sergey Beryozkin <sberyozkin@gmail.com> wrote:
>=20
> > Hi
> > On 19/09/13 21:56, Mandy Warren wrote:
> >> Hi,
> >>
> >> I would like to handle all exceptions thrown by my webservice in a
> >> single point so I can create Faults with specific codes / strings
> >> based on info in the exception. When using JAX-RS I can do this very
> >> neatly via an Exception Mapper (and then convert to a REST response)
> >> but there doesn't seem to be an equivalent for JAX-WS..
> >>
> >> Is there a way to handle the exceptions before they are turned into
> >> SOAP Faults?
> > See
> >
> > http://cxf.547215.n5.nabble.com/Implementing-smarter-
> RuntimeException-
> > handling-for-JAX-WS-service-tt5734264.html
> >
> > HTH
> > Sergey
> >> Many thanks
> >> Mandy
> >