6:05 a.m.
Hello All,
I'm working at HP Software R&D and we are considering using drools in our
product.
Benchmarking tests showed that running 10,000 rules consumes 382mb.
This is too high for our system requirements, and we would like to know how we can improve
it.
Technical details:
- Drools version: 5.1 with default configuration.
- All rules look like this:
rule "status-Fixed-Open"
when
event : FieldChangedEvent(fieldName == "status",
oldValue == "Fixed");
entity : Entity(entityType == "mock-entity");
eval(((String)
entity.getFieldValue("status")).equals("Open"));
then
do Something...
end
- Loading code:
KnowledgeBuilder knowledgeBuilder = KnowledgeBuilderFactory.newKnowledgeBuilder();
for(all resources)
{
knowledgeBuilder.add(resource, ResourceType.DRL);
}
knowledgeBase = KnowledgeBaseFactory.newKnowledgeBase();
knowledgeBase.addKnowledgePackages(knowledgeBuilder.getKnowledgePackages());
Any insights are most appreciated.
Thank You,
Liron, HP Software R&D
10:14 a.m.
There is no out of the box way to improve that, beyond just partitioning
your rulebases yourself.
If you would like to get involved in R&D we can do lazy network building
and try pushing unused parts of the rule network to disk.
Mark
On 26/04/2011 12:05, Shebs, Liron wrote:
Hello All,
I'm working at HP Software R&D and we are considering using drools in
our product.
Benchmarking tests showed that running 10,000 rules consumes 382mb.
This is too high for our system requirements, and we would like to
know how we can improve it.
Technical details:
-Drools version: 5.1 with default configuration.
-All rules look like this:
rule "status-Fixed-Open"
when
event : FieldChangedEvent(fieldName ==
"status", oldValue == "Fixed");
entity : Entity(entityType == "mock-entity");
eval(((String)
entity.getFieldValue("status")).equals("Open"));
then
do Something...
end
-Loading code:
KnowledgeBuilder knowledgeBuilder =
KnowledgeBuilderFactory.newKnowledgeBuilder();
for(all resources)
{
knowledgeBuilder.add(resource, ResourceType.DRL);
}
knowledgeBase = KnowledgeBaseFactory.newKnowledgeBase();
knowledgeBase.addKnowledgePackages(knowledgeBuilder.getKnowledgePackages());
Any insights are most appreciated.
Thank You,
Liron, HP Software R&D
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
10:18 a.m.
is it necessary to execute 10000 rules in one time for your case?
Why don't execute rule selectively?
2011/4/26 Mark Proctor <mproctor(a)codehaus.org>
There is no out of the box way to improve that, beyond just
partitioning
your rulebases yourself.
If you would like to get involved in R&D we can do lazy network building
and try pushing unused parts of the rule network to disk.
Mark
On 26/04/2011 12:05, Shebs, Liron wrote:
Hello All,
I’m working at HP Software R&D and we are considering using drools in our
product.
Benchmarking tests showed that running 10,000 rules consumes 382mb.
This is too high for our system requirements, and we would like to know how
we can improve it.
Technical details:
- Drools version: 5.1 with default configuration.
- All rules look like this:
rule "status-Fixed-Open"
when
event : FieldChangedEvent(fieldName ==
"status", oldValue == "Fixed");
entity : Entity(entityType == "mock-entity");
eval(((String)
entity.getFieldValue("status")).equals("Open"));
then
do Something…
end
- Loading code:
KnowledgeBuilder knowledgeBuilder =
KnowledgeBuilderFactory.newKnowledgeBuilder();
for(all resources)
{
knowledgeBuilder.add(resource, ResourceType.DRL);
}
knowledgeBase = KnowledgeBaseFactory.newKnowledgeBase();
knowledgeBase.addKnowledgePackages(knowledgeBuilder.getKnowledgePackages());
Any insights are most appreciated.
Thank You,
Liron, HP Software R&D
_______________________________________________
rules-users mailing
listrules-users@lists.jboss.orghttps://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
10:30 a.m.
The rule you have shown suggests that many of your rules (if not all)
compare fact fields with literals. If there are groups of rules where just
these literals vary, and the corresponding RHS logic is also uniform (just
varying with the values stored or written or whatever), then you might
consider reducing the number of rules - perhaps even considerably - by
putting those sets of literals into Parameter facts and perform the match
with a considerably smaller set of generic rules, one per such a group.
-W
2011/4/26 Mark Proctor <mproctor(a)codehaus.org>
There is no out of the box way to improve that, beyond just
partitioning
your rulebases yourself.
If you would like to get involved in R&D we can do lazy network building
and try pushing unused parts of the rule network to disk.
Mark
On 26/04/2011 12:05, Shebs, Liron wrote:
Hello All,
I’m working at HP Software R&D and we are considering using drools in our
product.
Benchmarking tests showed that running 10,000 rules consumes 382mb.
This is too high for our system requirements, and we would like to know how
we can improve it.
Technical details:
- Drools version: 5.1 with default configuration.
- All rules look like this:
rule "status-Fixed-Open"
when
event : FieldChangedEvent(fieldName ==
"status", oldValue == "Fixed");
entity : Entity(entityType == "mock-entity");
eval(((String)
entity.getFieldValue("status")).equals("Open"));
then
do Something…
end
- Loading code:
KnowledgeBuilder knowledgeBuilder =
KnowledgeBuilderFactory.newKnowledgeBuilder();
for(all resources)
{
knowledgeBuilder.add(resource, ResourceType.DRL);
}
knowledgeBase = KnowledgeBaseFactory.newKnowledgeBase();
knowledgeBase.addKnowledgePackages(knowledgeBuilder.getKnowledgePackages());
Any insights are most appreciated.
Thank You,
Liron, HP Software R&D
_______________________________________________
rules-users mailing
listrules-users@lists.jboss.orghttps://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
11:16 a.m.
Your eval, you could probably replace by something like this:
rule "status-Fixed-Open"
when
event : FieldChangedEvent(fieldName ==
"status", oldValue == "Fixed");
entity : Entity(entityType == "mock-entity",
field == "status", value == "Open");
then
do Something…
end
2011/4/26 Shebs, Liron <liron.shebs(a)hp.com>
Hello All,
I’m working at HP Software R&D and we are considering using drools in our
product.
Benchmarking tests showed that running 10,000 rules consumes 382mb.
This is too high for our system requirements, and we would like to know how
we can improve it.
Technical details:
- Drools version: 5.1 with default configuration.
- All rules look like this:
rule "status-Fixed-Open"
when
event : FieldChangedEvent(fieldName ==
"status", oldValue == "Fixed");
entity : Entity(entityType == "mock-entity");
eval(((String)
entity.getFieldValue("status")).equals("Open"));
then
do Something…
end
- Loading code:
KnowledgeBuilder knowledgeBuilder =
KnowledgeBuilderFactory.newKnowledgeBuilder();
for(all resources)
{
knowledgeBuilder.add(resource, ResourceType.DRL);
}
knowledgeBase = KnowledgeBaseFactory.newKnowledgeBase();
knowledgeBase.addKnowledgePackages(knowledgeBuilder.getKnowledgePackages());
Any insights are most appreciated.
Thank You,
Liron, HP Software R&D
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
2:48 p.m.
Benchmarking tests showed that running 10,000 rules consumes 382mb.
Are you talking about the memory footprint of your KnowledgeBase when you
load it or is after the insertion of facts / execution of rules?
Do you have any more detailed profiling information to share with us? We
might be able to help with some experimental features if you provide more
details.
On Tue, Apr 26, 2011 at 6:16 PM, Leonardo Gomes
<leonardo.f.gomes(a)gmail.com>wrote:
Your eval, you could probably replace by something like this:
rule "status-Fixed-Open"
when
event : FieldChangedEvent(fieldName ==
"status", oldValue == "Fixed");
entity : Entity(entityType == "mock-entity",
field == "status", value == "Open");
then
do Something…
end
2011/4/26 Shebs, Liron <liron.shebs(a)hp.com>
> Hello All,
>
>
>
> I’m working at HP Software R&D and we are considering using drools in our
> product.
>
> Benchmarking tests showed that running 10,000 rules consumes 382mb.
>
> This is too high for our system requirements, and we would like to know
> how we can improve it.
>
> Technical details:
>
> - Drools version: 5.1 with default configuration.
>
> - All rules look like this:
>
>
>
> rule "status-Fixed-Open"
>
> when
>
> event : FieldChangedEvent(fieldName ==
> "status", oldValue == "Fixed");
>
> entity : Entity(entityType == "mock-entity");
>
> eval(((String)
> entity.getFieldValue("status")).equals("Open"));
>
> then
>
> do Something…
>
> end
>
>
>
> - Loading code:
>
>
>
> KnowledgeBuilder knowledgeBuilder =
> KnowledgeBuilderFactory.newKnowledgeBuilder();
>
> for(all resources)
>
> {
>
> knowledgeBuilder.add(resource, ResourceType.DRL);
>
> }
>
> knowledgeBase = KnowledgeBaseFactory.newKnowledgeBase();
>
>
> knowledgeBase.addKnowledgePackages(knowledgeBuilder.getKnowledgePackages());
>
>
>
> Any insights are most appreciated.
>
>
>
> Thank You,
>
> Liron, HP Software R&D
>
>
>
>
>
>
>
> _______________________________________________
> rules-users mailing list
> rules-users(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-users
>
>
9:27 p.m.
Besides all suggestions already made in other e-mails, it is also worth
considering if you can pre-compile rules and just load them at runtime
instead of compiling them at runtime.
I.e, the method:
knowledgeBuilder.add(resource, ResourceType.DRL);
Will call the JDT compiler to compile your rules and that uses quite a
lot of memory that is later disposed. Instead, you could compile the
knowledge base at build time and serialize it, and at runtime all you do is
deserialize you kbase and use it, saving the memory that was previously used
for compilation.
Edson
2011/4/26 Shebs, Liron <liron.shebs(a)hp.com>
Hello All,
I’m working at HP Software R&D and we are considering using drools in our
product.
Benchmarking tests showed that running 10,000 rules consumes 382mb.
This is too high for our system requirements, and we would like to know how
we can improve it.
Technical details:
- Drools version: 5.1 with default configuration.
- All rules look like this:
rule "status-Fixed-Open"
when
event : FieldChangedEvent(fieldName ==
"status", oldValue == "Fixed");
entity : Entity(entityType == "mock-entity");
eval(((String)
entity.getFieldValue("status")).equals("Open"));
then
do Something…
end
- Loading code:
KnowledgeBuilder knowledgeBuilder =
KnowledgeBuilderFactory.newKnowledgeBuilder();
for(all resources)
{
knowledgeBuilder.add(resource, ResourceType.DRL);
}
knowledgeBase = KnowledgeBaseFactory.newKnowledgeBase();
knowledgeBase.addKnowledgePackages(knowledgeBuilder.getKnowledgePackages());
Any insights are most appreciated.
Thank You,
Liron, HP Software R&D
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
--
Edson Tirelli
JBoss Drools Core Development
JBoss by Red Hat @ www.jboss.com
3:42 a.m.
there's a maven-drools-plugin out there in the wild to precompile your
rules.
Op 27-04-11 04:27, Edson Tirelli schreef:
Besides all suggestions already made in other e-mails, it is also
worth considering if you can pre-compile rules and just load them at
runtime instead of compiling them at runtime.
I.e, the method:
knowledgeBuilder.add(resource, ResourceType.DRL);
Will call the JDT compiler to compile your rules and that uses
quite a lot of memory that is later disposed. Instead, you could
compile the knowledge base at build time and serialize it, and at
runtime all you do is deserialize you kbase and use it, saving the
memory that was previously used for compilation.
Edson
2011/4/26 Shebs, Liron <liron.shebs(a)hp.com <mailto:liron.shebs@hp.com>>
Hello All,
I’m working at HP Software R&D and we are considering using drools
in our product.
Benchmarking tests showed that running 10,000 rules consumes 382mb.
This is too high for our system requirements, and we would like to
know how we can improve it.
Technical details:
-Drools version: 5.1 with default configuration.
-All rules look like this:
rule "status-Fixed-Open"
when
event : FieldChangedEvent(fieldName
== "status", oldValue == "Fixed");
entity : Entity(entityType ==
"mock-entity");
eval(((String)
entity.getFieldValue("status")).equals("Open"));
then
do Something…
end
-Loading code:
KnowledgeBuilder knowledgeBuilder =
KnowledgeBuilderFactory.newKnowledgeBuilder();
for(all resources)
{
knowledgeBuilder.add(resource, ResourceType.DRL);
}
knowledgeBase = KnowledgeBaseFactory.newKnowledgeBase();
knowledgeBase.addKnowledgePackages(knowledgeBuilder.getKnowledgePackages());
Any insights are most appreciated.
Thank You,
Liron, HP Software R&D
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org <mailto:rules-users@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/rules-users
--
Edson Tirelli
JBoss Drools Core Development
JBoss by Red Hat @ www.jboss.com <http://www.jboss.com>
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
--
With kind regards,
Geoffrey De Smet
4:09 a.m.
http://drools.46999.n3.nabble.com/maven-drools-plugin-to-compile-DRL-s-at...
2011/4/27 Geoffrey De Smet <ge0ffrey.spam(a)gmail.com>
there's a maven-drools-plugin out there in the wild to
precompile your
rules.
Op 27-04-11 04:27, Edson Tirelli schreef:
Besides all suggestions already made in other e-mails, it is also worth
considering if you can pre-compile rules and just load them at runtime
instead of compiling them at runtime.
I.e, the method:
knowledgeBuilder.add(resource, ResourceType.DRL);
Will call the JDT compiler to compile your rules and that uses quite a
lot of memory that is later disposed. Instead, you could compile the
knowledge base at build time and serialize it, and at runtime all you do is
deserialize you kbase and use it, saving the memory that was previously used
for compilation.
Edson
2011/4/26 Shebs, Liron <liron.shebs(a)hp.com>
> Hello All,
>
>
>
> I’m working at HP Software R&D and we are considering using drools in our
> product.
>
> Benchmarking tests showed that running 10,000 rules consumes 382mb.
>
> This is too high for our system requirements, and we would like to know
> how we can improve it.
>
> Technical details:
>
> - Drools version: 5.1 with default configuration.
>
> - All rules look like this:
>
>
>
> rule "status-Fixed-Open"
>
> when
>
> event : FieldChangedEvent(fieldName ==
> "status", oldValue == "Fixed");
>
> entity : Entity(entityType == "mock-entity");
>
> eval(((String)
> entity.getFieldValue("status")).equals("Open"));
>
> then
>
> do Something…
>
> end
>
>
>
> - Loading code:
>
>
>
> KnowledgeBuilder knowledgeBuilder =
> KnowledgeBuilderFactory.newKnowledgeBuilder();
>
> for(all resources)
>
> {
>
> knowledgeBuilder.add(resource, ResourceType.DRL);
>
> }
>
> knowledgeBase = KnowledgeBaseFactory.newKnowledgeBase();
>
>
> knowledgeBase.addKnowledgePackages(knowledgeBuilder.getKnowledgePackages());
>
>
>
> Any insights are most appreciated.
>
>
>
> Thank You,
>
> Liron, HP Software R&D
>
>
>
>
>
>
>
> _______________________________________________
> rules-users mailing list
> rules-users(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-users
>
>
--
Edson Tirelli
JBoss Drools Core Development
JBoss by Red Hat @ www.jboss.com
_______________________________________________
rules-users mailing
listrules-users@lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/rules-users
--
With kind regards,
Geoffrey De Smet
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
7:24 a.m.
Hi All,
Thank you all for your responses and ideas.
Here are some answers to questions raised by you
* 10,000 rules is what we estimate a real system will contain.
* The rules are similar to each other on the testing environment, but in the real
system we expect more variance, making parameterized rules difficult to implement.
* Measurements of memory consumption where done after the rules loading was
completed + GC, so I'm sure pre-compiling will help.
* When I say memory consumption I mean memory footprint (production memory).
* Removing "eval" from the rules saved ~80mb (10,000 rules, same
environment).
Mark, reading all these clarifications, does 30kb per rule sound reasonable? Do you think
that we can improve this number somehow?
Thank you,
-- Liron
From: rules-users-bounces(a)lists.jboss.org [mailto:rules-users-bounces@lists.jboss.org] On
Behalf Of Leonardo Gomes
Sent: Wednesday, April 27, 2011 12:10 PM
To: Rules Users List
Subject: Re: [rules-users] Memory issue with drools (using 10000 rules)
http://drools.46999.n3.nabble.com/maven-drools-plugin-to-compile-DRL-s-at...
2011/4/27 Geoffrey De Smet
<ge0ffrey.spam@gmail.com<mailto:ge0ffrey.spam@gmail.com>>
there's a maven-drools-plugin out there in the wild to precompile your rules.
Op 27-04-11 04:27, Edson Tirelli schreef:
Besides all suggestions already made in other e-mails, it is also worth considering if
you can pre-compile rules and just load them at runtime instead of compiling them at
runtime.
I.e, the method:
knowledgeBuilder.add(resource, ResourceType.DRL);
Will call the JDT compiler to compile your rules and that uses quite a lot of memory
that is later disposed. Instead, you could compile the knowledge base at build time and
serialize it, and at runtime all you do is deserialize you kbase and use it, saving the
memory that was previously used for compilation.
Edson
2011/4/26 Shebs, Liron <liron.shebs@hp.com<mailto:liron.shebs@hp.com>>
Hello All,
I'm working at HP Software R&D and we are considering using drools in our
product.
Benchmarking tests showed that running 10,000 rules consumes 382mb.
This is too high for our system requirements, and we would like to know how we can improve
it.
Technical details:
- Drools version: 5.1 with default configuration.
- All rules look like this:
rule "status-Fixed-Open"
when
event : FieldChangedEvent(fieldName == "status",
oldValue == "Fixed");
entity : Entity(entityType == "mock-entity");
eval(((String)
entity.getFieldValue("status")).equals("Open"));
then
do Something...
end
- Loading code:
KnowledgeBuilder knowledgeBuilder = KnowledgeBuilderFactory.newKnowledgeBuilder();
for(all resources)
{
knowledgeBuilder.add(resource, ResourceType.DRL);
}
knowledgeBase = KnowledgeBaseFactory.newKnowledgeBase();
knowledgeBase.addKnowledgePackages(knowledgeBuilder.getKnowledgePackages());
Any insights are most appreciated.
Thank You,
Liron, HP Software R&D
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org<mailto:rules-users@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/rules-users
--
Edson Tirelli
JBoss Drools Core Development
JBoss by Red Hat @ www.jboss.com<http://www.jboss.com>
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org<mailto:rules-users@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/rules-users
--
With kind regards,
Geoffrey De Smet
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org<mailto:rules-users@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/rules-users
8:23 a.m.
Hi Liron,
Are you planning on using a stateful or a stateless session afterwards? Do
you have the memory numbers for rules execution? How many facts?
-Leonardo.
2011/4/27 Shebs, Liron <liron.shebs(a)hp.com>
Hi All,
Thank you all for your responses and ideas.
Here are some answers to questions raised by you
· 10,000 rules is what we estimate a real system will contain.
· The rules are similar to each other on the testing environment,
but in the real system we expect more variance, making parameterized rules
difficult to implement.
· Measurements of memory consumption where done after the rules
loading was completed + GC, so I’m sure pre-compiling will help.
· When I say memory consumption I mean memory footprint
(production memory).
· Removing “eval” from the rules saved ~80mb (10,000 rules, same
environment).
Mark, reading all these clarifications, does 30kb per rule sound
reasonable? Do you think that we can improve this number somehow?
Thank you,
-- Liron
*From:* rules-users-bounces(a)lists.jboss.org [mailto:
rules-users-bounces(a)lists.jboss.org] *On Behalf Of *Leonardo Gomes
*Sent:* Wednesday, April 27, 2011 12:10 PM
*To:* Rules Users List
*Subject:* Re: [rules-users] Memory issue with drools (using 10000 rules)
http://drools.46999.n3.nabble.com/maven-drools-plugin-to-compile-DRL-s-at...
2011/4/27 Geoffrey De Smet <ge0ffrey.spam(a)gmail.com>
there's a maven-drools-plugin out there in the wild to precompile your
rules.
Op 27-04-11 04:27, Edson Tirelli schreef:
Besides all suggestions already made in other e-mails, it is also worth
considering if you can pre-compile rules and just load them at runtime
instead of compiling them at runtime.
I.e, the method:
knowledgeBuilder.add(resource, ResourceType.DRL);
Will call the JDT compiler to compile your rules and that uses quite a
lot of memory that is later disposed. Instead, you could compile the
knowledge base at build time and serialize it, and at runtime all you do is
deserialize you kbase and use it, saving the memory that was previously used
for compilation.
Edson
2011/4/26 Shebs, Liron <liron.shebs(a)hp.com>
Hello All,
I’m working at HP Software R&D and we are considering using drools in our
product.
Benchmarking tests showed that running 10,000 rules consumes 382mb.
This is too high for our system requirements, and we would like to know how
we can improve it.
Technical details:
- Drools version: 5.1 with default configuration.
- All rules look like this:
rule "status-Fixed-Open"
when
event : FieldChangedEvent(fieldName ==
"status", oldValue == "Fixed");
entity : Entity(entityType == "mock-entity");
eval(((String)
entity.getFieldValue("status")).equals("Open"));
then
do Something…
end
- Loading code:
KnowledgeBuilder knowledgeBuilder =
KnowledgeBuilderFactory.newKnowledgeBuilder();
for(all resources)
{
knowledgeBuilder.add(resource, ResourceType.DRL);
}
knowledgeBase = KnowledgeBaseFactory.newKnowledgeBase();
knowledgeBase.addKnowledgePackages(knowledgeBuilder.getKnowledgePackages());
Any insights are most appreciated.
Thank You,
Liron, HP Software R&D
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
--
Edson Tirelli
JBoss Drools Core Development
JBoss by Red Hat @ www.jboss.com
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
--
With kind regards,
Geoffrey De Smet
_______________________________________________
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
9:40 p.m.
Would removing the eval() from your rule reduce memory usage?
Jevon
2011/4/26 Shebs, Liron <liron.shebs(a)hp.com>
Hello All,
I’m working at HP Software R&D and we are considering using drools in our
product.
Benchmarking tests showed that running 10,000 rules consumes 382mb.
This is too high for our system requirements, and we would like to know how
we can improve it.
Technical details:
- Drools version: 5.1 with default configuration.
- All rules look like this:
rule "status-Fixed-Open"
when
event : FieldChangedEvent(fieldName ==
"status", oldValue == "Fixed");
entity : Entity(entityType == "mock-entity");
eval(((String)
entity.getFieldValue("status")).equals("Open"));
then
do Something…
end
- Loading code:
KnowledgeBuilder knowledgeBuilder =
KnowledgeBuilderFactory.newKnowledgeBuilder();
for(all resources)
{
knowledgeBuilder.add(resource, ResourceType.DRL);
}
knowledgeBase = KnowledgeBaseFactory.newKnowledgeBase();
knowledgeBase.addKnowledgePackages(knowledgeBuilder.getKnowledgePackages());
Any insights are most appreciated.
Thank You,
Liron, HP Software R&D
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
5375
days inactive
5376
days old
11 comments
8 participants
participants (8)
-
Benson Fung -
Edson Tirelli -
Geoffrey De Smet -
Jevon Wright -
Leonardo Gomes -
Mark Proctor -
Shebs, Liron -
Wolfgang Laun