Uploaded image for project: 'Magnolia Workflow Module'
  1. Magnolia Workflow Module
  2. MGNLWORKFLOW-267

Library conflict between Workflow with JBPM 6 and Weblogic/Websphere

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • 5.5
    • None
    • None

      Deploying Magnolia with JBPM 6 affects deployment feature of Weblogic/Websphere AS. It does't care if Administration Console, weblogic.Deployer, wldeploy Ant task or auto deploy directory is used all are affected.

      Symptoms:
      Magnolia can't be deployed to Weblogic. "weblogic.application.ModuleException: java.lang.ClassNotFoundException: org.jbpm.services.task.lifecycle.listeners.TaskLifeCycleEventListener". Full stacktrace http://pastebin.com/gsUy28DU

      TaskLifeCycleEventListener is part of jbpm-human-task-core library. This library is excluded from the Workflow bundle. So if you remove exclusions from the workflow pom then "weblogic.application.ModuleException: java.lang.ClassNotFoundException: org.codehaus.janino.util.resource.ResourceFinder".

      ...

      Workaround:
      First deploy application which doesn't contain Magnolia Workflow with jbpm6 (etc. M5.2.2, M5.3 without workflow, etc.). And then in deployment target location replace deployed webapp by new webapp which contains workflow with jbpm6

      Related forum post:
      https://community.jboss.org/thread/237081

        Acceptance criteria

              ejervidalo Espen Jervidalo
              mdivilek Milan Divilek
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: