[SMXCOMP-570] Allow exceptions to be handled as JBI faults

• Type: New Feature
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Fix Version/s: 2013.02
• Component/s: servicemix-common
• Patch Info: Patch Available
• Assignee: Unassigned
• Reporter: Trevor Pounds
• Created: 15/Jun/09 20:50
• Updated: 10/Dec/12 10:11

Description

When an exception is thrown in a provider endpoint impl it is handled as a JBI error in most cases. Howeverm in some cases (i.e. SAXParseException) it may be useful to translate these exceptions into a JBI fault message which can then be handled by the exchange if needed. I've provided a simple patch to the base ProviderEndpoint class to provide setting exceptiosn that will be handled as JBI faults.

The following are a few examples of how the xbean.xml can be configured to handle exceptions:

<saxon:xslt
   service="example:myService"
   endpoint="myXSLT"
   resource="classpath:myDocument.xsl"
   handleExceptionsAsFault="java.lang.Exception"/>


<eip:message-filter
   service="example:myService"
   endpoint="myEIP"
   handleExceptionsAsFault="java.lang.Exception">
   <eip:target>
      <eip:exchange-target service="canonical:mte-pipeline" endpoint=""/>
   </eip:target>
   <eip:filter>
      <eip:xpath-predicate xpath="not(/FOO or /BAR)" namespaceContext="#nsContext"/>
   </eip:filter>
</eip:message-filter>

Issue Links

• supercedes: SMXCOMP-125 Saxon component should gracefully handle malformed XML messages

Sub-Tasks

• EIP Filter should propagate exceptions: Open
• EIP pattern to re-route the flow in case of an error / fault.: Open