Exchange Context properties are not propagated across SwitchYard services using SCA reference binding
Issue
- I have a SwitchYard service (Service A) that uses a Camel XML implementation and SCA service/reference bindings.
- In this camel route, I use the
<setProperty>
tag to set a property on theExchange
. Also in this camel route, there is a<to>
tag that invokes an external SwitchYard service (Service B), which is in a separate JAR file. -
Here is the definition of the camel route:
<route> <from uri="switchyard://ServiceA"/> <setProperty propertyName="PROPERTY"> <constant>Yes</constant> </setProperty> <to uri="switchyard://ServiceB"/> </route>
-
According to the message tracer (
org.switchyard.handlers.MessageTraceHandler
), the last step of Service A before it goes to Service B, all the context properties look good. Thenorg.apache.camel.processor.FilterProcessor
prints the exchange which is just a message body. - Then the message tracer prints the first step in Service B. This printing has many of the context properties removed including the properties I set in the route, i.e.
PROPERTY=Yes
. - How do I get some properties to propagate from Service A to Service B?
Environment
- Red Hat JBoss Fuse Service Works (FSW)
- 6.x
- SwitchYard SCA Binding
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.