Hi all,<br><br>I&#39;m working on an application that has to maintain a knowledge base that&#39;ll change (a lot) over time; meaning some rules might change, others will be added and, finally, some will be deleted from the KB. Our tests show the following un-expected (imho *) behaviors:<br>

<ul><li>Whenever the contents of the KB change, all rules associated with it are re-compiled.It doesn&#39;t matter whether one rule or all of them were changed.<br></li><li>If the time taken to re-compile all rules is greater than the frequency according to which resource change notification / scanner services poll the KB, then the KB will be re-compiled more than once. I can&#39;t measure how many extra compilations happen due to time constraints; it takes more than 10 minutes for the application to compile all rules and something like 5 minutes to recompile the smallest possible version of it.</li>

</ul>So... my question is: is possible to fine tune this behavior so that drools won&#39;t recompile everything from scratch? More than that, I&#39;d like to have it wait for itself to finish any compilation that might happening at the time. Is it possible?<br>

<br>My approach to using drools is the following: create a KnowledgeAgent, then have it apply a change set that points to a directory that contains DRL files. And this has to be done for five different KA&#39;s. I suppose this is the correct approach.<br>

<br>Thanks in advance for any feedback that you might have.<br><br>Regards,<br>Luiz Eduardo<br>