What do you mean exactly? Setting the agenda-group attribute for a rule at deploy time? You could do this by either post-processing the DRL rule at deployment time and injecting the attribute value, or by using drools parser to generate the descriptor model, populate the attribute in the descriptor model and then deploy. []s Edson 2010/1/28 Pritham <infinity2heaven(a)gmail.com&gt; -- Edson Tirelli JBoss Drools Core Development JBoss by Red Hat @ www.jboss.com

The "lifecycle" of drools assets, from source to executable ReteOO, can be represented by the following workflow: Source Code -> Descr Model -> Knowledge Model -> ReteOO (kbase) Explaining: 1. The source code (DRL, Decision Table, BRXML, etc) goes through the drools parser that generates the descriptor model. The descriptor model is a canonical text-based model of your assets (packages, rules, etc). You may think about it as an Abstract Syntax Tree, but without parser specific info. 2. The descriptor model goes through the knowledge builder and generates the knowledge model. The knowledge model is a 1-to-1 mapping from the descr model, but in binary (compiled) format. 3. The knowledge model goes through the reteoo builder to build the actual ReteOO network, that ultimately is the executable format. Steps 1 and 2 are hidden behind a higher level API on the KnowledgeBuilder, but you can easily execute the parser directly. Step 3 happens when you call KnowledgeBase.add(). Some people like to tinker with the source rules by just generating, changing, or injecting data into the Descr Model, instead of doing it in the textual source code. As long as you are aware that those are internal APIs that might change between drools versions and you are willing to maintain any code you write based on that, it is an easy way of avoiding parsing the rules source code yourself or using templates to inject the data you want. []s Edson 2010/1/29 Pritham <infinity2heaven(a)gmail.com&gt; -- Edson Tirelli JBoss Drools Core Development JBoss by Red Hat @ www.jboss.com