camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sengel <>
Subject Missing "detail" element in SOAP fault
Date Tue, 18 Oct 2011 12:41:41 GMT

we have a system consisting of (web and other) clients and our backend (SOAP
web services). Now when we throw a Fault/Exception in a backend operation,
the SOAP fault looks like this:

<env:Envelope xmlns:env="">
         <faultstring>An entity with the same ID already
               <reason>Entity was not created. An entity with the same ID
already exists</reason>

The client side uses the subelement "duplicateEntityFault" of "detail" to
generate the Exception class which we expect and catch

So now we added Camel to the setup which routes requests to the backend. We
expected that if a Fault/Exception is thrown on the backend, Camel would
just pass it back to the client. But, no. Instead the client gets this:

<soap:Envelope xmlns:soap="">
         <faultstring>HTTP operation failed invoking with statusCode:

So the problem is that there is no "detail" element in the fault message
from which the client can generate the Exception. Camel logs this:
Exhausted after delivery attempt: 1 caught:
org.apache.camel.component.http.HttpOperationFailedException: HTTP operation
failed invoking with
statusCode: 500

Could you please tell us what is missing or what we do wrong?
Thanks in advance,


View this message in context:
Sent from the Camel - Users mailing list archive at

View raw message