Running on WebSphere 6.1
WebSphere 6.1 has a few issues when running applications that use the Atlassian Plugin Framework:
- WebSphere itself is built on OSGi, but it uses an older version of the specification (4.0) whereas the plugin framework expects 4.1.
- The WebSphere classloader does not support classloader scanning, a technique used by the plugin framework to discover which packages are available from the host application. Specifically, the classloader does not return results when looking for packages or directories. This capability is required for most scanning techniques.
The solution is to configure your WebSphere application with the following settings:
- Application classloader policy —
- Application classloader mode —
By setting the classloader to
SINGLE, you ensure that the WebSphere OSGi classes do not override the classes needed by the Atlassian Plugin Framework.
The Atlassian Plugin Framework works around the classpath scanning issue, by scanning your JARs in
WEB-INF/lib and your classes in
WEB-INF/classes instead. This means that common libraries stored in the application server will not be recognised.
For more information see the WebSphere documentation.