Custom exception fields do not propagate over clustered SCA binding in SwitchYard

Solution Verified - Updated -

Issue

  • We are trying to implement a solution based on 2 SwitchYard projects where an SCA invocation between the two projects takes place. We are invoking a Bean component from the other project’s Camel component using an SCA clustered binding. Our invoked service can throw a ServiceException (our own customized exception). We created that exception because, among other reasons, we want to pass an error code to the invoking Camel component so that the error can be treated according to this code.
  • The problem with our solution is that if the SCA binding and reference are declared as a clustered binding / reference, the error code is not passed to the Camel component or the exception handler declared in that Camel component. However if we declare the binding as local (not clustered) service the error code is passed fine to the exception handler registered to the Camel route.
  • This seems like a bug. If that is not the case, how can we implement a solution that meets our needs and expectations?

Environment

  • Red Hat JBoss Fuse Service Works (FSW)
    • 6.0.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content