unfortunately I don't know enough about spring to say how this works. But my guess is it is being loaded up as part of a listener for servlet context where spring bootstraps stuff.
Basically that needs to be replaced with something you can trigger to force a reload of the rules (basically think of the rulebase a cache, and its time to flush it).
Not sure how to achieve that with what you have, but its easy enough to do many other ways.
Does anyone have the same problem? I'm still stuck in this--On 3/12/07, Carlos Henriquez < carlosalberto.henriquez@gmail.com > wrote:Hi all.
I'm new in this list and I have a year working with rules (integrated with Spring). We are using drools 2.5 despite is legacy.
We want to change rules at runtime without redeploying the whole application. I tried with the ruleAdministrator, deregistering the rule source and registering again but I had a problem creating the RuleExecutionSet with the createRuleExecutionSet method from LocalRuleExecutionSetProvider. It didn't see any of my class and I got a "unable to find class XXX" RuleExecutionSetCreateException every time I tried to create a rule set from a file.
What I don't understand is how does Spring load all my rules the first time? I don't know if I have to set som classpath manually and if I do, where?
I'll appreciate all the help you could give me.
Bye.
--
Carlos Henriquez
+58-416-839.94.28
Carlos Henriquez
Wincor-Nixdorf
+58-416-839.94.28
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users