n wrote:
> From: Ansgar Konermann
> Subject: Re: [rules-users] drools dynamic LHS
> To: rules-users@lists.jboss.org
> Date: Tuesday, May 24, 2011, 6:28 PM
> Am 25.05.2011 00:34, schrieb
> marunam:
> > What I was thinking was, creating fact object
> dynamically with its
&
oss.org
Subject: Re: [rules-users] drools dynamic LHS
Thank you all for your response
The reason why I need this is, the rules are for different states and the
fact values could differ among states(insurance application).
We probably don't want to duplicate rules for different states by writi
The Context fact I mentioned would be populated with values coming from a DB
or properties file. At runtime you can read the right properties file,
create a "Context" object and feed the working memory with it plus all the
other regular facts you already have. With this you achieve the
parametrizat
Am 25.05.2011 00:34, schrieb marunam:
> What I was thinking was, creating fact object dynamically with its
> attributes being loaded from some properties file dynamically??
>
> Any other solution/suggestions?
Create pre-compiled rule packages: one for each state and one for the
generic rules, and
Thank you all for your response
The reason why I need this is, the rules are for different states and the
fact values could differ among states(insurance application).
We probably don't want to duplicate rules for different states by writing
separate drl file(just changing the fact valueage i
Am 24.05.2011 21:17, schrieb marunam:
> Let's say, if the business
> want to modify the rules with more fact values, I want to be able to happen
> this dynamically rather than changing the code for fact values and adding it
> there.
Smells like YAGNI and a lot of accidental complexity.
I'd code i
WHat you're describing is a rule base, which is what writing drl (or using
guvnor) is for in the first place. :)
--- On Tue, 5/24/11, marunam wrote:
> From: marunam
> Subject: Re: [rules-users] drools dynamic LHS
> To: rules-users@lists.jboss.org
> Date: Tuesday, May 24,
I understand that fact could store the values but my question more towards
how to design this for dynamic number of facts. Let's say, if the business
want to modify the rules with more fact values, I want to be able to happen
this dynamically rather than changing the code for fact values and adding
You can have a fact that stores those values:
rule "Check Age"
when
Context($ageLimit : age)
Person(age > $ageLimit)
then
do something...
end
On Tue, May 24, 2011 at 6:33 PM, marunam wrote:
> Hello,
>
> I have a question about having dyna
Hello,
I have a question about having dynamic LHS in drool rules. Below is what I
am looking for
rule "Check Age"
when
Person(age > 24)
then
do something...
end
What is the best way to keep the actual fact data dynamic(i.e. 24 in this
cas
10 matches
Mail list logo
