I am packaging my rules as a drl source file in a jar that is then bundled in a war file that is then deployed to Tomcat. In my implementation, the rulebase is cached the first time it is used in my application, but when I add new rules to the source file and rebuild my application then redeploy it on Tomcat, the new version of the rules don't get loaded into the rulebase.
Why and how is an older version of the rules being loaded into the rulebase when I redeploy my application in Tomcat? As FYI, I have developed a business rules service that initializes the rulebase upon a Spring container startup by loading the drl file from the classpath. Is there an internal Drools static cache that is scoped to something other than my application? The only thing I can do to load the new rules is restart Tomcat. When I do this, the new version of the drl source file is loaded and used, so I'm thinking the problem I'm having is somehow related to the class loaders Tomcat uses, but I can't find information about what Drools might be doing internally with a static cache or something like that. Can anyone explain what might be happening and how to configure Drools and/or my application to get around this problem I'm having? I definitely appreciate any help you can provide! Keith _______________________________________________ rules-users mailing list rules-users@lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users
