Oh no … I have multiple knowledge bases configured in my apps. I just use a separate Spring bean to wrap each. :)
Although for your purposes it shouldn't be too tricky to manage a pool of knowledge bases or create a reference to one per user session. The main risk would be memory usage if you have a large knowledge base or lots of facts, as a knowledge base and session is relatively memory hungry. Depends on how many users you have I guess. On 14 Jan 2013, at 14:44, riri <[email protected]> wrote: > Thank you for your very quick replies. > > >> You just need to create a Spring bean to act as the interface to your >> knowledge >> base. That way, Spring ensures that you have only one knowledge base >> instance in play, so it is configured and compiled when the application >> starts. > > Does this mean that you can not have more than one knowledge base > configured? My application basically needs to offer the ability to edit and > test a user's own rules and facts (in a way similar to what Guvnor does but > much more simplified) and I do not know if that can be done using just one > knowledge base and sessions. I was thinking of having a separate knowledge > base per user and using a KnowledgeAgent for updating but I have yet to test > this approach. > > > > > > -- > View this message in context: > http://drools.46999.n3.nabble.com/Web-services-and-Drools-tp4021509p4021515.html > Sent from the Drools: User forum mailing list archive at Nabble.com. > _______________________________________________ > rules-users mailing list > [email protected] > https://lists.jboss.org/mailman/listinfo/rules-users _______________________________________________ rules-users mailing list [email protected] https://lists.jboss.org/mailman/listinfo/rules-users
