You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fx-dev@ws.apache.org by ch...@apache.org on 2005/05/26 11:58:30 UTC
cvs commit: ws-fx/sandesha/xdocs interopguide.html navigation.xml
chamikara 2005/05/26 02:58:29
Modified: sandesha/xdocs interopguide.html navigation.xml
Log:
Some changes to the interop guide
Revision Changes Path
1.2 +24 -28 ws-fx/sandesha/xdocs/interopguide.html
Index: interopguide.html
===================================================================
RCS file: /home/cvs/ws-fx/sandesha/xdocs/interopguide.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- interopguide.html 24 May 2005 18:08:14 -0000 1.1
+++ interopguide.html 26 May 2005 09:58:29 -0000 1.2
@@ -12,44 +12,44 @@
<body>
<h1><font size="6">Interop guide for Apache Sandesha</font></h1>
<p>This document explains the interoperability of apache Sandesha with
-several other well known WS-RM implementations. We will not only show you
-how nicely Sandesha interoperates with them but also how you can test the
-interoperability yourself.</p>
+several other well known WS-RM implementations. You can test the interoperability
+yourself using the stub classes and the test client web application we
+have provided.</p>
-<h2><font size="5">Sandesha client</font></h2>
-<p>Sandesha client has successfully interoperated with the WS-RM server
+<p>Sandesha client has successfully interoperated with the WS-RM
implementations given below. We have developed client classes for each of
-these server endpoints. Please make sure that the server endpoints are
+these endpoints. Please make sure that the server endpoints are
available before you try to run the client classes. Also make sure that
-your computer has a public IP address available before testing. This will
-be necessary for getting responses from the server.
+your computer can get information back asynchronously. (you may have to make
+sure that a firewall is not blocking the response path (default port 9090) and
+you may need to have a public IP address).
</p>
-<h3><font size="4">With IBM server</font></h3>
+<h3><font size="4">With IBM implementation</font></h3>
<p>Server endpoint is <a href="http://wsi.alphaworks.ibm.com:8080/wsrm/services/rmDemos">http://wsi.alphaworks.ibm.com:8080/wsrm/services/rmDemos</a></p>
-<p>With IBM we have successfully interoperated both Ping and EchoString clients.
+<p>With IBM we have successfully interoperated both Ping and EchoString scenarios.
Classes IBMEcho, IBMAsyncPing and IBMSyncPing can be used to test the interoperability
with this endpoint. These are available in the package org.apache.sandesha.samples.interop
-of the 'test' folder.
+of the 'interop' folder.
</p>
-<h3><font size="4">With Microsoft server</font></h3>
+<h3><font size="4">With Microsoft implementation</font></h3>
<p>Server endpoint is <a href="http://131.107.153.195/SecureReliableMessaging/ReliableOneWayDual.svc">http://131.107.153.195/SecureReliableMessaging/ReliableOneWayDual.svc</a></p>
-<p>Sandesha nicely works with above Ping service available from Microsoft.
+<p>Sandesha interoperated with the above Ping service ednpoints available from Microsoft.
Classes MicrosoftAsyncPing and MicrosoftSyncPing can be used to test the interoperability
with this endpoint. These are available in the package org.apache.sandesha.samples.interop
-of the 'test' folder.
+of the 'interop' folder.
</p>
<h3><font size="4">With Systinet server</font></h3>
<p>Server endpoint is <a href="http://soap.systinet.net:6064/Service">http://soap.systinet.net:6064/Service</a></p>
-<p>Sandesha has proved its interoperability with the Systinet server as well.
+<p>Sandesha has also proved to be interoperable with the Systinet server.
The client stub classes are SystinetSyncPing and SystinetAsyncPing, available
-in the package org.apache.sandesha.samples.interop of the 'test' folder.
+in the package org.apache.sandesha.samples.interop of the 'interop' folder.
</p>
<h3><font size="4">Using the test client webapp</font></h3>
<p>We have created a simple web application which you can deploy on tomcat and
test the interoperability with any available WS-RM server implementation.To build the webapp,
</p>
-<p>Make sure that you have Apache Ant installed in your system. After this go command
-prompt move to the the folder 'interop' and type,</p>
+<p>Make sure that you have Apache Ant installed in your system. After this go to the the
+folder 'interop' in command prompt and type,</p>
<p>
<source>ant war</source>
</p>
@@ -62,16 +62,12 @@
<p>
Most of the fields in this web page are self-explanaitory. First you can set the
target field to any valid target URL. After this choose the operation Ping or echoString accordingly.
-The AcksTo field tells weather the acknowledgements are synchronous or asynchronous.
-If acksTo is anonymous the acknowledgements will be sent in a synchronous path. You can also
-set the WS-Addressing fields From, To and ReplyTo. ReplyTo should say where you expect to
-receive applications responses. FaultTo URL should point to the location you expect to receive faults.
-Finally you can mention weather the client should send a sequence offer which is the sequence
-id of the response path, and the number of appplication messages you wish to send to the server.
-</p>
-<h2><font size="5">Sandesha Server</font></h2>
-<p>We have successfully tested the interoperability of Sandesha server with
-the IBM test client available at <a href="http://ibm_test_client_url">http://ibm_test_client_url</a>
+The AcksTo field represents the wsrm:acksTo value. If acksTo is anonymous the
+acknowledgements will be sent in a synchronous path. You can also set the
+fields From, To and ReplyTo which represent wsa:from, wsa:to and wsa:replyTo respectively. ReplyTo should say where you expect to receive applications responses.
+FaultTo URL should point to the location you expect to receive faults.
+Finally you can mention weather the client should send a sequence offer which
+is the sequence id of the response path, and the number of application messages you wish to send to the server.
</p>
</body>
1.4 +1 -1 ws-fx/sandesha/xdocs/navigation.xml
Index: navigation.xml
===================================================================
RCS file: /home/cvs/ws-fx/sandesha/xdocs/navigation.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- navigation.xml 15 Mar 2005 05:14:45 -0000 1.3
+++ navigation.xml 26 May 2005 09:58:29 -0000 1.4
@@ -6,7 +6,7 @@
<menu name="Sandesha">
<item name="Simple User Guide" href="userguide.html"/>
<item name="Architecture Guide" href="architecture.html"/>
-
+ <item name="Interop Guide" href="interopguide.html"/>
</menu>