[
https://issues.jboss.org/browse/DROOLS-1540?page=com.atlassian.jira.plugi...
]
Mario Fusco commented on DROOLS-1540:
-------------------------------------
[~fabio.bonfante] As found by [~awilkinson] (thanks for it) the problem was caused by that
additional droolsClassLoader referenced by our ProjectClassLoader. That (ugly) ack is only
necessary when you run inside an OSGi container, but we were use it regardless. What
I'm doing now is just limiting the scope of the ack only when you're effectively
running inside OSGi, thus eliminating the cause of the problem with spring-boot-devtools
when you aren't.
As for your 2nd question we could in theory do what you wrote, but this will require some
reflection and slow down the whole engine for something that is useless in 99.9% of cases,
so I don't t think it would be a good idea.
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, 7.20.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.12.1#712002)