You are viewing a plain text version of this content. The canonical link for it is here.
Posted to axis-cvs@ws.apache.org by ha...@apache.org on 2005/02/09 14:24:55 UTC
cvs commit: ws-axis/c/docs linuser-guide.html LibWWW-transport-HOWTO.txt
hawkeye 2005/02/09 05:24:55
Modified: c/tests/transportAbsTest Readme_Linux.txt
c/tests/client/exceptionTest README
c/tests/parserAbsTest Readme_Linux.txt
c/src/common AxisConfig.h AxisTrace.h
c/docs linuser-guide.html LibWWW-transport-HOWTO.txt
Log:
Removed and replaced occurences of AXIS_HOME with AXISCPP_DEPLOY. I'm relying on the 1.5 release build to generate the web site again.
Revision Changes Path
1.2 +4 -4 ws-axis/c/tests/transportAbsTest/Readme_Linux.txt
Index: Readme_Linux.txt
===================================================================
RCS file: /home/cvs/ws-axis/c/tests/transportAbsTest/Readme_Linux.txt,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- Readme_Linux.txt 24 Jun 2004 06:17:33 -0000 1.1
+++ Readme_Linux.txt 9 Feb 2005 13:24:52 -0000 1.2
@@ -7,7 +7,7 @@
Case 2: Test with transport not in place as specified by axiscpp.conf
- Transport entry is in $AXIS_HOME/axiscpp.conf as given below
+ Transport entry is in $AXISCPP_DEPLOY/axiscpp.conf as given below
Transport_http:/usr/local/Axis/libs/libaxis_transport.so
@@ -15,7 +15,7 @@
$ mkdir temp
- Move $AXIS_HOME/libs/libaxis_transport.so file to the temp directory
+ Move $AXISCPP_DEPLOY/libs/libaxis_transport.so file to the temp directory
$ mv $AXISCPP_HOME/libs/libaxis_transport.so [Place of choice]/temp/
@@ -24,11 +24,11 @@
Case 3: Test with no transport specified in axiscpp.conf
Move [Place of choice]/temp/libaxis_transport.so file back
- to original location on $AXIS_HOME/libs/
+ to original location on $AXISCPP_DEPLOY/libs/
$ mv [Place of choice]/temp/libaxis_transport.so $AXISCPP_HOME/libs/
- Comment "Transport_http" in $AXIS_HOME/axiscpp.conf as follows:
+ Comment "Transport_http" in $AXISCPP_DEPLOY/axiscpp.conf as follows:
#Transport_http:/usr/local/Axis/libs/libaxis_transport.so
1.2 +3 -3 ws-axis/c/tests/client/exceptionTest/README
Index: README
===================================================================
RCS file: /home/cvs/ws-axis/c/tests/client/exceptionTest/README,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- README 28 Jun 2004 07:29:34 -0000 1.1
+++ README 9 Feb 2005 13:24:52 -0000 1.2
@@ -84,7 +84,7 @@
test3
You may runt the test by removing the target service library
- $AXIS_HOME/webservices/libmathops.so and restarting apache
+ $AXISCPP_DEPLOY/webservices/libmathops.so and restarting apache
Message returned
@@ -102,7 +102,7 @@
test5
To run the application correctly you should have libaxis_xmlparser.so(parser
- library) in $AXIS_HOME/libs folder with the exact name given. You can run the
+ library) in $AXISCPP_DEPLOY/libs folder with the exact name given. You can run the
test with the name changed.
Message returned
@@ -111,7 +111,7 @@
test6
To run the application correctly you should have libaxis_transport.so(transport
- library) in $AXIS_HOME/libs folder with the exact name given. You can run the
+ library) in $AXISCPP_DEPLOY/libs folder with the exact name given. You can run the
test with the name changed.
Message returned
1.2 +6 -6 ws-axis/c/tests/parserAbsTest/Readme_Linux.txt
Index: Readme_Linux.txt
===================================================================
RCS file: /home/cvs/ws-axis/c/tests/parserAbsTest/Readme_Linux.txt,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- Readme_Linux.txt 24 Jun 2004 05:53:17 -0000 1.1
+++ Readme_Linux.txt 9 Feb 2005 13:24:52 -0000 1.2
@@ -4,9 +4,9 @@
case 1:Test all samples/tests with each parser
-case 2:Test with parser not in place as specified by $AXIS_HOME/axiscpp.conf
+case 2:Test with parser not in place as specified by $AXISCPP_DEPLOY/axiscpp.conf
- Parser entry is in $AXIS_HOME/axiscpp.conf as given below
+ Parser entry is in $AXISCPP_DEPLOY/axiscpp.conf as given below
XMLParser:/usr/local/Axis/libs/libaxis_xmlparser.so
@@ -14,20 +14,20 @@
$ mkdir temp
- Move $AXIS_HOME/libs/libaxis_xmlparser.so file to the temp directory
+ Move $AXISCPP_DEPLOY/libs/libaxis_xmlparser.so file to the temp directory
$ mv $AXISCPP_HOME/libs/libaxis_xmlparser.so [Place of choice]/temp/
Run the samples and test.
-case 3:Test with no parser specified in $AXIS_HOME/axiscpp.conf
+case 3:Test with no parser specified in $AXISCPP_DEPLOY/axiscpp.conf
Move [Place of choice]/temp/libaxis_xmlparser.so file back
- to original location on $AXIS_HOME/libs/
+ to original location on $AXISCPP_DEPLOY/libs/
$ mv [Place of choice]/temp/libaxis_xmlparser.so $AXISCPP_HOME/libs/
- Comment XMLParser in $AXIS_HOME/axiscpp.conf as follows:
+ Comment XMLParser in $AXISCPP_DEPLOY/axiscpp.conf as follows:
#XMLParser:/usr/local/Axis/libs/libaxis_xmlparser.so
1.20 +3 -3 ws-axis/c/src/common/AxisConfig.h
Index: AxisConfig.h
===================================================================
RCS file: /home/cvs/ws-axis/c/src/common/AxisConfig.h,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- AxisConfig.h 11 Jan 2005 13:24:26 -0000 1.19
+++ AxisConfig.h 9 Feb 2005 13:24:52 -0000 1.20
@@ -34,7 +34,7 @@
*
* The purpose of this class is to provide a way so that
* the server takes the configuration path where the
- * axiscpp.conf lies from the environment variable AXIS_HOME.
+ * axiscpp.conf lies from the environment variable AXISCPP_DEPLOY.
* User has to set this variable pointing the path to axiscpp.conf file.
* This axiscpp.conf file contains all the configuration paths
* like wsdd configuration file path, axis log path etc.
@@ -69,7 +69,7 @@
/**
* This method will read from the configuration file called axiscpp.conf
- * which is located in a place defined by AXIS_HOME environment variable.
+ * which is located in a place defined by AXISCPP_DEPLOY environment variable.
*
* @return The status which indicates whether the operation is success
* (AXIS_SUCCESS) or not (AXIS_FAIL).
@@ -80,7 +80,7 @@
* This is called to get the value of a property as defined by the g_axconfig
* enumeration.
*
- * @return the $AXIS_HOME value
+ * @return the requested value or NULL if the property is not set.
*/
char* getAxisConfProperty(g_axconfig property);
1.29 +2 -2 ws-axis/c/src/common/AxisTrace.h
Index: AxisTrace.h
===================================================================
RCS file: /home/cvs/ws-axis/c/src/common/AxisTrace.h,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -r1.28 -r1.29
--- AxisTrace.h 3 Feb 2005 09:55:59 -0000 1.28
+++ AxisTrace.h 9 Feb 2005 13:24:52 -0000 1.29
@@ -116,7 +116,7 @@
/**
* This is called in writing to the log file whose path is specified in
- * $AXIS_HOME/axiscpp.c * onf file.
+ * $AXISCPP_DEPLOY/axiscpp.conf file.
* This method is used when the caller has two string messages
* as arguments. One may be his *own message.
* The other may be to print a trace value. User can also specify the
@@ -147,7 +147,7 @@
* Log file is opened for logging server side log messages
*
* The file is created( if one is already not there) with the name and
- * path specified in $AXIS_HOME/axiscpp.conf file when web server loads.
+ * path specified in AXISCPP_DEPLOY/axiscpp.conf file when web server loads.
*
* @return The status which indicates whether the operation is successful
* (AXIS_SUCCESS) or not (AXIS_FAIL).
1.7 +3 -3 ws-axis/c/docs/linuser-guide.html
Index: linuser-guide.html
===================================================================
RCS file: /home/cvs/ws-axis/c/docs/linuser-guide.html,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- linuser-guide.html 3 Feb 2005 06:42:33 -0000 1.6
+++ linuser-guide.html 9 Feb 2005 13:24:52 -0000 1.7
@@ -273,7 +273,7 @@
<p> Copy this service library into $AXICPP_DEPLOY/lib </p>
-<p>Modify the <strong>$AXIS_HOME/conf/</strong><strong>server.wsdd</strong> . (You have a sample server.wsdd file entry given below appropriately filled for this service).</p>
+<p>Modify the <strong>$AXISCPP_DEPLOY/conf/</strong><strong>server.wsdd</strong> . (You have a sample server.wsdd file entry given below appropriately filled for this service).</p>
<p>
<strong><?xml version="1.0" encoding="UTF-8"?></strong>
<br>
@@ -418,9 +418,9 @@
<h3>Handlers</h3>
</div>
<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>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>Note: If you are using Client side Handlers you need to enter the following entry in the AXISCPP_DEPLOY/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>After entering this entry your AXISCPP_DEPLOY/axiscpp.conf configuration file will look like:</p>
<p> AXISLOGPATH:Axis\logs\AxisLog.txt</p>
<p> WSDDFILEPATH:Axis\conf\server.wsdd</p>
<p> CLIENTWSDDFILEPATH:Axis\conf\client.wsdd</p>
1.3 +2 -2 ws-axis/c/docs/LibWWW-transport-HOWTO.txt
Index: LibWWW-transport-HOWTO.txt
===================================================================
RCS file: /home/cvs/ws-axis/c/docs/LibWWW-transport-HOWTO.txt,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- LibWWW-transport-HOWTO.txt 6 Sep 2004 06:48:54 -0000 1.2
+++ LibWWW-transport-HOWTO.txt 9 Feb 2005 13:24:52 -0000 1.3
@@ -88,7 +88,7 @@
3. Using the LibWWW transport
Once you build the library, you could use it by specifying the location of the
-lib in $AXIS_HOME/axiscpp.conf file.
+lib in $AXISCPP_DEPLOY/axiscpp.conf file.
e.g.
Transport_http:/usr/local/Axis/libs/libaxis_LibWWWTransport.so
@@ -97,7 +97,7 @@
Thread Safety:
http://www.w3.org/Library/User/Architecture/Events.html says
“LibWWW is not posix thread safe but it uses a 'pseudo-thread'
-model based on non-blocking sockets and interleaved IO.”
+model based on non-blocking sockets and interleaved IO.�?
I did a bit of research and figured out how to make LibWWW thread safe.
However I was unable to successfully use the 'pseudo-thread'
model of LibWWW and achieve thread safety with Axis C++. I think the problem