anonymous wrote : There is a little more to this potentially than just configuring the names of a entry points in a single service. Entry points are relative to the StatefulKnowledgeSession. They allow for multiple event streams to populate the working memory. So for example the Order service could be configured to use the OrderStream, and a Customer service would be configured to use the CustomerStream. A third service would then be configured to create the StatefulKnowledgeSession and place this object in some location where it could be looked up and used to create the entry points by the other two services. This capability is perhaps not necessary as part of the Tech Preview, but should be kept in mind when designing the entry point logic. I'm trying to understand the usecase here and this is my take on this: 1. OrderService (ESB service) uses rules and specifies an entry-point named "OrderEntryPoint". 2. CustomerService (ESB service) uses rules and specifies an entry-point named "CustomerEntryPoint". 3. DeliveryService (ESB service) uses rules and uses both of the above entry points. If this is correct then why would the OrderService and CustomerService not simply produce a Order and Customer object and pass them to the DeliveryService instead of making the DeliveryService operate on the same StatefulKnowledgeSession. Or have I totally misunderstood what you mean here :) Jeff, could you help me understand what you are after and the usecase you have in mind? Thanks, /Daniel View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4239972#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...