Andy, Using a static routing slip is perfectly fine for your use case. We don't really have a more specific concept like the Mule transformer around because we could already handle the use case with the plain EIP, I guess.
If you want a less verbose way to configure the same thing, you might want to take a look at servicemix-camel too. In the Spring XML syntax, it would basically look like: <route> <from uri="[starting-endpoint]"/> <to uri="[pre-processing-endpoint]"/> <to uri="[jms-endpoint]"/> <to uri="[post-processing-endpoint]"/> </route> You could also use the Java fluent API (my personal favorite) that would read from(...).to(...).to(...).to(...). Regards, Gert Vanthienen ------------------------ Open Source SOA: http://fusesource.com Blog: http://gertvanthienen.blogspot.com/ 2009/4/17 nhcoder <[email protected]>: > > Hi everyone, > > I am putting together a service assembly and while I have an example > working, I wanted to ask the experts as to if it was the best way to achieve > the goal. > > Basically what I have right now is a Static Routing Slip that has three > components in the flow of operations. The first one accepts and processes > the xml message, then sends that to another component that calls a jms > queue, and then a third service unit post processes the message which then > gets returned to the calling client. > > In this case my pre and post processing components are basically acting like > a Mule transformer. Is this the right way to do this type of operation or > does ServiceMix have a "transformer" like component that you configure in a > different way in some config file? > > Thanks, > > Andy > > > -- > View this message in context: > http://www.nabble.com/Design-Question-With-%22Transformers%22-tp23102513p23102513.html > Sent from the ServiceMix - User mailing list archive at Nabble.com. > >
