Re: [rules-users] Can we make our kbase object available from one context to another context (one application to another webservice)

OK, let me step back. Do you mean contexts of page, request and application in a single web-application, or different contexts (i.e. applications) on a web-server? If the latter why would you want to do that? Isn't it likely different applications require different KnowledgeBases. In this instance too I'd recommend exposing it as web-service that other contexts can call into. AFAIK drools-server provides for this (Esteban or Salaboy may know more). This would allow you to scale horizontally if your consuming contexts' load increased. If you mean to share a KnowledgeBase across different HTTP requests then I believe the common pattern is to store it in application scope and create different stateless sessions for each request. On 15 December 2011 16:42, srinivasasanda <srinivasasanda(a)gmail.com&gt; wrote: