I have not looked at Camel source code so cant say at which level of abstraction is the actual integration, ideally of course it would be at JMS API level. Regarding the CEP/ESP concepts, in case you have not had a chance to look at this technology so Ill try to illustrate: Lets say we have two streams of real-time messages called A (first stream) and B (second stream). This maps to JMS concepts such as queue or topic aka destination. No lets say we have 2 business requirements: 1) If message M1 comes in stream A, and message M2 does appear on stream B after maximum 5 seconds, do some action. 2) Provide sliding window facilities that covers messages in last 5 seconds for stream A and B that satisfy condition that field F1 from message in stream A is equal to F2 of messages in stream B. In technical terms administrator would define these declarative (no compile/restart required) requirements as follows: 1) EVERY m1 FROM a FOLLOWED BY m2 FROM b TIME_WINDOW(5) 2)SELECT a.*, b.* FROM a, a WHERE a.f1=b.f2 and TIME_WINDOW(5) Basically reversed relational database, SQL like API for managing and correlating messages. Does JBoss middleware has need for such thing? Any opinions appreciated. Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138040#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...