cvs commit: ws-site/targets/axis/java install.pdf install.html

Thu, 09 Dec 2004 22:30:26 -0800 

toshi       2004/12/09 22:30:25

  Modified:    targets/axis/java install.pdf install.html
  Log:
  Applied the document patch from Dominik Kacprzak to the master.
  
  Revision  Changes    Path
  1.12      +494 -403  ws-site/targets/axis/java/install.pdf
  
        <<Binary file>>
  
  
  1.19      +18 -0     ws-site/targets/axis/java/install.html
  
  Index: install.html
  ===================================================================
  RCS file: /home/cvs/ws-site/targets/axis/java/install.html,v
  retrieving revision 1.18
  retrieving revision 1.19
  diff -u -r1.18 -r1.19
  --- install.html      26 Nov 2004 10:59:03 -0000      1.18
  +++ install.html      10 Dec 2004 06:30:25 -0000      1.19
  @@ -380,6 +380,24 @@
   <h2>Tomcat 4.x and Java 1.4</h2>
   </div>
   <p>Java 1.4 changed the rules as to how packages beginning in java.* and 
javax.* get loaded. Specifically, they only get loaded from <em>endorsed</em> 
directories. jaxrpc.jar and saaj.jar contain javax packages, so they may not 
get picked up. If happyaxis.jsp (see below) cannot find the relevant packages, 
copy them from axis/WEB-INF/lib to CATALINA_HOME/common/lib and restart 
Tomcat.</p>
  +<div class="h2">
  +<h2>WebLogic 8.1</h2>
  +</div>
  +<p>WebLogic 8.1 ships with <span class="codefrag">webservices.jar</span> 
that conflicts with Axis' <span class="codefrag">saaj.jar</span> and prevents 
Axis 1.2 from working right out of the box. This conflict exists because 
WebLogic uses an older definition of <span 
class="codefrag">javax.xml.soap.*</span> package from <a 
href="http://java.sun.com/webservices/docs/1.0/api/javax/xml/soap";>Java Web 
Services Developer Pack Version 1.0</a>, whereas Axis uses a newer revision 
from J2EE 1.4.</p>
  +<p>However, there are two alternative configuration changes that enable Axis 
based web services to run on Weblogic 8.1.</p>
  +<ul>
  +<li>In a webapp containing Axis, set &lt;prefer-web-inf-classes&gt; element 
in <span class="codefrag">WEB-INF/weblogic.xml</span> to true. An example of 
<span class="codefrag">weblogic.xml</span> is shown below: <pre>   
&lt;weblogic-web-app&gt; 
  +    &lt;container-descriptor&gt; 
  +     &lt;prefer-web-inf-classes&gt;true&lt;/prefer-web-inf-classes&gt; 
  +    &lt;/container-descriptor&gt; 
  +   &lt;/weblogic-web-app&gt;</pre>
  +<p>If set to <span class="codefrag">true</span>, the <span 
class="codefrag">&lt;prefer-web-inf-classes&gt;</span> 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>
  +</li>
  +<li>In a script used to start WebLogic server, modify <span 
class="codefrag">CLASSPATH</span> property by placing Axis's <span 
class="codefrag">saaj.jar</span> library in front of WeLlogic's <span 
class="codefrag">webservices.jar</span>. <p>
  +<strong>NOTE:</strong> This approach impacts all applications deployed on a 
particular WebLogic instance and may prevent them from using WebLogic's 
webservices.</p>
  +</li>
  +</ul>
  +<p>For more information on how WebLogic's class loader works, see <a 
href="http://e-docs.bea.com/wls/docs81/programming/classloading.html";>WebLogic 
Server Application Classloading</a>.</p>
   <p>
   <a name="start"></a>
   </p>

Reply via email to