Details
-
Bug
-
Resolution: Done
-
Major
-
5.2.0.M1
-
None
Description
This bug occurs when using Drools inside an OSGi environment. The ServiceRegistryImpl is instantiated instead of using the instance singleton, which leads to having objects being registered against the wrong ServiceRegistry. The OSGi class loader won't let the default instantiator work, as the classes are part of a different bundle. As a result, the configuration of the knowledge base fails.
The patch attached fixes this problem, it is a one liner.