Re: [rules-users] [rules-dev] DRL - Local objects

Adhir, Im facing the same challenge using rules in a ETL process where performance is a main concern (some millisecs do the different when you have millions of executions), so I'm using Globals to keep data in the session. You can add a global object as a global variable in the session scope and all the rules will have access to it in conditions and actions. MyHelperClass helper = new MyHelperClass(); StatelessKnowledgeSession statelessSession = kb.newStatelessKnowledgeSession(); if (statelessSession == null){ log.error("Session was not created."); return; } statelessSession.setGlobal("myHelper", helper); In the DRL you import the class and define the global. You can also define some static (or not) methods in the helper class to assit you and use them as functions in your rules (if used as functions, methods needs to be static, if no static, then they can be used as methods of the global instance in the consequence block) import com.mycompany.rules.helpers.MyHelperClass; import function com.mycompany.helpers.MyHelperClass.SOME_FUNCTION; global com.emycompany.helpers.MyHelperClass helper; This solution is not ideal, because you relay on java classes (code outside of the rules and RETE) to perform evaluations (functions with evals in conditions) and the consequence hide some code in java classes, which is not so good because one of the main features of a rule engine is the separation of the logic from the static code... but it works and it helps sometimes. Good luck. On Wed, Mar 23, 2011 at 7:55 AM, Adhir Mehta <adhirmehta21(a)gmail.com&gt; wrote: -- ----------------------------- Felipe Piccolini felipe.piccolini(a)gmail.com