The Drools client API is simply a fairly lightweight interface for starting a session, manipulating knowledge and executing rules.
Retrieving a RuleBase
Before any activities may be performed, the client application must obtain a RuleBase through either building one using the administrative API or by performing a lookup within a JNDI directory or other managed object data source.
Looking up a RuleBase from JNDI
A RuleBase may be a managed object which is deployed by an administrator within a JNDI directory. This method of deployment allows an application to be isolated from changes in the rules. The rules can be easily altered and redeployed, enabling an on-the-fly modification of the behaviour of an application:
Deploying a RuleBase to JNDI
Rule Serialization
When serialising a WorkingMemory back into memory you have to remember that it effectively makes a clone of your knowledge; the WorkingMemory and main application no longer reference the same object. When you serialize back into memory you must get your objects again using the FactHandle, or search for it via the returned collection using the get Objects() method.