Uploaded image for project: 'jBPM'
  1. jBPM
  2. JBPM-4603

RuntimeManagerFactory allows to change the implementing class but not load the alternative implementation from a different ClassLoader

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: jBPM 6.4.0.Beta1
    • Component/s: None
    • Labels:
      None

      Description

      RuntimeManagerFactory allows to define an alternative implementation of its interface via System.property. Unfortunately the class containing this alternative implementation couldn't be loadable from the RuntimeManagerFactory ClassLoader (for instance in a OSGi environment) and the current API doesn't permit to optionally pass the ClassLoader from where the implementing class could be loaded.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  mfusco Mario Fusco
                  Reporter:
                  mfusco Mario Fusco
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: