I think that http://servicemix.org/servicemix-eip#servicemix-eip-StaticRoutingSlip should solve this problem. You may need a http://servicemix.org/servicemix-eip#servicemix-eip-Pipeline in front of the routing slip to transform the InOnly pattern from the quartz component to an InOut.
You can not use the destinationService on binding components as they will handle In-Only and In-Out meps differently. Cheers, Guillaume Nodet On 4/30/06, dajevu <[EMAIL PROTECTED]> wrote:
I've worked with commercial ESB's such as Fiorano and Sonic, and I was under the impression that I could simply "chain together" a set of components by way of using the "DestinationService" attribute? Is that assumption correct? I don't seem to be able to go beyond 2 component's tied together? If I need to chain together a whole sequence of steps, what is the best way of doing that? Through the JMS service? For instance, if I want to do something like: 1. Use the Quartz service to initiate an action, such as an HTTP Post 2. The HTTP Post component posts a request, which in turn, is passed to: 3. An XSTL component to do a transformation, which then: 4. Calls a web service using the SAAJ component, which then: 5. Emails me with the results. Can I simply chain these 5 steps together by using the DestinationService mechanism? None of the examples seem to address a scenario such as I've mentioned. Thanks a bunch! jeff -- View this message in context: http://www.nabble.com/General-Question-t1531899.html#a4161636 Sent from the ServiceMix - User forum at Nabble.com.
