You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Thomas Diesler (JIRA)" <ji...@apache.org> on 2019/06/17 10:50:01 UTC
[jira] [Created] (CAMEL-13654) optaplanner-7.23 not usable in
wildfly
Thomas Diesler created CAMEL-13654:
--------------------------------------
Summary: optaplanner-7.23 not usable in wildfly
Key: CAMEL-13654
URL: https://issues.apache.org/jira/browse/CAMEL-13654
Project: Camel
Issue Type: Bug
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: 3.0.0
drools-7.23 uses this code in `org.drools.core.common.ProjectClassLoader` ...
{code}
public void setDroolsClassLoader(ClassLoader droolsClassLoader) {
if (getParent() != droolsClassLoader && isOsgiClassLoader(droolsClassLoader)) {
this.droolsClassLoader = droolsClassLoader;
if (CACHE_NON_EXISTING_CLASSES) {
nonExistingClasses.clear();
}
}
}
{code}
drools-7.14 uses
{code}
public void setDroolsClassLoader(ClassLoader droolsClassLoader) {
if (getParent() != droolsClassLoader) {
this.droolsClassLoader = droolsClassLoader;
if (CACHE_NON_EXISTING_CLASSES) {
nonExistingClasses.clear();
}
}
}
{code}
The later version of drools does not allow the CL to get set to anything that is not an OSGi CL. Hence, it will fail in any other modular environment, except OSGi.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)