blob: cc176f70d55263a8744ce496d57d068fc986e65d [file] [log] [blame]
<?xml version="1.0" encoding="iso-8859-1"?>
~ Licensed to the Apache Software Foundation (ASF) under one
~ or more contributor license agreements. See the NOTICE file
~ distributed with this work for additional information
~ regarding copyright ownership. The ASF licenses this file
~ to you under the Apache License, Version 2.0 (the
~ "License"); you may not use this file except in compliance
~ with the License. You may obtain a copy of the License at
~ Unless required by applicable law or agreed to in writing,
~ software distributed under the License is distributed on an
~ KIND, either express or implied. See the License for the
~ specific language governing permissions and limitations
~ under the License.
<html xmlns="">
<meta name="generator" content=
"HTML Tidy for Windows (vers 14 June 2007), see" />
<meta http-equiv="content-type" content=
"text/html; charset=us-ascii" />
<title>Application Server Specific Configuration Guide</title>
<meta content="amaya 9.2.1, see" />
<link href="../css/axis-docs.css" rel="stylesheet" type="text/css"
media="all" />
<h1>Application Server Specific Configuration Guide</h1>
<p>This document provides configuration information required for
your Application Server to run Apache Axis2 to its fullest
<h3>WebLogic/ WebSphere</h3>
<p><strong>1. Use exploded configuration to deploy Axis2
<p>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 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 the modules and services directory
<li><b>WEB-INF/services/services.list</b> : should list all the
services (aar files) that you want to expose.</li>
<li><b>WEB-INF/modules/modules.list</b> : should list all the
modules (mar files) that you want to use.</li>
NOTE: In both cases, please list one entry per line.
<p>WebLogic ships with JARs that conflict with JARs present in
Axis2. Therefore use &lt;prefer-web-inf-classes&gt; to ensure that
JARs packaged in Axis2 WAR are picked up from WEB-INF/lib. You can
do this by setting the &lt;prefer-web-inf-classes&gt; element in
WEB-INF/weblogic.xml to true. An example of weblogic.xml is shown
<p>If set to true, the &lt;prefer-web-inf-classes&gt; 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.</p>
<p>Please refer to the following documents in WebLogic/ WebSphere
for more information:</p>
<li><a href=
ServerApplication Classloading</a>- For more information on how
WebLogic's class loader works</li>
<li><a href=
a Web Application in Exploded Directory Format</a></li>
<li><a href=
Deploying the Web application in exploded form</a></li>
<p><strong>2. Lack of namespacing on serialised items</strong></p>
<p>BEA WebLogic Server 9.0 comes with its own StAX implementation.
This results in lack of namespacing on serialised items. In turn,
WebLogic server (WLS) breaks with AXIOM on the WLS classpath. Hence
a filtering classloader is required:</p>
<p>Adding the following to weblogic-application.xml should resolve
this issue:</p>
<p>Note that the libraries listed--Xerces, StAX API, Woodstox--need
to be on the application classpath.</p>