Is it by design Headers will not be propagated to next component in the
route, after the bean component in the route?
We are trying to process a message on queue, with a custom header set used
as correlation id, which will invoke two bean components in pipeline. Based
on the response from the pipline the status should be updated in the
database using the the customer header set on the original message.
Route defenition:
//STUDENT_ID header set on send
from("activemq:queue:provider2AsyncQueue")
.unmarshal().xstream()
.pipeline(
"bean:PROVIDER2_TRANSFORMER",
"bean:PROVIDER2?methodName=executeRequest",
"activemq:queue:updateThirdPartyProvisioningStatus");
//UPDATE STATUS AFTER PROCESSING THE THIRD PARTY REQUEST
from("activemq:queue:updateThirdPartyProvisioningStatus")
.process(new Processor(){
public void process(Exchange arg0) throws Exception {
System.out.println( arg0.getIn().getHeader("STUDENT_ID"));
}
});
I am not able retrive the STUDENT_ID header while processing
"bean:PROVIDER2?methodName=executeRequest" or processing the
"activemq:queue:updateThirdPartyProvisioningStatus"
The header is available to the PROVIDER2_TRANSFORMER.
Please provide some advice.
--
View this message in context:
http://www.nabble.com/Missing-Headers-in-pipline-with-bean-components-tp17234481s22882p17234481.html
Sent from the Camel - Users mailing list archive at Nabble.com.
