Re: [rules-users] Using the drools as the backend engine for a service

You would likely NOT want to create a rulebase per session. Most people create working memory per session. Rulebases should only be loaded once per server (context) in my opinion, and you reload it as rules changes. Loading a rulebase loads rules from a file, and orders your rete tree. For our installation that takes several minutes. Rulebase = once Working memory = per user/transaction -Michael ------------------------------ *From:* rules-users-bounces(a)lists.jboss.org [mailto: rules-users-bounces(a)lists.jboss.org] *On Behalf Of *Jai Vasanth *Sent:* Friday, February 01, 2008 3:23 PM *To:* Rules Users List *Subject:* [rules-users] Using the drools as the backend engine for a service Hi, I am planning on using Drools as the rules engine for a service that I am building. I am considering instantiating a stateful session for every request to the service. The RuleBase would be created when the service starts. Is this the correct way to go about incorporating Drools in a service ? Is session creation an expensive process and if so are there other efficient ways of doing so ? Thanks Jai _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users