Hi Dalys, Please see my comments inline.
Regards, Ali Sadik Kumlali > ----- Original Message ---- > From: Dalys Sebastian <[EMAIL PROTECTED]> > To: [email protected] > Sent: Wednesday, November 22, 2006 12:47:58 AM > Subject: Re: Using asynchronous messaging > > Hi Ali, > > Thanks for the links. I had read through these links, and I still am not able > to get the > complete picture of the service-side processing. > > For e.g.,suppose my service class will look like this: > public class A > { > public void asyncservice(String data) > { > //determine the replyTo address > //queue data in the server for further processing > } > } > > 1) And when I get back response after processing at the server, how will I > communicate > this to the client? > > 2) What must the client set in the replyTo address? It doesnot have any > webservice > running. It's a simple .Net client. Don't know about .Net. In the case of Axis2 client, it will create a separate listener at replyTo address for the callback from the service side. When your service side completes the process, it will return the result back to the replyTo address of the incoming message. These are all automatically handled by Axis2, if you provide suitable WSDL and generate the skeleton(for the service side) and the stub(for the client side) from it. > > Any answers for this will be very helpful. I apologize if I have overlooked > something. > > Thanks, > Dalys --- Ali Sadik Kumlali <[EMAIL PROTECTED]> wrote: > Hi Dalys, > > If you mean axis2, you might start from: > - "Do a Non-Blocking Invocation" title in user guide[1] > - "Request-Response, Non-Blocking that uses two transport connections" title > in this[2] > page. > - Similar e-mails in axis-user list[3] > > Regards, > > Ali Sadik Kumlali > > [1] http://ws.apache.org/axis2/1_1/userguide.html > [2] http://ws.apache.org/axis2/1_1/dii.html > [3] > http://www.mail-archive.com/search?q=axis2%20asynchronous&[EMAIL PROTECTED]&start=10 > > ----- Original Message ---- > From: Dalys Sebastian <[EMAIL PROTECTED]> > To: [email protected] > Sent: Tuesday, November 21, 2006 11:14:09 PM > Subject: Using asynchronous messaging > > Hello, > > I am trying to figure out how to configure the service side for solving the > following > problem: > > The server gets a request from a client which cannot be immediately > processed. It has > to > go to an external program to fetch information which may take a delay. Only > after a > response is obtained from the external program, can a response be sent back > to the > client. > > How do I implement the service-side logic to solve this issue? Till now I > have been > using > the RPCMessageReceiver and performing only synchronous calls. > > 1) What's the MessageReceiver that needs to be used in these situations? > 2) What must the client set in their reply-To address field? Should the > client be > running > a separate webservice to get back responses? > 3) And when I need to return back the response to the client, how does the > server > invoke > it? is it as a webservice call with the To address same as the received > replyTo field? > 4) How must the client-side code be to get back the response? Using > sendReceiveNonBlocking? > If there is an example somewhere which can demonstrate these configurations, > it would > help a lot. > > Thank you, > Dalys > > > > ____________________________________________________________________________________ > Sponsored Link > > Mortgage rates near 39yr lows. $510k for $1,698/mo. > Calculate new payment! www.LowerMyBills.com/lre > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > ____________________________________________________________________________________ Sponsored Link $200,000 mortgage for $660/ mo 30/15 yr fixed, reduce debt http://yahoo.ratemarketplace.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
