Hi,
I have a question regarding the creation of "mediation flows" within ServiceMix, that is, chaining together validations, transformations, mediations, aggregations, etc. in a sequence. I am aware this messaging route can be achieved using the EIP Static Routing Slip pattern, specifying the endpoints or services through which the message should pass before reaching the final destination. However I have noticed that every single validation, transformation or mediation service needs to essentially be exposed as a *service* on the ESB. Instead of having to do so, does ServiceMix offer a mechanism to embed the different activities inside a mediation flow in an anonymous manner, without having to expose each single activity as a service? I am thinking of something equivalent to what Synapse/WSO2 calls "sequences". The thing is that in my opinion, exposing each single activity or step as a service on the bus kind of "clutters" the ESB, because in most scenarios the activities not be reusable in other mediation flows, and, on the other hand, architecturally speaking, they are too fine-grained to be offered as services. Apologies if I have got wrong information... Thanks a lot, Raul. ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente. Pueden estar protegidos por secreto profesional Si usted recibe este correo electronico por error, gracias de informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos Origin no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos Origin, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus ------------------------------------------------------------------
