Ok, thanks for your reply! Im wondering however whether putting this functionality in a SE the right place? Shouldn't this be considered a core functionality of esb? As far as i understand it most of the (more advanced) routing functionality is build upon camel. What about production cases where the esb is deployed in a distributed manner? In this case a simple camel routing slip would cause the messages to travel back and forth trough the container where th camel-su is deployed. So, can't we achieve the same functionality with core jbi functionality?
cheers, Johannes > You can achieve this routing scenario using the Camel routing engine via de > servicemix-camel service engine. > > You would create some routing logic that upon receipt of the message from > Service A, invokes the "get temperature measure description" service on > Service B, compare the result with some field on the message from Service A, > and if there is a match, the message would go through to Service B. Else, > the necesary transformation would occur based on the required conversion > before the message is sent to B. > > Take a look at the servicemix-camel SE and Apache Camel. > > Good luck. > > > 2008/10/23 Johannes Elsinghorst <[EMAIL PROTECTED]> > > >> Hello, >> >> consider the following situation: >> >> service A sends a message to service B. The message contains some >> measure, lets say temperature. Service's A data model uses degree >> Celsius and service B uses Fahrenheit. Both services offer an operation >> returning an description including the used unit of measure. How can we >> configure servicemix and its components to check whether the message >> contains the mesaure in the correct unit of measure and, if that is not >> the case, route it first through a transformation service? Where would >> this scenario fit in the Jbi-routing-mechanism? >> Thanks in advance for any hints and ideas! >> cheers, Johannes >> >> >> > >
