You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-dev@xml.apache.org by na...@apache.org on 2002/05/16 15:27:23 UTC
cvs commit: xml-soap/java/docs/install FAQ_Tomcat_SOAP_SSL.html JRun.html iPlanet.html index.html tomcat.html weblogic51.html weblogic60.html websphere.html
nagy 02/05/16 06:27:23
Modified: java/docs changes.html head.html
java/docs/guide interop.html
java/docs/install FAQ_Tomcat_SOAP_SSL.html JRun.html
iPlanet.html index.html tomcat.html weblogic51.html
weblogic60.html websphere.html
Log:
Changed 2.2 references to 2.3
Revision Changes Path
1.18 +245 -2 xml-soap/java/docs/changes.html
Index: changes.html
===================================================================
RCS file: /home/cvs/xml-soap/java/docs/changes.html,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- changes.html 29 May 2001 19:27:07 -0000 1.17
+++ changes.html 16 May 2002 13:27:22 -0000 1.18
@@ -1,9 +1,10 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type"
content="text/html; charset=iso-8859-1">
-<meta name="GENERATOR" content="Microsoft FrontPage Express 2.0">
+<META name="GENERATOR" content="IBM WebSphere Homepage Builder V4.0.0 for Linux">
<title></title>
</head>
@@ -15,7 +16,249 @@
most recent version is at the top.</p>
<ul>
- <li><a name="v2.2"><strong>Version 2.2</strong></a> <ul>
+ <LI><STRONG>Version 2.3</STRONG><A name="v2.2"></A>
+ <UL>
+ <LI>Changed default schema to 2001 spec.
+ <LI>Reflected timeInstant -> dateTime change
+ in 2001 schema spec.
+ <LI>Added support for primitive XSD data type
+ hexBinary.
+ <LI>Added support for 2001:base64Binary.
+ <LI>Added HTTPS proxy support.
+ <LI>
+ Made several changes to reduce the overhead
+ of a SOAPMappingRegistry creation and
+ also
+ to reduce the number of SMRs created.
+ <LI>Removed SMR constructor which took the schema
+ namespace URI because it doesn't work
+ (new'ing
+ an SMR with the desired URI isn't enough
+ to make the entire thing use that schema
+ URI).
+ <LI>Added a getParent() method to SOAPMappingRegistry
+ to allow the registry tree to be walked-up.
+ <LI>Added a test to the SOAPMappingRegistry so
+ that null strings get serialized correctly.
+ <LI>Fixed a bug that prevents the default encoding
+ from being correctly applied in the SOAPMappingRegistry.
+ <LI>The SOAPMappingRegistry class, a subclass
+ of XMLJavaMappingRegistry, now supports
+ chaining,
+ i.e. an instance has a parent, with the
+ parent
+ being null for the "root" instance.
+ When looking up a mapping, the chain
+ is followed
+ if necessary to resolve the mapping.
+ <LI>The XMLJavaMappingRegistry class has a method
+ setDefaultEncodingStyle, which sets the
+ default
+ encoding style. When this method is called
+ on a SOAPMappingRegistry instance, the
+ default
+ encoding style is set only for the particular
+ link in the chain. It is *not* set for
+ the
+ parent (and recursively for all parents).
+ This breaks the proper application of
+ the
+ default.
+ <LI>Fixed encoding in SOAPHTTPConnection for
+ systems whose default codepage is not
+ 8859_1.
+ <LI>Add deployment descriptor to the bag in SOAPContext
+ so people can query the data in it.
+ <LI>Fixed the popPollDelay constructor argument
+ in SOAPSMTPConnection so that it is no
+ longer
+ being ignored.
+ <LI>Put the port number back in the HTTP host
+ header.
+ <LI>Fixed the behavior of ExceptionFaultListener.
+ It was previously not looking in the
+ right
+ place for the type of the detail entry
+ to
+ be unmarshalled. It was also not printing
+ the encodingStyle attribute.
+ <LI>Within SOAPException, the fault code and
+ exception message will now be run through
+ Utils.cleanString(...) to escape special
+ characters.
+ <LI>"Clean" stack tracebacks. In particular,
+ constructors appear in stack tracebacks
+ as
+ <init> methods.
+ <LI>
+ Fixed the deployment descriptor so javaType=
+ doesn't get output if the value is null.
+ <LI>Fixed a bug that prevented a service's method
+ from taking a Hashtable, array, or Vector,
+ as a parameter, while returning a DOM
+ Element.
+ <LI>Fixed the documentation and code for the
+ Base64 class so that they match, and
+ so that
+ encode uses its len parameter correctly.
+ <LI>Fixed a bug that prevented the client from
+ using a BeanSerializer to serialize SOAP-encoded
+ parameters within a Call labeled with
+ the
+ literalXML encoding style.
+ <LI>The BooleanDeserializer has been updated
+ to be very liberal in what it will accept;
+ per the spec, 0 and 1 are valid boolean
+ values
+ (and, in fact, are the ones used by the
+ WhiteMesa
+ implementation).
+ <LI>Synchronized calls to DateFormat's methods,
+ since DateFormat appears to not be thread-safe.
+ <LI>Serialize dates without losing precision
+ (the JDK format is contains milliseconds).
+ Deserialize dates with any number of
+ digits
+ of fractional seconds, and with or without
+ a time zone offset.
+ <LI>Fixed a NullPointerException that was being
+ thrown when a DataSource was passed as
+ the
+ source parameter within the MimePartSerializer.
+ <LI>Started to add the ability to serialize elements
+ with qualified names. If PrefixedName
+ objects
+ are not explicitly used as the context
+ arguments
+ for serialization, the behavior is exactly
+ the same as it was before.
+ <LI>
+ Fixed a bug in the EJB providers which
+ printed
+ out the wrong error message.
+ <LI>Changed context intialization within the
+ EJB providers to allow the specification
+ of the PROVIDER_URL and INITIAL_CONTEXT_FACTORY
+ separately.
+ <LI>Put in the non-debug version of the COM provider.
+ <LI>
+ Added a method to remove a body part
+ from
+ a Call object.
+ <LI>
+ Fixed a problem that would cause a Call
+ object's
+ targetObjectURI property to get set to
+ null
+ if a Fault was returned.
+ <LI>Pass the actual encoding style on the Call
+ constructor. Solves a literal XML interop
+ problem with pocket soap.
+ <LI>
+ Fixed a bug that was causing an attribute
+ to be printed without a closing ".
+ <LI>
+ The DeploymentDescriptor will now allow
+ a
+ TypeMapping to be specified without the
+ elementType.
+ <LI>Made the DeploymentDescriptor and TypeMappings
+ serializing/deserializing logic more
+ tolerant
+ of null values.
+ <LI>Fixed the DeploymentDescriptor.toString()
+ method to correctly display the TypeMappings.
+ <LI>
+ Removed debug println from the DeploymentDescriptor.
+ <LI>
+ Add support for opts on java and script
+ services
+ in the dd.xml file.
+ <LI>A type-check was not being performed in the
+ ServiceManager due to its placement.
+ It has
+ been moved so that it now has effect.
+ <LI>Added support for setting the configuration
+ file name as a Web application context
+ parameter
+ so that it will be picked up by the JSPs
+ as well as the router servlets. This
+ will
+ fix the problem of the JSPs using the
+ default
+ ConfigMananger when one has been specified
+ for the router servlets.
+ <LI>Fixed problem of attempting to store null
+ as the classloader in the servlet attributes.
+ <LI>Made the servlets store the classloader from
+ the thread instead of theirs.
+ <LI>Removed 2 server-side stack traces from the
+ servlets where exceptions were also being
+ propagated.
+ <LI>Made the ServerHTTPUtils.readEnvelopeFromRequest(...)
+ method public, instead of the default
+ package
+ access.
+ <LI>The code will now only store the target object
+ in the ServletContext or HTTPSession
+ when
+ it is newly created, and will not store
+ it
+ on each invocation.
+ <LI>Added a patch to SOAPHTTPConnection that
+ makes the set-cookie and set-cookie2
+ header
+ searches case-insensitive.
+ <LI>Fixed exceptions that are thrown from HTTPUtils,
+ so that they contain more helpful messages.
+ <LI>Ensure request URI contains at least one
+ character.
+ <LI>Fixed a StringOutOfBoundsException that was
+ being thrown when a server returned a
+ header
+ with no value to an Apache SOAP client.
+ <LI>Added a method to DOMUtils to retrieve qualified
+ attribute value. That is, it will returna
+ QName representing the value of the requested
+ attribute.
+ <LI>Fixed a problem with QName that Was causing
+ it to throw a NullPointerException if
+ localPart
+ constructor arg was null.
+ <LI>
+ Fixed a missing closing </a> tag
+ in
+ list.jsp.
+ <LI>Build now allows dist target to build when
+ ejb is not present.
+ <LI>Added support for config file element to
+ allow users to enable or disable SOAP
+ interface
+ to Service Manager.
+ <LI>Changed all samples to use the Fault class's
+ toString() method, instead of calling
+ the
+ getFaultCode() and getFaultString() methods.
+ This will cause the samples to display
+ all
+ the fault information, and not just parts
+ of it.
+ <LI>Added a new calculator demo that simulates
+ a reverse polish notation calculator.
+ <LI>Fixed the EJB sample so that the correct
+ parameters are passed to the EJB method.
+ <LI>Fixed up the interop sample and added support
+ for the echoMap service.
+ <LI>Updated to reflect Java 1.2+ requirement.
+ <LI>Fixed some typos in the documentation.
+ <LI>Fixed WAS 3.5 instructions for using the
+ correct Xerces JAR.
+ <LI>Updated deployment descriptor schema to reflect
+ the mapping QName being made optional.
+ </UL>
+</UL>
+ <UL>
+ <li><a name="v2.2"><strong>Version 2.2</strong></a> <ul>
<li>Changed all code and samples to use JAXP; no
longer bound to Xerces.</li>
<li>Removed many printlns from the server-side code,
1.3 +4 -1 xml-soap/java/docs/head.html
Index: head.html
===================================================================
RCS file: /home/cvs/xml-soap/java/docs/head.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- head.html 16 May 2001 03:58:35 -0000 1.2
+++ head.html 16 May 2002 13:27:22 -0000 1.3
@@ -1 +1,4 @@
-<h1><center>Apache SOAP v2.2 Documentation</center></h1>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<HTML><HEAD>
+<META name="GENERATOR" content="IBM WebSphere Homepage Builder V4.0.0 for Linux"></HEAD><BODY><center><h1>Apache SOAP v2.3 Documentation</h1></center>
+</BODY></HTML>
\ No newline at end of file
1.4 +1 -1 xml-soap/java/docs/guide/interop.html
Index: interop.html
===================================================================
RCS file: /home/cvs/xml-soap/java/docs/guide/interop.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- interop.html 29 Jun 2001 15:03:57 -0000 1.3
+++ interop.html 16 May 2002 13:27:22 -0000 1.4
@@ -284,7 +284,7 @@
</li>
</ul>
-<p>The "bidybuy" sample in the Apache SOAP v2.2 release
+<p>The "bidybuy" sample in the Apache SOAP v2.3 release
is an implementation of the "Bid Buy" test developed by
the SOAP Builders forum. It provides a fairly comprehensive
example of implementing a non-trivial interoperable Web service
1.3 +1 -1 xml-soap/java/docs/install/FAQ_Tomcat_SOAP_SSL.html
Index: FAQ_Tomcat_SOAP_SSL.html
===================================================================
RCS file: /home/cvs/xml-soap/java/docs/install/FAQ_Tomcat_SOAP_SSL.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- FAQ_Tomcat_SOAP_SSL.html 16 May 2001 04:02:12 -0000 1.2
+++ FAQ_Tomcat_SOAP_SSL.html 16 May 2002 13:27:23 -0000 1.3
@@ -224,7 +224,7 @@
<Parameter name="socketFactory" value="org.apache.tomcat.net.SSLSocketFactory" />
-<b><Parameter name="keystore" value="c:\apache\soap-2_2\bin\server.keystore" />
+<b><Parameter name="keystore" value="c:\apache\soap-2_3\bin\server.keystore" />
</b><Parameter name="keypass" value="changeit"/>
1.5 +1 -1 xml-soap/java/docs/install/JRun.html
Index: JRun.html
===================================================================
RCS file: /home/cvs/xml-soap/java/docs/install/JRun.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- JRun.html 16 May 2001 03:58:36 -0000 1.4
+++ JRun.html 16 May 2002 13:27:23 -0000 1.5
@@ -9,7 +9,7 @@
<body bgcolor="#FFFFFF">
-<h1 align="center">Apache-SOAP Version 2.2: Installing the Server-Side Under JRun 3.0</h1>
+<h1 align="center">Apache-SOAP Version 2.3: Installing the Server-Side Under JRun 3.0</h1>
<p><strong>IMPORTANT</strong>: JRun comes with an XML parser, which will by default hide Xerces and therefore cause problems with your SOAP installation. Please follow step 1 below!</p>
1.3 +10 -10 xml-soap/java/docs/install/iPlanet.html
Index: iPlanet.html
===================================================================
RCS file: /home/cvs/xml-soap/java/docs/install/iPlanet.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- iPlanet.html 29 May 2001 16:05:39 -0000 1.2
+++ iPlanet.html 16 May 2002 13:27:23 -0000 1.3
@@ -6,7 +6,7 @@
<BODY bgColor=#ffffff>
<H1><B><FONT size=+3>Installing Apache SOAP on iPlanet Application
Server</FONT></B></H1><I>Updated May 24, 2001</I>
-<P>This document describes how to install Apache SOAP 2.2 on iPlanet Application
+<P>This document describes how to install Apache SOAP 2.3 on iPlanet Application
Server 6.0 and how to exercise the Apache SOAP samples.
<BLOCKQUOTE>
<P><A href="#install-apache-soap">Installing Apache SOAP</A>
@@ -57,7 +57,7 @@
<P>Download a copy of a JAXP compatible, namespace-aware XML parser such as
Xerces. Version 1.4 or later of the <A
href="http://xml.apache.org/xerces-j/">Xerces Java Parser</A> has been shown to
-work properly with Apache SOAP 2.2.</P>
+work properly with Apache SOAP 2.3.</P>
<P>To avoid conflicts with the XML parser bundled with the application server,
you must ensure that the JAXP compatible parser library appears at the start of
the application server's classpath.</P>
@@ -196,23 +196,23 @@
<TD width="39%"><I><FONT face="Courier New, Courier, mono" color=#000099
size=2>xercesinstalldir</FONT></I><FONT face="Courier New, Courier, mono"
color=#000099 size=2>/xerces.jar</FONT></TD></TR></TBODY></TABLE>
-<P>To register and run the Apache SOAP 2.2 samples, you also need to add the
+<P>To register and run the Apache SOAP 2.3 samples, you also need to add the
location of the samples directory to your client classpath. </P>
<P>On Windows, the client classpath setting might resemble the following:</P>
<BLOCKQUOTE>
<P><FONT face="Courier New, Courier, mono" color=#000099 size=2>set
IAS_HOME=d:\iplanet\ias6\ias<BR>set
- CLASSPATH=%IAS_HOME%\classes\java\mail.jar;%IAS_HOME%\classes\java\activation.jar;<BR>c:\xerces-1_4_0\xerces.jar;c:\soap-2_2\lib\soap.jar;c:\soap-2_2;%CLASSPATH%
+ CLASSPATH=%IAS_HOME%\classes\java\mail.jar;%IAS_HOME%\classes\java\activation.jar;<BR>c:\xerces-1_4_0\xerces.jar;c:\soap-2_3\lib\soap.jar;c:\soap-2_3;%CLASSPATH%
</FONT></P></BLOCKQUOTE>
<P>On UNIX, the client classpath setting might resemble the following:</P>
<BLOCKQUOTE>
<P><FONT color=#000099>export <FONT face="Courier New, Courier, mono"
size=2>IAS_HOME=/usr/iplanet/ias6/ias</FONT><BR><FONT
face="Courier New, Courier, mono" size=2>export
- CLASSPATH=$IAS_HOME/classes/java/mail.jar:$IAS_HOME/classes/java/activation.jar:<BR>/opt/xerces-1_4_0/xerces.jar:/opt/soap-2_2/lib/soap.jar:/opt/soap-2_2:$CLASSPATH</FONT></FONT></P></BLOCKQUOTE>
+ CLASSPATH=$IAS_HOME/classes/java/mail.jar:$IAS_HOME/classes/java/activation.jar:<BR>/opt/xerces-1_4_0/xerces.jar:/opt/soap-2_3/lib/soap.jar:/opt/soap-2_3:$CLASSPATH</FONT></FONT></P></BLOCKQUOTE>
<H1><A name=register-samples></A><B>Registering and Exercising the Apache SOAP
Samples</B> </H1>
-<P>Each sample bundled with Apache SOAP 2.2 includes a script to register and
+<P>Each sample bundled with Apache SOAP 2.3 includes a script to register and
exercise the samples. Since the supporting Java classes for the Apache SOAP
sample services have already been deployed as part of the SOAP web application,
you do not need to move these classes to the application server. The sample
@@ -239,7 +239,7 @@
<P>Doublecheck to ensure that your client's classpath is set appropriately. Then
execute the testit script. For example, when running the addressbook sample, you
should see the following output in the client window:</P>
-<BLOCKQUOTE><PRE><FONT color=#000099>D:\soap-2_2\samples\addressbook>testit<BR>This test assumes a server URL of http://127.0.0.1/NASApp/soap/servlet/rpcrouter</FONT></PRE><PRE><FONT color=#000099>Deploying the addressbook service...
+<BLOCKQUOTE><PRE><FONT color=#000099>D:\soap-2_3\samples\addressbook>testit<BR>This test assumes a server URL of http://127.0.0.1/NASApp/soap/servlet/rpcrouter</FONT></PRE><PRE><FONT color=#000099>Deploying the addressbook service...
.
Verify that it's there
Deployed Services:
@@ -263,7 +263,7 @@
<P>If you encounter the following messages when running a sample, the most
likely cause is not having the JAXP compatible parser library at the front of
the server's classpath:</P>
-<BLOCKQUOTE><PRE><FONT color=#000099>D:\soap-2_2\samples\addressbook>testit
+<BLOCKQUOTE><PRE><FONT color=#000099>D:\soap-2_3\samples\addressbook>testit
This test assumes a server URL of http://127.0.0.1/NASApp/soap/servlet/rpcr
Deploying the addressbook service...
@@ -345,13 +345,13 @@
<P>For the purposes of specifying the location of a service configuration file,
the <FONT face="Courier New, Courier, mono" color=#000099 size=2>soap.xml</FONT>
file takes the following form:</P>
-<BLOCKQUOTE><PRE><FONT color=#000099><soapServer><BR> <configManager value="org.apache.soap.server.DefaultConfigManager" ><BR> <option name="filename" value="d:\soap-2_2\DeployedServices.ds" /><BR> </configManager><BR></soapServer></FONT></PRE></BLOCKQUOTE>
+<BLOCKQUOTE><PRE><FONT color=#000099><soapServer><BR> <configManager value="org.apache.soap.server.DefaultConfigManager" ><BR> <option name="filename" value="d:\soap-2_3\DeployedServices.ds" /><BR> </configManager><BR></soapServer></FONT></PRE></BLOCKQUOTE>
<H2>Adding ConfigFile Servlet Initialization Parameter</H2>
<P>In the <FONT face="Courier New, Courier, mono" color=#000099
size=2>web.xml</FONT> file, the initialization parameters in the web application
deployment descriptor takes the following form:</P>
<BLOCKQUOTE><PRE><FONT color=#000099><servlet><BR> <servlet-name>messagerouter</servlet-name><BR> <display-name>Apache-SOAP Message Router</display-name><BR> <servlet-class>org.apache.soap.server.http.MessageRouterServlet</servlet-class><BR> <init-param><BR> <param-name>faultListener</param-name><BR> <param-value>org.apache.soap.server.DOMFaultListener</param-value><BR> </init-param>
- <B><init-param><BR> <param-name>ConfigFile</param-name><BR> <param-value>d:\soap-2_2\soap.xml</param-value><BR> </init-param></B><BR></servlet></FONT></PRE></BLOCKQUOTE>
+ <B><init-param><BR> <param-name>ConfigFile</param-name><BR> <param-value>d:\soap-2_3\soap.xml</param-value><BR> </init-param></B><BR></servlet></FONT></PRE></BLOCKQUOTE>
<P>The new<FONT size=2> <FONT face="Courier New, Courier, mono"
color=#000099><init-param></FONT></FONT> must be added to the <FONT
face="Courier New, Courier, mono" color=#000099 size=2><servlet></FONT>
1.25 +7 -5 xml-soap/java/docs/install/index.html
Index: index.html
===================================================================
RCS file: /home/cvs/xml-soap/java/docs/install/index.html,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -r1.24 -r1.25
--- index.html 28 Aug 2001 20:37:27 -0000 1.24
+++ index.html 16 May 2002 13:27:23 -0000 1.25
@@ -1,15 +1,17 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type"
content="text/html; charset=iso-8859-1">
-<meta name="GENERATOR" content="Microsoft FrontPage Express 2.0">
+<META name="GENERATOR" content="IBM WebSphere Homepage Builder V4.0.0 for Linux">
<title>Apache SOAP Installation Instructions</title>
</head>
<body bgcolor="#FFFFFF">
-<h2 align="center">Installation Instructions for Apache SOAP v2.2</h2>
+<h2 align="center">Installation Instructions for Apache SOAP
+v2.3</h2>
<p>The Apache-SOAP distribution can be installed for use as a
client or as a server. This document provides installation
@@ -37,7 +39,7 @@
<p>We assume that you have downloaded the binary distribution of
Apache-SOAP and have extracted the archive into the directory <tt>/foo</tt>.
-Thus the files from the distribution are in the directory <tt>/foo/soap-2_2/</tt>.</p>
+Thus the files from the distribution are in the directory <tt>/foo/soap-2_3/</tt>.</p>
<p>Note that if you are on a Win32 machine then you should
replace "/" with "\" as you follow these
@@ -45,7 +47,7 @@
<h3>Client-Side Instructions</h3>
-<p>Your classpath must contain <strong>/foo/soap-2_2/lib/soap.jar</strong>
+<p>Your classpath must contain <strong>/foo/soap-2_3/lib/soap.jar</strong>
and the following:</p>
<ul>
@@ -64,7 +66,7 @@
</ul>
<p>Additionally, to run the samples that came with the
-distribution, add <strong>/foo/soap-2_2</strong> to your
+distribution, add <strong>/foo/soap-2_3</strong> to your
classpath.</p>
<h3>Server-Side Instructions</h3>
1.10 +4 -4 xml-soap/java/docs/install/tomcat.html
Index: tomcat.html
===================================================================
RCS file: /home/cvs/xml-soap/java/docs/install/tomcat.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- tomcat.html 16 May 2001 18:02:33 -0000 1.9
+++ tomcat.html 16 May 2002 13:27:23 -0000 1.10
@@ -7,7 +7,7 @@
<body bgcolor="#FFFFFF">
-<h1 align="center">Apache-SOAP Version 2.2: Installing the Server Side
+<h1 align="center">Apache-SOAP Version 2.3: Installing the Server Side
Under Apache Tomcat v3.2</h1>
<h2>Getting Tomcat ready:</h2>
@@ -41,10 +41,10 @@
<h3>Method 1: Deploying the web archive.</h3>
-<p>The Apache SOAP distribution includes a web archive at <code>/soap-2_2/webapps/soap.war</code>.
+<p>The Apache SOAP distribution includes a web archive at <code>/soap-2_3/webapps/soap.war</code>.
Simply drop this web archive into Tomcat's webapps directory (i.e. <code>%tomcat_home%/webapps</code>).
If you deploy Apache SOAP into Tomcat in this manner, you will not need to have anything from the
-<code>/soap-2_2</code> directory on your server's classpath (the relevant items are included in the web
+<code>/soap-2_3</code> directory on your server's classpath (the relevant items are included in the web
archive). Note: If you copy the web archive into the webapps directory while Tomcat is running, Tomcat
will need to be restarted before the Apache SOAP web application can be accessed.</p>
@@ -65,7 +65,7 @@
<p>Now, make sure you have the jar files from the lib directory
of this distribution on your classpath and start up tomcat. Also,
you will want to have on the classpath any of your code that you
-want to deploy as services (e.g. <code>/soap-2_2</code> if you want to deploy
+want to deploy as services (e.g. <code>/soap-2_3</code> if you want to deploy
any of the included samples).</p>
<h2>Accessing the Apache SOAP context:</h2>
1.2 +1 -1 xml-soap/java/docs/install/weblogic51.html
Index: weblogic51.html
===================================================================
RCS file: /home/cvs/xml-soap/java/docs/install/weblogic51.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- weblogic51.html 19 May 2001 05:24:34 -0000 1.1
+++ weblogic51.html 16 May 2002 13:27:23 -0000 1.2
@@ -9,7 +9,7 @@
<body bgcolor="#FFFFFF">
-<h1 align="center">Apache-SOAP Version 2.2: Installing the Server-Side Under WebLogic
+<h1 align="center">Apache-SOAP Version 2.3: Installing the Server-Side Under WebLogic
Application Server 5.1</h1>
<p><strong>IMPORTANT</strong>: WebLogic comes with an XML parser. So, you must
1.3 +1 -1 xml-soap/java/docs/install/weblogic60.html
Index: weblogic60.html
===================================================================
RCS file: /home/cvs/xml-soap/java/docs/install/weblogic60.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- weblogic60.html 19 May 2001 05:27:00 -0000 1.2
+++ weblogic60.html 16 May 2002 13:27:23 -0000 1.3
@@ -5,7 +5,7 @@
<META content="Dion Almaer" name=author>
<META content="MSHTML 5.50.4613.1700" name=GENERATOR></HEAD>
<BODY bgColor=#ffffff>
-<H1 align=center>Apache-SOAP Version 2.2: Installing the Server-Side Under BEA
+<H1 align=center>Apache-SOAP Version 2.3: Installing the Server-Side Under BEA
WebLogic Application Server 6.0</H1>
<P>Installing SOAP with BEA WebLogic is very straight foreward. <BR>The steps
are: <BR>
1.6 +4 -4 xml-soap/java/docs/install/websphere.html
Index: websphere.html
===================================================================
RCS file: /home/cvs/xml-soap/java/docs/install/websphere.html,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- websphere.html 6 May 2002 15:20:54 -0000 1.5
+++ websphere.html 16 May 2002 13:27:23 -0000 1.6
@@ -10,7 +10,7 @@
<body bgcolor="#FFFFFF">
-<h1 align="center">Apache-SOAP Version 2.2: Installing the Server-Side
+<h1 align="center">Apache-SOAP Version 2.3: Installing the Server-Side
Under IBM WebSphere Advanced Edition</h1>
<p>These instructions assume:</p>
@@ -75,11 +75,11 @@
</OL>
</li><li><p>In the tree view, open the SoapWebApp, and select the Advanced tab:
<ol>
- <li><p>Change Document Root to "C:\install-dir\soap-2_2\webapps\soap".</li>
+ <li><p>Change Document Root to "C:\install-dir\soap-2_3\webapps\soap".</li>
<li><p>Set the classpath to
<ul>
- <li><p><code>C:\XML\apache\soap-2_2\lib\soap.jar</code></li>
- <li><p><code>C:\XML\apache\soap-2_2</code></li>
+ <li><p><code>C:\XML\apache\soap-2_3\lib\soap.jar</code></li>
+ <li><p><code>C:\XML\apache\soap-2_3</code></li>
<li><p><code>C:\tools\BSF\lib\bsf.jar</code></li>
<li><p><code>C:\tools\BSF\lib\bsfengines.jar</code></li>
<li><p><code>C:\Tools\Rhino\js.jar</code></li>