There is a difference. If you use incremental mode if effectively
"diffs" the current kbase with the new kbase, and applies the diff. In
this situation you need the changeset to always include all drls of what
you want the kbase to look like; as it'll build the changeset as a kbase
and then "diff" the original and new.
On 11/07/2012 23:56, lhorton wrote:
Version 5.2.0.Final. I have a DRL file that is loaded into my server
change set and Spring configuration. The file loads without error, and I am
able to read the compiled package and print the rule names to confirm they
did load; however, only one of the rules fires. Then I copy (hot-deploy)
the same DRL file to its server-side directory, and the Resource change
Scanner picks it up and reloads it. After reload, all the expected rules
My guess is that the Spring/KnowledgeAgent compilation is different than the
one done via the resource change scanner. Has anyone else seen this
behavior? Any suggestions for further trouble shooting?
I can attach the change set, spring config and drl file if needed.
View this message in context:
Sent from the Drools: User forum mailing list archive at Nabble.com
rules-users mailing list