I am interested in different methods for linking two ServiceMix buses. The use case is the customer department has its own set of service interfaces and at some point, needs to pass along messages to the finance department. Each department has its own bus.
I've read through the news items and these are the ways I have found so far to connect two different SM containers: 1. JMS: Have customer application put a message onto their local bus and have the outbound binding component place this message onto a JMS queue for transmission to the finance department. 2. RemoteClient: Have the customer application receive its message from SM and use RemoteClient to attach to the finance SM. To avoid hard coding the address, the RemoteClient URL could be placed in a properties file or JNDI tree somewhere. As a side note, does it matter if the customer application runs as an external service receiving messages from a provider BC or as a Service Engine? Theoretically there is some sort of performance hit for getting on and off the bus, but in someways it seems by pushing such specific, non-crosscutting application logic into a service engine might be against the paradigm. Are there additional considerations if you try and use RemoteClient from within a service engine? Most of the examples I've seen using the RemoteClient class appear to be external web-applications or standalone java test classes. Thanks in advance. -- View this message in context: http://www.nabble.com/Bus-to-Bus-Communication-tf3918026s12049.html#a11109514 Sent from the ServiceMix - User mailing list archive at Nabble.com.
