Hi Lars, So the camel endpoint you have at the end of the route is a cxf endpoint, as you talk about a SOAP fault from the end of the route?
In a request-response scenario, you will get the SOAP fault transferred back to the other end of the route and this is typically returned as an HTTP 500 SOAP Fault to the caller by the cxf-endpoint. But you could technically change the fault/response message somewhere in the path to e.g., change the HTTP code, or its response body, etc if that is required. An unchecked exception during the processing after the cxf-endpoint takes the message will result in a SOAP fault from the cxf-endpoint and consequently you will see the SOAP fault message at your client. But if the exception occurs before entering the cxf endpoint (e.g., your client didn't even reach the cxf endpoint), you will get a different HTTP error response 404 etc. regards, aki 2012/12/13 helander <leh...@gmail.com>: > Aki, thanks for the feedback. > > At the moment I am only using request/response (InOut). > > If the service (called by the end of the route) returns a SOAP Fault, will > then the cxf-endpoint make sure that the http status code returned to the > caller becomes 500? > > Do the cxf-endpoint force the return of any other 4xx/5xx code? If so, in > which situations? > > Do the cxf-endpoint ever create a SOAP Fault or does it only return SOAP > Faults originating from the service implementation? If the cxf-endpoint > creates SOAP Faults, under which circumstances does this happen? > > Thanks > > Lars > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Error-handling-when-using-camel-cxf-tp5723955p5724021.html > Sent from the Camel - Users mailing list archive at Nabble.com.
