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@gmail.com> wrote:

Hi Manstris

is there any api in drools to make its kbase object to available to any
context

--
View this message in context: http://drools.46999.n3.nabble.com/Can-we-make-our-kbase-object-available-from-one-context-to-another-context-one-application-to-anothe-tp3588689p3589172.html

Sent from the Drools: User forum mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users