Page History

...

Oracle WebLogic 12c library conflicts

...

commons-lang

When deploying on Oracle WebLogic 12c, there is a version conflict while using commons-lang. Oracle WebLogic-12c is distributed with commons-lang-2.5.jar, JackRabbit with commons-lang-2.6.jar and Magnolia with commons-lang-2.1.jar.

To resolve this issue, modify setDomainEnv.sh of Oracle WebLogic and add commons-lang-2.6.jar to the PRE_CLASSPATH. 

...

Bouncy Castle

Magnolia uses the Bouncy Castle cryptography package to decode the license key and to secure the activation process. Oracle WebLogic 12c is distributed with bcprov-jdk16-1.45.jar but Magnolia is distributed with bcprov-jdk16-1.46.jar. This leads to a library version conflict.

...

Oracle WebLogic and IBM WebSphere deployment issue with jBPM 6

Google Guava

Magnolia cannot render images stored in dam workspace. Google Guava library is used by the DAM API 2.0 which is used for working with images.jBPM 6 cannot be deployed on Oracle WebLogic or IBM WebSphere. jBPM is included in the Magnolia Workflow module. All deployment methods are affected: Administration Console, Oracle WebLogic.Deployer, wldeploy Ant task and autodeploy directory.

Symptom:

weblogicjava.applicationlang.ModuleExceptionRuntimeException: java.lang.ClassNotFoundExceptionNoClassDefFoundError: org.jbpm.services.task.lifecycle.listeners.TaskLifeCycleEventListener Could not initialize class com.google.common.cache.LocalCache

Workaround:

1. Deploy an application which doesn't contain Magnolia Workflow with jBPM6, for example Magnolia 5.2.2 or Magnolia 5.3 without the Workflow module.
2. In the deployment target location, replace the deployed webapp with a new webapp that contains workflow with jBPM6

Oracle WebLogic 12c conflict with Google Guava library

 Modify the weblogic.xml file in your application's WEB-INF folder with the prefer-application-packages  element:

<container-descriptor>
   <prefer-application-packages>
	 <package-name>com.google.common.*</package-name>
   </prefer-application-packages>
</container-descriptor>

Oracle WebLogic and IBM WebSphere deployment issue with jBPM 6

jBPM 6 cannot be deployed on Oracle WebLogic or IBM WebSphere. jBPM is included in the Magnolia Workflow module. All deployment methods are affected: Administration Console, Oracle WebLogic.Deployer, wldeploy Ant task and autodeploy directoryMagnolia cannot render images stored in dam workspace. Google Guava library is used by the DAM API 2.0 which is used for working with images.

Symptom:

javaweblogic.langapplication.RuntimeExceptionModuleException: java.lang.NoClassDefFoundErrorClassNotFoundException: Could not initialize class com.google.common.cache.LocalCacheorg.jbpm.services.task.lifecycle.listeners.TaskLifeCycleEventListener

Workaround:

 Modify the weblogic.xml file in your application's WEB-INF folder with the prefer-application-packages  element:

...

...

1. Deploy an application which doesn't contain Magnolia Workflow with jBPM6, for example Magnolia 5.2.2 or Magnolia 5.3 without the Workflow module.
2. In the deployment target location, replace the deployed webapp with a new webapp that contains workflow with jBPM6

Oracle WebLogic 12c conflict with Google Guava library

Jetty 9± java.io.IOException stream closed

Magnolia's resource loader makes heavy use of accessing classpath resources (last modification date and contents). Jetty uses caching of such resources by default, which may result in a java.io.IOException occurring randomly. See

...