That is per the JAX-WS specification, the SOAP client (your first web
service provider in this case) will receive only SOAP faults from the
second WSP in case of system or any other exceptions. Normally for
non-client created system exceptions the WSP having the exception
(either 1st or 2nd) should be sending only another SOAP fault with a
generic "something bad happened, contact support" error message to the
client that called it (either the original WSC or the 1st WSP) while
writing the inner details about the exception in the exception-raising
WSP's log. I.e., you don't want to broadcast internal error details
about a WSP to the client calling it, as that can give Bad Guy Hacker
useful information about the workings of your system.
Glen
On 08/03/2012 06:23 AM, anoordover wrote:
I have a webservice which calls another soap-service.
If there is a systemexception is raise when I call this soap-service I want
to throw the same exception from the first soap-service.
So i don't want to receive a soap-fault.
I can't get this to work. I always get a soap-fault when i call the first
soap-service.
--
View this message in context:
http://cxf.547215.n5.nabble.com/raise-exception-tp5711982.html
Sent from the cxf-user mailing list archive at Nabble.com.
--
Glen Mazza
Talend Community Coders
coders.talend.com
blog: www.jroller.com/gmazza
