The use case is: 1. OrderService (ESB service) specifies an entry-point named "OrderEntryPoint" and inserts order events into working memory. 2. CustomerService (ESB service) specifies an entry-point named "CustomerEntryPoint" and inserts customer facts into working memory. 3. DeliveryService (ESB service) uses rules, i.e., creates rulebase and working memory (statefulsession) used by used by both of the above entry points. The rationale for having multiple services use different entry points to insert different facts are: - Better performance. Some of these types of CEP applications have very high event rates (hundreds or more events per second). Funneling all the events to a single service (single queue) could be a performance bottleneck. - Cleaner design. Order service and Customer service are independent of each other. They might have other logic that is Order or Customer specific. For example the events may arrive in XML format and require transforming xml to Java and possibly adding some event related data (i.e., timestamp). Another service might be added to insert other types of facts without any impact to these two services. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240080#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...