We are working on a web application which does resource scheduling. We
have already built all of the basics, using Spring, Hibernate, Tomcat,
and other underlying technologies. We also have built the actual
scheduler interface, which will validate a schedule using Drools rules.
It's now time to
Thats exactly the goal with drools 2.5 - precompiled jars. We call them
.ddjs drools deployment jars. Unfortunately this hasn't been documented
that well, as we are putting all our efforts into 3.0. The best way to
understand this API is to look over the unit tests:
Is this the default behavior in Drools 2.5+? I.e. compile the rules to a
jar file containing .class-files followed by the loading of this jar? (I
can see on the JavaPolis 2005 presentation a source ddj is also
generated) And I suppose the rules do not have to be recompiled the next
time you use
When you use the fireAllRules(AgendaFilter) method on the WorkingMemory does
it clear the Agenda when its done or can you fire different rules in the
working memory at different points in time without modifying the facts in
between.
The rules I have can be broken into two distinct rulesets that
no when its finished, the agenda is clear.
I think what you really want is Agenda Groups where it is partioned based
on some logic - but this is an upcoming drools 3 feature.
in the meantime, you can also iterate through and modify all the objects
that are already in working memory, causing
