[jboss-jira] [JBoss JIRA] (JBRULES-2683) DroolsSession's initWorkItemManagerFactory method can not work in a OSGi context

[Geoffrey De Smet (JIRA)]

     [ https://issues.jboss.org/browse/JBRULES-2683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Geoffrey De Smet resolved JBRULES-2683.
---------------------------------------

         Assignee: Geoffrey De Smet  (was: Mark Proctor)
    Fix Version/s: 5.4.0.CR1
                       (was: FUTURE)
       Resolution: Cannot Reproduce Bug


Please reopen if it's still an issue with 5.4.0.CR1 or higher.
                
> DroolsSession's initWorkItemManagerFactory method can not work in a OSGi context
> --------------------------------------------------------------------------------
>
>                 Key: JBRULES-2683
>                 URL: https://issues.jboss.org/browse/JBRULES-2683
>             Project: Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-core
>    Affects Versions: 5.2.0.M1
>            Reporter: Antoine Toulme
>            Assignee: Geoffrey De Smet
>             Fix For: 5.4.0.CR1
>
>
> This affects the current trunk.
> The code in the method does this:
> String className = this.chainedProperties.getProperty( "drools.workItemManagerFactory",
>                                                                "org.drools.process.instance.impl.DefaultWorkItemManagerFactory" );
> [..]
> clazz = (Class<WorkItemManagerFactory>) Thread.currentThread().getContextClassLoader().loadClass( className );
> [..]
> clazz = (Class<WorkItemManagerFactory>) SessionConfiguration.class.getClassLoader().loadClass( className );
> None of this can work for the default factory since drools-core does not depend on drools-flow-core (and creating a dependency would create a cycle). Actually, this won't work for customer code as well, since drools-core won't depend on their bundle.
> I suggest to use a declarative service to work around this problem, while keeping this type of instantiation around when OSGi is not on.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira