[
https://issues.jboss.org/browse/DROOLS-1540?page=com.atlassian.jira.plugi...
]
Mario Fusco resolved DROOLS-1540.
---------------------------------
Resolution: Rejected
This is not a Drools issue. The problem is that when using devtools the Message instance
doesn't come from the launcher classloader, but from a different one named
org.springframework.boot.devtools.restart.classloader.RestartClassLoader and then Drools
is no longer able to match it.
I think you can maybe workaround the problem as explained here
https://docs.spring.io/spring-boot/docs/current/reference/html/using-boot...
but I strongly suggested to introduce tools like this that change the classes of your
domain objects at runtime.
Drools does not work with spring-boot-devtools
----------------------------------------------
Key: DROOLS-1540
URL:
https://issues.jboss.org/browse/DROOLS-1540
Project: Drools
Issue Type: Bug
Components: core engine
Affects Versions: 6.5.0.Final
Reporter: G Xiong
Assignee: Mario Fusco
Priority: Critical
Attachments: complete.zip
Drools does work with spring-boot-devtools.
If you add in pom.xml the following, no rules will be fired in Drools.
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-devtools</artifactId>
</dependency>
if you comment out this, then rules will be fired in Drools.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)