[rules-users] Drools implementation problem

2011-06-27 Thread dan.dobrescu
Hello,

I'm trying to implement Drools in our project, but I really don't know which
method to adopt. First of all, our project is about creating marketing
campaigns for mobile network operators. So, we've got a Web UI where we let
the user define his own rules for the campaign.. Now.. here's my problem.
Should i try to translate everything in the UI in a custom drl with a custom
agenda-name (because there can be many custum campaigns with different
flows), or should I create an object with different properties which should
reflect the chosen options in the web-ui and then use it in my rules to
create the behaviour?

If I should go with the first option, how can I store it? Should I store the
drl in Guvnor(but the models my change from time to time.. not the
attributes used in the rules, other attributes.. and I can't import several
jars from an url to have access to the models, can I?) or in DB, and the
dynamically add the rules at run-time? 

--
View this message in context: 
http://drools.46999.n3.nabble.com/Drools-implementation-problem-tp3113482p3113482.html
Sent from the Drools: User forum mailing list archive at Nabble.com.
___
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users


Re: [rules-users] Drools implementation problem

2011-06-27 Thread Michael Anstis
IMO it really comes down to personal preference.

If you don't have any rules shared across campaigns I'd personally use a
different KnowledgeBase for each campaign. It'll make maintenance cleaner
when things start to change.

However if you have rules that are shared across multiple campaigns then
using a differentiator fact (i.e Campaign) that causes certain rules to
activate for certain campaigns; again as maintenance will be cleaner.

Guvnor can reference models from multiple JARs; but if you already have a
custom UI you'd only really need Guvnor as your repository (i.e database)
all be it with version control.

If you have your own UI and Guvnor's other features are excessive to your
need then storing the DRL in a database is probably your simplest option.

Cheers,

Mike

On 27 June 2011 13:41, dan.dobrescu danutzdobre...@gmail.com wrote:

 Hello,

 I'm trying to implement Drools in our project, but I really don't know
 which
 method to adopt. First of all, our project is about creating marketing
 campaigns for mobile network operators. So, we've got a Web UI where we let
 the user define his own rules for the campaign.. Now.. here's my problem.
 Should i try to translate everything in the UI in a custom drl with a
 custom
 agenda-name (because there can be many custum campaigns with different
 flows), or should I create an object with different properties which should
 reflect the chosen options in the web-ui and then use it in my rules to
 create the behaviour?

 If I should go with the first option, how can I store it? Should I store
 the
 drl in Guvnor(but the models my change from time to time.. not the
 attributes used in the rules, other attributes.. and I can't import several
 jars from an url to have access to the models, can I?) or in DB, and the
 dynamically add the rules at run-time?

 --
 View this message in context:
 http://drools.46999.n3.nabble.com/Drools-implementation-problem-tp3113482p3113482.html
 Sent from the Drools: User forum mailing list archive at Nabble.com.
 ___
 rules-users mailing list
 rules-users@lists.jboss.org
 https://lists.jboss.org/mailman/listinfo/rules-users

___
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users


Re: [rules-users] Drools implementation problem

2011-06-27 Thread dan.dobrescu
hmm.. ok, thank you very much for the advice. 

--
View this message in context: 
http://drools.46999.n3.nabble.com/Drools-implementation-problem-tp3113482p3113769.html
Sent from the Drools: User forum mailing list archive at Nabble.com.
___
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users