WebLogic/ WebSphere

We recommend using the exploded configuration to deploy Axis2 WAR in WebLogic and WebSphere application servers to support the hotupdate/ hotdeployment features in Axis2. However if you do want to deploy custom wars say in a clustering environment, You need to add two additional files into the WEB-INF named "services.list" and "modules.list" under modules and services directory respectively.

• WEB-INF/services/services.list : should list all the services (aar files) that you want to expose.
• WEB-INF/modules/modules.list : should list all the modules (mar files) that you want to use.

NOTE: In both cases, please list one entry per line

WebLogic ships with jars which conflict with jars present in Axis2. So, kindly use <prefer-web-inf-classes> to ensure that jars packaged in Axis2 WAR are picked up from WEB-INF/lib. You can do this by setting <prefer-web-inf-classes> element in WEB-INF/weblogic.xml to true. An example of weblogic.xml is shown below:

<weblogic-web-app>
 <container-descriptor>
    <prefer-web-inf-classes>true</prefer-web-inf-classes>
  </container-descriptor>
</weblogic-web-app>

If set to true, the <prefer-web-inf-classes> element will force WebLogic's classloader to load classes located in the WEB-INF directory of a Web application in preference to application or system classes. This is a recommended approach since it only impacts a single Web module.

Please look at the following documents in WebLogic/ WebSphere for more information:

• WebLogic ServerApplication Classloading- For more information on how WebLogic's class loader works
• Redeploying a Web Application in Exploded Directory Format
• Deploying the Web application in exploded form