![]() |
|
|
|
|
Change By:
|
Milan Divilek
(30/Jul/14 9:04 PM)
|
|
Description:
|
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
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <dev-list-unsubscr...@magnolia-cms.com>
----------------------------------------------------------------
