[rules-users] Storing and loading rules in database

[Meeraj Kunnumpurath]

Hi,

We do something similar, a bit more intricate though. We have been
integrating Drools into an SCA container, where the rule infrastructure is
used as an implementation type. We define the implementation type in a SCDL,
which is an XML file that has the service component definitions. Like below
for example,

<composite>

    <component name="MyRoolsComponent">
        <implementation.drools resource="jdbc://myDs?query=foo" />
    </component>

</composite>

The resource attribute is a URL, and we have custom URL connection factories
that source DRL definitions from relational databases. The users may edit
the DRL files whichever way they want and upload through a web UI.

On a slight sidebar,  we also allow other components within the SCA
container, injected via DI as globals into the rule files. We are also able
to autowire non-components implemented in Groovy, BPEL etc, into globals
within the rules component based on contract compatibility checks.

Regards
Meeraj

On Mon, Jul 19, 2010 at 9:38 PM, wilsonywx <wei.yuan at baml.com> wrote:

>
> I am trying to develop an application where users can specify rules at a
> front end and the rule engine would execute in the backend. The users will
> work with a pre-defined set of objects and actions they can take on the
> objects.
>
> I could use a BRMS such as Guvnor but I found the GUI lacking and not
> friendly enough for the non-technical end users I am supporting. I will
> instead write a front end for user input, which is stored in the DB, and
> the
> backend will pull data and generate a .drl file each time it's run.
>
> I have found an old article on loading rules in and out of a DB
> dynamically,
> at
>
> http://docs.codehaus.org/display/DROOLS/Loading+and+managing+rules+dynamically+from+a+database
>
> http://docs.codehaus.org/display/DROOLS/Loading+and+managing+rules+dynamically+from+a+database
> , which seems to fit my need. I am looking for feedbacks on users who have
> tried this approach. How flexible is it? My main concerns is that future
> versions of Drools might break a lot of things and require a lot of
> recoding. To me it seems like a reasonable approach.
> --
> View this message in context:
> http://drools-java-rules-engine.46999.n3.nabble.com/Storing-and-loading-rules-in-database-tp979499p979499.html
> Sent from the Drools - User mailing list archive at Nabble.com.
> _______________________________________________
> rules-users mailing list
> rules-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/rules-users/attachments/20100719/bf24c714/attachment.html