Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: neutral (athena.apache.org: 216.139.236.26 is neither permitted
 nor denied by domain of eric.bender@gmail.com)
Date: Wed, 4 Apr 2012 11:36:37 -0700 (PDT)
From: Castyn <eric.bender@gmail.com>
To: users@camel.apache.org
Message-ID: <1333564597016-5618665.post@n5.nabble.com>
Subject: Detecting SOAP Faults
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I currently have a custom processor setup within a route that does the
following


public class SoapFaultDetectionProcessor implements Processor {

	public void process(Exchange exchange) throws Exception {
		if(exchange.getIn().isFault()) {
			SoapFault fault = exchange.getIn().getBody(SoapFault.class);
	        System.out.println(fault.getMessage());
		}
	}
}

This processor immediately follows a CXF Producer in POJO mode.  I am having
the service generate a soap fault, but for some reason the isFault() call
always remains false.  

1) Am I not using this properly or
2) Is there a better way to capture and manipulate / display SOAP faults
(for logging purposes and such)

--
View this message in context: http://camel.465427.n5.nabble.com/Detecting-SOAP-Faults-tp5618665p5618665.html
Sent from the Camel - Users mailing list archive at Nabble.com.