svn commit: r406854 - in /webservices/axis2/trunk/c/xdocs/docs: userguide.html userguide1.html userguide2.html userguide3.html

[sa...@apache.org]

Author: samisa
Date: Mon May 15 23:26:33 2006
New Revision: 406854

URL: http://svn.apache.org/viewcvs?rev=406854&view=rev
Log:
Removed old files and fixed a typo in user guide

Removed:
    webservices/axis2/trunk/c/xdocs/docs/userguide1.html
    webservices/axis2/trunk/c/xdocs/docs/userguide2.html
    webservices/axis2/trunk/c/xdocs/docs/userguide3.html
Modified:
    webservices/axis2/trunk/c/xdocs/docs/userguide.html

Modified: webservices/axis2/trunk/c/xdocs/docs/userguide.html
URL: http://svn.apache.org/viewcvs/webservices/axis2/trunk/c/xdocs/docs/userguide.html?rev=406854&r1=406853&r2=406854&view=diff
==============================================================================
--- webservices/axis2/trunk/c/xdocs/docs/userguide.html (original)
+++ webservices/axis2/trunk/c/xdocs/docs/userguide.html Mon May 15 23:26:33 2006
@@ -791,7 +791,7 @@
 we use a Blocking API in the client code. Sample code for this can be found
 in the "Axis2CHome/samples/user_guide/clients/" directory and the explanation
 is similar to the <a
-href="#EchoNonBlockingDualClient">EchoNonBlockingDualClient</a>, except that
+href="#EchoNonBlockingDualClient">echo_non_blocking_dual client</a>, except that
 here we do not use a callback object to handle response. This is a very
 useful mechanism when the service invocation is IN-OUT in nature and the
 transports are One-Way (e.g. SMTP). For the sample client we use two HTTP