Author: veithen
Date: Wed Jun 22 18:53:16 2011
New Revision: 1138582
URL: http://svn.apache.org/viewvc?rev=1138582&view=rev
Log:
AXIS2-4917: Merged r1138144 and r1138203 to the 1.6 branch for inclusion in the
Axis2 1.6.1 site.
Modified:
axis/axis2/java/core/branches/1_6/ (props changed)
axis/axis2/java/core/branches/1_6/src/site/xdoc/docs/app_server.xml
Propchange: axis/axis2/java/core/branches/1_6/
------------------------------------------------------------------------------
--- svn:mergeinfo (original)
+++ svn:mergeinfo Wed Jun 22 18:53:16 2011
@@ -1 +1 @@
-/axis/axis2/java/core/trunk:1070439,1072077,1072271,1072499,1072510,1078242,1081563,1081587,1081590,1082316,1082322,1082600,1082702,1082726,1082738,1083180,1083192,1083379,1083381,1083425,1083433,1083446,1084753,1085514,1087073,1088239,1088248-1088249,1088251,1088268,1091178,1091191,1099385,1099389,1100628,1101037,1103013,1103606,1103760,1128580,1128584,1128618,1128645,1130590,1131425,1134438,1134616,1136156,1136159,1137153,1137159
+/axis/axis2/java/core/trunk:1070439,1072077,1072271,1072499,1072510,1078242,1081563,1081587,1081590,1082316,1082322,1082600,1082702,1082726,1082738,1083180,1083192,1083379,1083381,1083425,1083433,1083446,1084753,1085514,1087073,1088239,1088248-1088249,1088251,1088268,1091178,1091191,1099385,1099389,1100628,1101037,1103013,1103606,1103760,1128580,1128584,1128618,1128645,1130590,1131425,1134438,1134616,1136156,1136159,1137153,1137159,1138144,1138203
Modified: axis/axis2/java/core/branches/1_6/src/site/xdoc/docs/app_server.xml
URL:
http://svn.apache.org/viewvc/axis/axis2/java/core/branches/1_6/src/site/xdoc/docs/app_server.xml?rev=1138582&r1=1138581&r2=1138582&view=diff
==============================================================================
--- axis/axis2/java/core/branches/1_6/src/site/xdoc/docs/app_server.xml
(original)
+++ axis/axis2/java/core/branches/1_6/src/site/xdoc/docs/app_server.xml Wed Jun
22 18:53:16 2011
@@ -1,5 +1,4 @@
<?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
@@ -18,46 +17,39 @@
~ specific language governing permissions and limitations
~ under the License.
-->
-
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
- "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd";>
-<html xmlns="http://www.w3.org/1999/xhtml";>
-<head>
-<meta name="generator" content=
-"HTML Tidy for Windows (vers 14 June 2007), see www.w3.org" />
-<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 http://www.w3.org/Amaya/"; />
-</head>
-<body>
-<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
-potential.</p>
-<h3>WebLogic/ WebSphere</h3>
-<p><strong>1. Use exploded configuration to deploy Axis2
-WAR</strong></p>
-<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
-respectively.</p>
-<ul>
-<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>
-</ul>
-NOTE: In both cases, please list one entry per line.
-<p>WebLogic ships with JARs that conflict with JARs present in
-Axis2. Therefore 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 the <prefer-web-inf-classes> element in
-WEB-INF/weblogic.xml to true. An example of weblogic.xml is shown
-below:</p>
+<document xmlns="http://maven.apache.org/XDOC/2.0";
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
+ xsi:schemaLocation="http://maven.apache.org/XDOC/2.0
http://maven.apache.org/xsd/xdoc-2.0.xsd";>
+ <properties>
+ <title>Application Server Specific Configuration Guide</title>
+ </properties>
+ <body>
+ <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
+ potential.</p>
+ <section name="WebLogic">
+ <subsection name="Use exploded configuration to deploy Axis2 WAR">
+ <p>We recommend using the exploded configuration to deploy
Axis2
+ WAR in WebLogic application server 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
+ respectively.</p>
+ <ul>
+ <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>
+ </ul>
+ NOTE: In both cases, please list one entry per line.
+ <p>WebLogic ships with JARs that conflict with JARs present in
+ Axis2. Therefore 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 the <prefer-web-inf-classes> element
in
+ WEB-INF/weblogic.xml to true. An example of weblogic.xml is
shown
+ below:</p>
<pre>
<weblogic-web-app>
<container-descriptor>
@@ -65,32 +57,30 @@ below:</p>
</container-descriptor>
</weblogic-web-app>
</pre>
-<p>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.</p>
-<p>Please refer to the following documents in WebLogic/ WebSphere
-for more information:</p>
-<ul>
-<li><a href=
-"http://e-docs.bea.com/wls/docs81/programming/classloading.html";>WebLogic
-ServerApplication Classloading</a>- For more information on how
-WebLogic's class loader works</li>
-<li><a href=
-"http://e-docs.bea.com/wls/docs81/webapp/deployment.html";>Redeploying
-a Web Application in Exploded Directory Format</a></li>
-<li><a href=
-"http://publib.boulder.ibm.com/infocenter/wsiihelp/v8r3/index.jsp?topic=/com.ibm.websphere.ii.product.ce.doc/configuring/iiyviigdepwebexpl.htm";>
-Deploying the Web application in exploded form</a></li>
-</ul>
-<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>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.</p>
+ <p>Please refer to the following documents in WebLogic
+ for more information:</p>
+ <ul>
+ <li><a href=
+
"http://e-docs.bea.com/wls/docs81/programming/classloading.html";>WebLogic
+ ServerApplication Classloading</a>- For more information on how
+ WebLogic's class loader works</li>
+ <li><a href=
+
"http://e-docs.bea.com/wls/docs81/webapp/deployment.html";>Redeploying
+ a Web Application in Exploded Directory Format</a></li>
+ </ul>
+ </subsection>
+ <subsection name="Lack of namespacing on serialised items">
+ <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>
<pre>
<prefer-application-packages>
<package-name>com.ctc.wstx.*</package-name>
@@ -98,7 +88,56 @@ this issue:</p>
<package-name>org.apache.*</package-name>
</prefer-application-packages>
</pre>
-<p>Note that the libraries listed--Xerces, StAX API, Woodstox--need
-to be on the application classpath.</p>
-</body>
-</html>
+ <p>Note that the libraries listed--Xerces, StAX API,
Woodstox--need
+ to be on the application classpath.</p>
+ </subsection>
+ </section>
+ <section name="WebSphere">
+ <subsection name="Avoiding conflicts with WebSphere's JAX-WS
runtime">
+ <p>
+ The JAX-WS runtime in WebSphere Application Server is
based on a modified version of Axis2 and these
+ classes are visible to application class loaders. This
means that when deploying
+ a standard version of Axis2 on WAS 7.0 (and WAS 6.1 with
the Web Services feature pack installed),
+ special configuration is required to avoid conflicts with
the Axis2 classes used internally by WebSphere.
+ In particular it is necessary to change the class loader
policy of the Web module to parent last. However,
+ this is not sufficient because Axis2 creates additional
class loaders for modules and services, and
+ these use parent first class loading by default.
Therefore, two things must be done to make a standard
+ Axis2 distribution work with WebSphere:
+ </p>
+ <ol>
+ <li>
+ Before deploying the Axis2 WAR, edit the
<tt>axis2.xml</tt> file and set the
+ <tt>EnableChildFirstClassLoading</tt> parameter to
<tt>true</tt>.
+ Please note that this parameter is only supported in
Axis2 1.5.5 or higher.
+ </li>
+ <li>
+ After deployment, modify the application configuration
to enable parent last class loading
+ for the Web module: in the WebSphere admin console, go
the the configuration page for
+ the enterprise application, click on <em>Manage
Modules</em> and locate the WAR containing
+ Axis2 (in the default WAR distribution, the module is
called <em>Apache-Axis2</em>), then
+ change the <em>Class loader order</em> option to
<em>Classes loaded with local class
+ loader first (parent last)</em>. Note that the class
loader policy for the enterprise
+ application itself (which can be specified under
<em>Class loading and update detection</em>)
+ is irrelevant, unless a custom EAR distribution is
used that includes the Axis2 libraries
+ in the EAR instead of the WAR.
+ </li>
+ </ol>
+ </subsection>
+ <subsection name="Deploying services and modules">
+ <p>
+ By default (i.e. if the <em>Distribute application</em>
option has not been disabled explicitly)
+ WebSphere will deploy the application in exploded form.
The standard location for these files is
+ in the <tt>installedApps</tt> subdirectory in the
WebSphere profile directory. This means that AAR
+ and MAR files can simply be deployed by dropping them into
the corresponding folders. In this
+ scenario, hot deployment is supported and there is no need
to update the <tt>services.list</tt>
+ and <tt>modules.list</tt> files.
+ </p>
+ <p>
+ However, the directory is still under control of WebSphere
and manually deployed AAR and MAR files
+ will be removed e.g. when the application is upgraded. It
may therefore be a good idea to configure
+ Axis2 to use a repository location outside of the
<tt>installedApps</tt> directory.
+ </p>
+ </subsection>
+ </section>
+ </body>
+</document>
