Yet another addition:
Changing one DRL file does not mean you have to recompile them all; only the
changed one. This means that you can, by judicious distribution of your
rules over several .DRL files separate stable rules from the volatile or
likely-to-be-changed ones. Then, you keep the KnowledgePackage-s resulting
from individual DRL files in serialized form, load those where the DRL does
not change into your KnowledgeBase and compile (and save!) the changed DRL.
-W
2010/12/21 Michael Anstis <michael.anstis(a)gmail.com>
Hi,
Any changes to rules within a DRL will need to be reflected in the
KnowledgeBase after being compiled by KnowledgeBuilder into
KnowledgePackages..
How the DRL changes *get* to the KnowledgeBase is a different matter: You
could use Changesets, KnowledgeAgent, Guvnor or simply add the DRL to your
KnowledgeBase manually.
To avoid any confusion you do not need to recompile your application as
"rules" are simply an external resource.
Cheers,
Mike
On 21 December 2010 08:17, dhermanns <d.hermanns(a)lvm.de> wrote:
>
> Hi Kiran,
>
> that depends :) I'm using Drools Guvnor and with every change of a drl you
> have to start a "build" so that the binary packages get updated (but this
> build is in guvnor only, you don't have to recompile your java-code).
>
> But i think if you are building the knowledgebase with plain drools and
> always recreating it all changes to the drls should be active at once
> (@everyone else: correct me if I'm wrong ;)
>
> cu,
> Dirk
> --
> View this message in context:
>
http://drools-java-rules-engine.46999.n3.nabble.com/Does-rule-modificatio...
> Sent from the Drools - User mailing list archive at
Nabble.com.
> _______________________________________________
> rules-users mailing list
> rules-users(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/rules-users
>
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users