[ https://issues.jboss.org/browse/DROOLS-1540?page=com.atlassian.jira.plugi... ] Fabio Bonfante commented on DROOLS-1540: ---------------------------------------- First thank's for the fix, I've looked to the commit and try to figure out how I can safely use drools and the devtools in the future without too much "worries" about versions upgrades (of both of them). I've a couple of questions: # There's a specific version of spring-boot-devtools covered by the fix (1.5.x or 2.x) ? (saw that depends if the classLoader is an OSGI classloader... just for curiosity how this play a role with the devtools?) # Can Drools detect if the object inserted in the kieSession have a different classloader than himself and throws an exception? I can imagine that the kieSession has reference to the classes imported in the drl file, and a check with an object inserted in the session can reveal if the same classes (using Class.getName() for example) have different classloaders. I'm surely missing (probably a lot of) details, but I think an exception like that could be helpful to prevent the current "silent" behaviour (es. [optaplanners rules don't fire|https://stackoverflow.com/questions/35746370/optaplanners-drools-rul...]) in future deployments of drools not limited with this spring-boot-devtools corner case. -- This message was sent by Atlassian Jira (v7.12.1#712002)