You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by ch...@apache.org on 2005/06/28 05:53:28 UTC

svn commit: r202122 - /webservices/axis/trunk/java/xdocs/rest-ws.html

Author: chathura
Date: Mon Jun 27 20:53:25 2005
New Revision: 202122

URL: http://svn.apache.org/viewcvs?rev=202122&view=rev
Log:
Litrature changes

Modified:
    webservices/axis/trunk/java/xdocs/rest-ws.html

Modified: webservices/axis/trunk/java/xdocs/rest-ws.html
URL: http://svn.apache.org/viewcvs/webservices/axis/trunk/java/xdocs/rest-ws.html?rev=202122&r1=202121&r2=202122&view=diff
==============================================================================
--- webservices/axis/trunk/java/xdocs/rest-ws.html (original)
+++ webservices/axis/trunk/java/xdocs/rest-ws.html Mon Jun 27 20:53:25 2005
@@ -7,21 +7,23 @@
 <p>Axis2 can be configured as REST Cantainer and can be used to send and receives restful web services. The REST Web Services can be access in two ways, using HTTP GET and POST. </p>
  
  <h2>Doing REST web services with HTTP POST</h2> 
-  <p>REST support can be enabled in the Server side by adding the following line to the server.xml file.</p>
+  <p>REST support can be enabled in the Server side by adding the following line to the axis.xml file.</p>
   <code>
     &lt;parameter name="eanbleREST" locked="xsd:false"&gt;true&lt;/parameter&gt;
     </code>
   <p>But it act both as a REST endpoint as well as a SOAP endpoint. When a Message is received if the content type is text/xml and the SOAP Action Headers is missing the Message is considered as a RESTful Message. Else they are treated as usual SOAP Messages.</p>
   
-    <p>While sending the Messages decision they should be RESTful or not is up to the Client side developer. There are two ways to enable REST at the client side, first is to do the same thing done at the 
-  Server side in the client.xml file or do the following in the Call.</p>
-    
+    <p>On sending a message out, the fact that the message is RESTful or not, can be decided from the client API or by deployment descriptor of the client.</p>
+<ol>
+   <li> By adding an entry in the client.xml file similar to that of the axis.xml.</li>
+<li>Through client API e.g. call.set(Constants.Configuration.DO_REST,"true")</li>
+</ol>
     
     
 <code>call.set(Constants.Configuration.DO_REST,"true");</code>
   
-  <h2>Accsess a REST Web Service Via HTTP GET</h2>
-   <p>Axis2 let the users accsess Web Service that has simple type parameters via the HTTP GET. For example following URL requests the version service Via HTTP GET. But the Web Services arrived via GET assumes REST . Other parameter are converted in to the XML and put them in to the SOAP Body.</p>
+  <h2>Access a REST Web Service Via HTTP GET</h2>
+   <p>Axis2 let the users access Web Service that has simple type parameters via the HTTP GET. For example following URL requests the version service Via HTTP GET. But the Web Services arrived via GET assumes REST . Other parameter are converted in to the XML and put them in to the SOAP Body.</p>
    <code>http://127.0.0.1:8080/axis2/services/Version/getVersion?operation=getVersion</code>
    <p>Result can be shown in the browser as follows</p>
    <img src="images/userguide/http-get-ws.png"/>