Sorry, in this thread i was talking about the
org.apache.servicemix.components.util.ChainedComponent and not about the
org.apache.servicemix.components.util.PipelineComponent.
Guillaume
Guillaume Nodet wrote:
You can use the
org.apache.servicemix.components.util.PipelineComponent, which can be
used to pipeline multiple components using in-out requests : each
component will receive in input the output of the previous component
in the list.
Another way is to use in-only exchanges and define the destinationXXX
attributes on the activation spec.
Nearly all lightweight components support using in-only for request /
response exchanges : in these cases,
the output is sent in an in-only exchange to the configured
destination. The main problem of such a thing, it that
it will be difficult to do that in a synchronous manner : you will
have to write your own correlation stuff on the first
component so that it will be able to match the response with the
request. You may prefer using the PipilineComponent ...
Cheers,
Guillaume Nodet
Markandeya Sarraju wrote:
All,
Does service mix support a pipeline as follows?
Aè NMRèBèNMRèC and back
Component A receives incoming payload, route to B via NMR, B does
some processing and route to C via NMR with response coming back to A.
The above did not work for me as B send back the response to A
instead of routing to C?
Any alternatives to achieve above?
Thanks
Mark
This message may contain privileged and/or confidential information.
If you receive this message in error or are not the intended
recipient, you may not disseminate this message and you are requested
to erase all copies of this message and attachments.
