roshan 2004/07/27 21:37:48
Modified: targets/axis/cpp winuser-guide.pdf winuser-guide.html
windev-guide.html linuser-guide.pdf
linuser-guide.html
Log:
Added the location of the latest jars to Linux User Guide,Win Dev Guide & Win User
Guide.Changed by Rangika
Revision Changes Path
1.22 +183 -153 ws-site/targets/axis/cpp/winuser-guide.pdf
<<Binary file>>
1.22 +5 -1 ws-site/targets/axis/cpp/winuser-guide.html
Index: winuser-guide.html
===================================================================
RCS file: /home/cvs/ws-site/targets/axis/cpp/winuser-guide.html,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- winuser-guide.html 13 Jul 2004 09:56:35 -0000 1.21
+++ winuser-guide.html 28 Jul 2004 04:37:46 -0000 1.22
@@ -338,7 +338,11 @@
</div>
<br>
<p>To use WSDL2Ws java tool on the command line you require jdk1.4 or above.<br>
-<br>To use WSDL2Ws java tool you have to set the CLASSPATH Environment Variable to
point to the following jar files in AXIS_EXTRACT\lib\axisjava.<br>
+<br>To use WSDL2Ws java tool you have to set the CLASSPATH Environment Variable to
point to the following latest jar files.<br>
+<br>
+<strong>Note:</strong> The latest jar files are in <a
href="http://apache.towardex.com/ws/axis/1_2beta/";>http://apache.towardex.com/ws/axis/1_2beta/</a>
+<br>
+<br>
<br>axis.jar<br>commons-discovery.jar<br>commons-logging.jar<br>jaxrpc.jar<br>saaj.jar<br>wsdl4j.jar<br>xml-apis.jar<br>
<br>The CLASSPATH Environment Variable should have the absolute paths of the jars
(including the jar file name) given as a semicolon separated list.<br>
<br>
1.20 +10 -6 ws-site/targets/axis/cpp/windev-guide.html
Index: windev-guide.html
===================================================================
RCS file: /home/cvs/ws-site/targets/axis/cpp/windev-guide.html,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- windev-guide.html 22 Jul 2004 11:09:33 -0000 1.19
+++ windev-guide.html 28 Jul 2004 04:37:46 -0000 1.20
@@ -398,14 +398,14 @@
</p>
<p>1) Copy [EXPAT_EXTRACT]\source\lib\expat.h from expat binary distribution to
[CHECKOUT_HOME]\c\include\expat\ directory<br>
<br>2) Copy [EXPAT_EXTRACT]\lib\libexpat.lib to [CHECKOUT_HOME]\c\lib\expat\
directory.</p>
-<p>3) Copy libexpat.dll file from [EXPAT_EXTRACT]\Libs to %AXIS_HOME%/libs/<br>
+<p>3) Copy libexpat.dll file from [EXPAT_EXTRACT]\Libs to %AXISCPP_DEPLOY%/libs/<br>
<br>
</p>
<p>
<strong>For Xerces Parser</strong>
</p>
<p>1) Copy [XERCES_EXTRACT]\lib\xerces-c_2.lib to [CHECKOUT_HOME]\c\lib\xerces\
directory.</p>
-<p>2) Copy xerces-c_2_2_0.dll file from [XERCES_EXTRACT]\bin to
%AXIS_HOME%/libs/<br>
+<p>2) Copy xerces-c_2_2_0.dll file from [XERCES_EXTRACT]\bin to
%AXISCPP_DEPLOY%/libs/<br>
</p>
<p>
<strong>For apache 1.3.X:</strong>
@@ -457,10 +457,10 @@
<br>
<p>1) Create a directory structure called "Axis" inside [APACHE_HOME] as
follows.<br>(Instead, you can copy the folder [CHECKOUT_HOME]\c\deploy to
[APACHE_HOME] and rename it to "Axis" and you will find some of the files that you are
asked to create in this guide, already existing in that folder)<br>
<br>Axis<br>|__ libs (Copy [EXPAT_EXTRACT]\Libs\libexpat.dll or<br>
[XERCES_EXTRACT]\bin\xerces-c_2_2_0.dll and paste it inside)<br>|__ logs (log files
are located here)<br>|__ conf (server.wsdd file is located here)<br>|__ webservices
(The place to put webservice dlls)<br>|__ wsdls (wsdl files of the deployed web
services are located here)<br>
-<br>2) Set an environment variable named AXIS_HOME and give [APACHE_HOME]\Axis as
the value.<br>
+<br>2) Set an environment variable named AXISCPP_DEPLOY and give [APACHE_HOME]\Axis
as the value.<br>
<br>i)You will find AxisServer.dll and APACHE_MODULE in [CHECKOUT_HOME]\c\bin
directory.<br>ii)Copy APACHE_MODULE to [APACHE_HOME]\modules directory of your apache
installation.<br>
</p>
-<p>Copy AxisServer.dll ,AxisTransport.dll and AxisXMLParser.dll to
[AXIS_HOME]\libs\ directory and add that directory to your PATH environment
variable.Or to any location specified by your PATH environment variable.</p>
+<p>Copy AxisServer.dll ,AxisTransport.dll and AxisXMLParser.dll to
[AXISCPP_DEPLOY]\libs\ directory and add that directory to your PATH environment
variable.Or to any location specified by your PATH environment variable.</p>
<br>
<br>
<p>3) Set the "PATH" environment variable to the following
directories.<br>[APACHE_HOME]<br>[APACHE_HOME]\Axis\libs<br>
@@ -499,7 +499,10 @@
<br>Select java in the "New Project" dialog and click "Next".<br>
<br>In the "New" dialog that appears give a project Name (e.g. test). In the "New
dialog" keep the "use default" Tick Box checked.<br>Note down the path in the
"Directory" Text Box. This location will be referred to as [SKELSTUB_HOME] from this
point onwards. Click "Next".<br>
<br>Another dialog named "New” will appear. Select the “Source”
tab. Select the project that you created (i.e. test).<br>Click on “Add
Folder…”. In the “Source Folder Selection” dialog that
appears select the project that you created (i.e. test) and click “Create New
Folder…”. In the “New Folder” dialog that appears give a
folder name as “src” and click “OK”. Click “OK” in
the “Source Folder Selection” dialog. Click “Yes” on the
confirmation message box that pops up.<br>
-<br>Click “Libraries” in the “New” dialog. Click “Add
External JARs…”. In the “JAR Selection” dialog that appears
browse to [CHECKOUT_HOME]\ lib\axisjava and select the following JARs.<br>
+<br>Click “Libraries” in the “New” dialog. Click “Add
External JARs…”. In the “JAR Selection” dialog that appears
browse to the location where the latest jars are and select the following JARs.<br>
+<br>
+<strong>Note:</strong> The latest jars are in <a
href="http://apache.towardex.com/ws/axis/1_2beta/";>http://apache.towardex.com/ws/axis/1_2beta/</a>
+<br>
<br>axis.jar<br>commons-discovery.jar<br>commons-logging.jar<br>jaxrpc.jar<br>saaj.jar<br>wsdl4j.jar<br>xml-apis.jar<br>
<br>Click “Open”.<br>
<br>Click “Finish” on the “New” dialog.<br>
@@ -527,7 +530,8 @@
<h2>Building and running WSDL2Ws on the command line</h2>
</div>
<p>To build the WSDL2Ws java tool on the command line you require jdk1.4 or
above.<br>
-<br>To build WSDL2Ws java tool set the CLASSPATH Environment Variable to point to
the following jar files.Create a New Folder called wsdl2wsTool\lib and put the above
mentioned jars in it. You can find these jars in [CHECKOUT_HOME]\lib\axisjava.<br>
+<br>To build WSDL2Ws java tool set the CLASSPATH Environment Variable to point to
the following jar files.Create a New Folder called wsdl2wsTool\lib and put the above
mentioned jars in it. You can find the latest jars in <a
href="http://apache.towardex.com/ws/axis/1_2beta/";>http://apache.towardex.com/ws/axis/1_2beta/</a>
+<br>
<br>axis.jar<br>commons-discovery.jar<br>commons-logging.jar<br>jaxrpc.jar<br>saaj.jar<br>wsdl4j.jar<br>xml-apis.jar<br>
<br>Open a command window.<br>
<br>Change directory to [CHECKOUT_HOME]\c\src\wsdl.<br>We will refer to this
directory as [SKELSTUB_HOME] as we did during generating Skeletons/Wrappers and Stubs
with eclipse.<br>
1.16 +138 -119 ws-site/targets/axis/cpp/linuser-guide.pdf
<<Binary file>>
1.16 +19 -24 ws-site/targets/axis/cpp/linuser-guide.html
Index: linuser-guide.html
===================================================================
RCS file: /home/cvs/ws-site/targets/axis/cpp/linuser-guide.html,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- linuser-guide.html 21 Jul 2004 09:43:48 -0000 1.15
+++ linuser-guide.html 28 Jul 2004 04:37:47 -0000 1.16
@@ -391,17 +391,17 @@
<h3>Axis C++ now delivers the following key features</h3>
<p>- Speed: Axis uses SAX (event-based) parsing to acheive significantly greater
speed</p>
<p>- Flexibility</p>
-<p>- Stability , Component Oriented Deployment</p>
+<p>- Stability , Component oriented Deployment</p>
<p>- Transport Framework</p>
<p>- WSDL support</p>
-<p>Axis C++ 1.1 supports the Web Service Description Language, version 1.1, which
allows you to easily build stubs to access remote services, and also to automatically
export machine-readable descriptions of your deployed services from Axis. We hope you
enjoy using Axis c++ 1.1. Please note that this is an open-source effort - if you feel
the code could use some new features or fixes, please get involved and lend a hand!
The Axis developer community welcomes your participation. Let us know what you think!
Please send feedback about the package to <a href="mailto:[EMAIL PROTECTED]">[EMAIL
PROTECTED]</a>
+<p>AxisC++ 1.1 supports the Web Service Description Language, version 1.1, which
allows you to easily build stubs to access remote services, and also to automatically
export machine-readable descriptions of your deployed services from Axis. We hope you
enjoy using Axis c++ 1.1. Please note that this is an open-source effort - if you feel
the code could use some new features or fixes, please get involved and lend a hand!
The Axis developer community welcomes your participation. Let us know what you think!
Please send feedback about the package to <a href="mailto:[EMAIL PROTECTED]">[EMAIL
PROTECTED]</a>
</p>
<p>
<a name="What1"></a>
</p>
<h3>Installing Axis and Using this Guide</h3>
-<p>Look at the Axis Installation Guide for instructions to install Axis C++</p>
-<p>Before running the examples in this guide, you need to make sure that your
environment variables and other configurations are set correctly as described in
Installation guide. That is you need</p>
+<p>See the Axis Installation Guide for instructions on installing Axis C++</p>
+<p>Before running the examples in this guide, you'll need to make sure that your
environment variables and other configurations are set correctly as described in
Installation guide. That is you need</p>
<p>- Axis C++</p>
<p>- Apache1.3 (or Apache2.0)</p>
<p>- expat</p>
@@ -416,7 +416,7 @@
<p>
<strong>$AXISCPP_HOME/src/wsdl</strong>
</p>
-<p>You need the following jar files included in the <strong>CLASSPATH</strong> .</p>
+<p>You need the following latest jar files which are in <a
href="http://apache.towardex.com/ws/axis/1_2beta/";>http://apache.towardex.com/ws/axis/1_2beta/</a>
please include them in the <strong>CLASSPATH</strong> .</p>
<p>- axis.jar</p>
<p>- commons-discovery.jar</p>
<p>- commons-logging.jar</p>
@@ -443,7 +443,8 @@
<strong>PATH="$PATH:$JAVA_HOME/bin:."</strong>
</p>
<p>
-<strong>CLASSPATH="$CLASSPATH:./:$JAVA_HOME/lib:$AXIS_JARS:"</strong>(Refer the
Note given below)</p>
+<strong>CLASSPATH="$CLASSPATH:./:$JAVA_HOME/lib:$AXIS_JARS:"</strong>
+</p>
<p>
<strong>export PATH USER LOGNAME MAIL HOSTNAME HISTSIZE INPUTRC
AXIS_JARS_HOME</strong>
</p>
@@ -469,8 +470,7 @@
<p>
<strong>$cp -f wsdl2ws.jar $AXISCPP_HOME/lib/axis</strong>
</p>
-<p>
-<strong>Note:</strong>Add this jar as the first entry into the classpath as
well.(In the binary distribution you don't need to create this jar. It is already in
$AXISCPP_HOME/lib/axis)</p>
+<p>add this jar as the first entry into the classpath as well.(In the binary
distribution you don't need to create this jar. It is already in
$AXISCPP_HOME/lib/axis)</p>
<p>
<a name="Server"></a>
</p>
@@ -485,7 +485,7 @@
</strong>
</p>
<p>We use this sample to demonstrate the generation of serverside skeletons and how
to deploy a web service using it.</p>
-<p>Inside this folder you will find Calculator.wsdl file using which, we generate
skeleton and Wrappers. Here is the command line arguments to generate the skeleton.</p>
+<p>Inside this folder you will find Calculator.wsdl file using which we generate
skeleton and Wrappers. Here is the command line arguments to generate the skeleton.</p>
<p>
<strong>*important:In this sample we generate the skeltons using Calculator.wsdl
and wsdl2ws tool. But in the folder you will find already generated files. If you wish
to use those without generating new ones you can do so. We recommend that you deploy
the sample with the already generated files in the first round and<br> later do the
same with code generated from Calcuator.wsdl.<br>
</strong>
@@ -497,8 +497,7 @@
<p>
<strong>% java org.apache.axis.wsdl.wsdl2ws.WSDL2Ws Calculator.wsdl -lc++
-sserver</strong>
</p>
-<p>
-<strong>Note:</strong> If you give <strong>-o. /GenClassesServer</strong> then the
server creates a folder named GenClassServer and put the source there. Otherwise the
source is put in the current folder where the tool is run.</p>
+<p>Note: If you give <strong>-o. /GenClassesServer</strong> then the server create
a folder named GenClassServer and put the source there. Otherwise the source is put in
the current folder where the tool is run.</p>
<p>
<a name="Deploying"></a>
</p>
@@ -571,7 +570,7 @@
</p>
<p>
<strong>
-<br>Note:</strong> again if you specify <strong>-o./GenClassesClient</strong> you
will have source generated inside GenClassClient folder instead of current folder
where the tool is run. Before compiling the client you have to write a class which
contains a main method in which Calculator instance is created and its methods are
called.</p>
+<br>Note:</strong> again if you specify <strong>-o./GenClassesClient</strong> you
will have source generated inside GenClassClient folder instead of current folder
where the tool is run. Before compiling the client you have to write a class which
contain a main method in which Calculator instance is created and its methods are
called.</p>
<p>Then fill the samples with the relevant business logics .</p>
<p>Then fill the main method in a file as follows</p>
<p>
@@ -698,8 +697,7 @@
</p>
<h3>Handlers</h3>
<p>Handlers are pluggable components to Axis C++. We have included a set of sample
handlers for your reference. You could write your own handlers by following the
instructions which are given for the sample Handlers.</p>
-<p>
-<strong>Note:</strong> If you are using Client side Handlers you need to enter the
following entry in the AXIS_HOME/axiscpp.conf configuration file.</p>
+<p>Note: If you are using Client side Handlers you need to enter the following
entry in the AXIS_HOME/axiscpp.conf configuration file.</p>
<p>CLIENTWSDDFILEPATH:Axis\conf\client.wsdd</p>
<p>After entering this entry your AXIS_HOME/axiscpp.conf configuration file will
look like:</p>
<p> AXISLOGPATH:Axis\logs\AxisLog.txt</p>
@@ -727,7 +725,7 @@
<p>
<strong><strong>Building echoStringHeaderHandler (A server side handler
sample)</strong></strong>
</p>
-<p>The build files are available at
AXISCPP_HOME/samples/server/echoStringHeaderHandler. Change your current directory to
this directory and then you could execute the following.</p>
+<p>The build files are available at
AXISCPP_HOME/samples/server/echoStringHeaderHandler. Change your current directory to
this direcotory and then you could execute the following.</p>
<p> sh autogen.sh</p>
<p> sh runconfig</p>
<p> make</p>
@@ -751,10 +749,9 @@
<p><parameter name="className" value="Axis\webservices\Calculator.dll" /></p>
<p></service></p>
<br>
-<p>
-<strong>Note:</strong> Make sure you specify the correct path of the handler so in
the server.wsdd file. Replace the AXIS_HOME with the exact relative path which
AXIS_HOME points to. (eg:
type="/usr/local/apache2/Axis/handlers/custom/echoStringHeaderHandler/libeshhandler.so
)</p>
+<p>Note: Make sure you specify the correct path of the handler so in the
server.wsdd file. Replace the AXIS_HOME with the exact relative path which AXIS_HOME
points to. (eg:
type="/usr/local/apache2/Axis/handlers/custom/echoStringHeaderHandler/libeshhandler.so
)</p>
<p>Now you are almost done to run your server side handler.</p>
-<p>Restart the Apache server and thats it.</p>
+<p>Restart the Apache server and that is it.</p>
<p>
<strong><strong>Running the Handler</strong></strong>
</p>
@@ -788,11 +785,9 @@
<p></requestFlow></p>
<p></service></p>
<br>
-<p>
-<strong>Note:</strong> Make sure you specify the correct path of the handler so in
the client.wsdd file. Replace the AXIS_HOME with the exact relative path which
AXIS_HOME points to. (eg:
type="/usr/local/apache2/Axis/handlers/client/test_handler/libtest_client_handler.so)</p>
+<p>Note: Make sure you specify the correct path of the handler so in the
client.wsdd file. Replace the AXIS_HOME with the exact relative path which AXIS_HOME
points to. (eg:
type="/usr/local/apache2/Axis/handlers/client/test_handler/libtest_client_handler.so)</p>
<p>Now you are almost done to run your client side handler.</p>
-<p>
-<strong>Note:</strong> If you are using Client side Handlers you need to enter the
CLIENTWSDDFILEPATH entry in the AXIS_HOME/axiscpp.conf configuration file. (See
above)</p>
+<p>Note: If you are using Client side Handlers you need to enter the
CLIENTWSDDFILEPATH entry in the AXIS_HOME/axiscpp.conf configuration file. (See
above)</p>
<p>
<strong><strong>Running the Handler</strong></strong>
</p>
@@ -825,8 +820,8 @@
<strong><strong><strong>cvs -d :pserver:[EMAIL PROTECTED]:/home/cvspublic checkout
-d <your local folder> ws-axis/c"</strong></strong></strong>
</p>
<br>
-<br>
-<a href="linuser-guide.pdf"><img alt="PDF" src="../skin/images/pdfdoc.gif"><br>
PDF</a>
+<br>
+<a href="linuser-guide.pdf"><img alt="PDF" src="../skin/images/pdfdoc.gif"><br>
PDF</a>
<div id="pdf" align="right">
<a href="linuser-guide.pdf"><img alt="PDF" src="../skin/images/pdfdoc.gif"
class="skin"><br>
PDF</a>
