THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
| Gliffy Diagram | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Currently servicemix JMSFlow transports Messages between Service endpoints as serialized objects. More exactly the serialized version of the servicemix MessageExchange implementation object is used.
The disadvantage is that this is no standard format. So only servicemix containers can talk to each other using JMSFlow. This is the reason why we did not use JMSFlow in our project to connect containers and instead used JMS endpoints. This allows us to use for example Tibco Business Works or Even .Net3 on the other end of the queue. But the problem is that creating a SU and a JMS endpoint for each service is quite a lot of redundant configuration.
...