ServiceRegistryImpl is registered twice: once as a singleton and once as a service tracker ------------------------------------------------------------------------------------------ Key: JBRULES-2682 URL: https://jira.jboss.org/browse/JBRULES-2682 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-api Affects Versions: 5.2.0.M1 Reporter: Antoine Toulme Assignee: Mark Proctor Fix For: FUTURE Attachments: ServiceRegistryImpl.patch 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. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira