Date: 2004-12-17T04:17:32
Editor: DeepalJayasinghe <[EMAIL PROTECTED]>
Wiki: Apache Web Services Wiki
Page: FrontPage/Architecture/Client
URL: http://wiki.apache.org/ws/FrontPage/Architecture/Client
no comment
Change Log:
------------------------------------------------------------------------------
@@ -50,10 +50,10 @@
== Possible Message Paths ==
-=== One-Way Invocation ===
+=== sendAsync Invocation ===
The service invocation is a void invocation. No return value.
{{{
-a -> call.invokeInOnly(SOAPEnvelope)
+a -> call.sendAsync(SOAPEnvelope)
b -> engine.send( ..)
c -> Send the SOAP message
}}}
@@ -64,14 +64,31 @@
{{{
call.setTargetURL(URL)
call.setAction(String)
-call.invokeInOnly(SOAPEnvelope)
+call.sendAsync(SOAPEnvelope)
}}}
+=== send Invocation ===
+The service invocation is a void invocation. No return value.
+{{{
+a -> call.send(SOAPEnvelope)
+b -> engine.send( ..)
+c -> Send the SOAP message
+}}}
+//Asume that the transport is one way e.g. SMTP
+
+
+Code Snippet:
+{{{
+call.setTargetURL(URL)
+call.setAction(String)
+call.send(SOAPEnvelope)
+}}}
+
-=== InOutSynchronous Invocation ===
+=== sendReceive Invocation ===
The service method has a response and the communication happens synchronously
using a bi-directional protocol. Client hangs until the response (or fault) is
returned.
{{{
-a -> call.invokeInOutSync(SOAPEnvelope)
+a -> call.sendReceive(SOAPEnvelope)
b- > engine.send (..)
c -> Send the SOAP message
d -> Receive the response over the synchronous transport
@@ -85,15 +102,15 @@
{{{
call.setTargetURL(URL)
call.setAction(String)
-SOAPEnvelope env=call.invokeInOutSync(SOAPEnvelope)
+SOAPEnvelope env=call.sendReceive(SOAPEnvelope)
}}}
-=== InOutAynchronous Invocation ===
+=== sendReceiveAsync Invocation ===
The service method has a response and the communication happens synchronously
using a bi-directional protocol. Client DOES NOT hang until the response (or
fault) is returned. Client uses callback mechanism to retrieve the response.
Call API uses threads from a thread pool for each invocation.
{{{
-a -> call.invokeInOutAsync(SOAPEnvelope, callbackObj)
+a -> call.sendReceiveAsync (SOAPEnvelope, callbackObj)
p -> correlator.addCorrelationInfor(msgID,allbackObjRef)
b- > engine.send (..)
c -> Send the SOAP message
@@ -107,13 +124,13 @@
{{{
call.setTargetURL(URL)
call.setAction(String)
-call.invokeInOutAsync(SOAPEnvelope, Callback)
+call.sendReceiveAsync (SOAPEnvelope, Callback)
}}}
-=== InOutAynchronous Invocation with One way transport ===
+=== sendReceiveAsync Invocation with One way transport ===
The service method has a response and the communication happens Aynchronously
using a uni-directional protocol. Client DOES NOT hang until the response (or
fault) is returned. Client uses callback mechanism to retrieve the response.
Call API uses threads from a thread pool for each invocation.
{{{
-a -> call.invokeInOutAsync(SOAPEnvelope, callbackObj)
+a -> call.sendReceiveAsync (SOAPEnvelope, callbackObj)
p -> correlator.addCorrelationInfor(msgID,allbackObjRef)
b- > engine.send (..)
c -> Send the SOAP message
@@ -129,7 +146,7 @@
call.setTargetURL(URL)
call.setAction(String)
call.setListenerTransport(�http�)
-call.invokeInOutAsync(SOAPEnvelope, Callback)
+call.sendReceiveAsync(SOAPEnvelope, Callback)
}}}
