I just created a test case to demonstrate how Axis2 server side async work if you can have a look at that.
org.apache.axis2.async.AsyncServiceTest SOA Work wrote: >I'm a little sorry for spending such much confusion to this list ;-) > >Thx for your answer. > >There is no techincal architecure question. I'm not using axis client on the >process side. My BPEL engine is going to handle this. > >It is all about the service, which should be called. > >After reading some more forums the problem is less axis side more an bpel >issue. >But I'm using axis for covering an async service used by an bpel process, so >the question is not wrong in this list. I thought maybe some users got some >experience on working with bpel and axis. > >I would say close the thread and forget about it. > >If somebody is still intrested in the topic, don't bother mailing me. (The >time you read this email, I'll implemented the scenario). > >thx >Dominik > >p.s.: for intresteds: it seems bpel adds some information about the callback >port to the soap header (as it is specified in ws-addressing). So a solution >would be to store the callback information during the async invocation of the >service and use it later with dynamic client side invocation (client side >invocation on server side *smile*) . > > > >[email protected] schrieb am 08.03.06 15:41:43: > > >>Ok lemme try one more time. >> >>Your process -> calls a service that takes a lot of time >>your process dont want to wait but rather call backed of the responce. >> >>So why cant you simply do a fully async call in your process to the >>service. What i ment by fully async is to use the async client api as >>well as to use a seperate transport to get the responce back. So even >>if the service takes a time greate than HTTP timeout, you will be safe >>because the responce is sent back in a seperate Transport. >>What really happenns is, when you register a seperate transport in the >>client call axis2 client will send the SOAP request to the server and >>close the HTTP connection. In the meantime the cilent will start a >>small HTTP server that will listen to incomming SOAP responce to the >>request it sent earlier. Once the responce is received at the cilent >>it will notifiy a callback object registed with it. So doesnt matter >>how long the service takes cilen can wait and further your process >>will not get blocked because its using the async api. >>Have a look at the following article by me fellow devs for further >>information about the CLient API architecture. >>http://www.onjava.com/pub/a/onjava/2005/07/27/axis2.html?page=3 (Code >>there is outdates) >>HTH >>THanks >>Chathura >> >> >> >>On 3/8/06, SOA Work <[EMAIL PROTECTED]> wrote: >> >> >>>Hm, okay. I guess my questions are missleding you. I'm looking for an axis >>>user which covered the same design problem as I do, your answers are more >>>about the technical axis architecture. >>> >>>On the axis2 (and your) point of view a service can be sync and async (just >>>a matter of messagereceiver). >>> >>>My problem is a little different and maybe not an issue for technical >>>discussion more a design issue. >>>f.e.: >>>what I have: >>>a process covering a holiday order >>>a web service covering user interaction >>> >>>1. ) I want the process to invoke the service on an async way (<- that's it >>>where your answers are pointing, how to create a service with an >>>async-only-in-message-receiver ) >>>2.) the user takes a lot of time to decide what to do >>>3.) the service makes a callback to the bpel process >>> >>>My question was about the hole scenario. How to implement the service part >>>and how to create the callback? Now I'm going to create a service with an >>>async void operation. After the user made his decision, I'm going to use the >>>axis client api to callback a wsdl port on the bpel process. >>> >>>So my question is cleared. >>>Thx >>>Dominik >>> >>>[email protected] schrieb am 08.03.06 14:05:12: >>> >>> >>>>Hi guys, >>>>I believe we did give a considerable thought to this very problem >>>>during architecture discussions in Axis2. >>>>Dominik, Could you try one more time refrasing the question please. I >>>>am sure we can answer this. >>>>Here is an answer to the question as i understod it. >>>>Serverside sync or async issue is a serverside programming model issue >>>>rather WSDL issue. So you need to explecitly decide the serverside >>>>asyncness as you develop the service(ideally as you deploy the >>>>service). >>>>If you are asking whether the async service is deployed in a different >>>>Endpoint than the sync service,( i.e. every service has two endpoints >>>>one syn and one async??) .The answer is no. >>>>You should decide sync async ness of the service before deployment. >>>>WSDL nor the endpoint has nothing to do with sync asyncness of the >>>>service. >>>>How do you do this async service in Axis2.... You use a special >>>>MessageReceiver. Have a look at >>>>org.apache.axis2.receivers.AbstractInOutAsyncMessageReceiver. >>>>I am sure Deepals sample will extend this message receiver. >>>>Did i answer the right question?? >>>> >>>>Thanks >>>>Chathura >>>> >>>>On 3/8/06, SOA Work <[EMAIL PROTECTED]> wrote: >>>> >>>> >>>>>No problem. A sample would be nice. Async services could be very important >>>>>for bpel and user interaction. >>>>> >>>>>Does somebody know an answer to my questions: >>>>>How does it know which operation on wich port type on wich endpoint it has >>>>>to call (for callback)? >>>>>Is there any message added to the soap request? >>>>> >>>>>[email protected] schrieb am 08.03.06 11:10:36: >>>>> >>>>> >>>>>>right now I dont have a sample server side service to give you (I am >>>>>>very sorry for that) , but I will give you a sample soon >>>>>> >>>>>>For the client side we have bunch of samples in the site as well as SVN. >>>>>> >>>>>> >>>>>>SOA Work wrote: >>>>>> >>>>>> >>>>>> >>>>>>>Hm now I am confused. >>>>>>>If I invoke a service async. >>>>>>>How does it know which operation on wich port type on wich endpoint it >>>>>>>has to call (for callback)? >>>>>>> >>>>>>>Is there any message added to the soap request? >>>>>>> >>>>>>>Is there an sample for server side async service? >>>>>>> >>>>>>>Dominik >>>>>>> >>>>>>> >>>>>>>[email protected] schrieb am 08.03.06 09:39:21: >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>>>Hi; >>>>>>>> >>>>>>>>We can support both server side and client side asynchronous , we have >>>>>>>>fully tested the client side but not the server side , and we can >>>>>>>>support serve side async by adding custom message receiver. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>>The asynchronous capability in axis2? Isn't it client side? >>>>>>>>>I thought about writing the service. I'll handle the problem with a >>>>>>>>>void operation and later "client side axis" to callback. >>>>>>>>> >>>>>>>>>Thx >>>>>>>>>Dominik >>>>>>>>> >>>>>>>>> >>>>>>>>>[email protected] schrieb am 08.03.06 05:20:42: >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>>Well , In Axis2 you have asynchronous capability , so I think you can >>>>>>>>>>use Axis2 . >>>>>>>>>> >>>>>>>>>>Prashanth.S wrote: >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>Cant you use SOAP over JMS rather than SOAP over HTTP?? >>>>>>>>>>>I think it provides async invocations using queues. >>>>>>>>>>> >>>>>>>>>>>Rgds >>>>>>>>>>>Prashanth >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>*/SOA Work <[EMAIL PROTECTED]>/* wrote: >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Hi there, >>>>>>>>>>> >>>>>>>>>>> almost every BPEL guide is talking about invoking services in a >>>>>>>>>>> asynchronous way and reveiving the result via callback later. Now >>>>>>>>>>> I was thinking about how such a service in axis or axis2 would >>>>>>>>>>> look like. >>>>>>>>>>> >>>>>>>>>>> I guess the service has to now the callback port and maybe the >>>>>>>>>>> endpoint. At the end of the operation the service has to use the >>>>>>>>>>> client side axis and callback the process. >>>>>>>>>>> >>>>>>>>>>> Does somebody do any similar? Any examples? Is there a way how to >>>>>>>>>>> determine from which sender the invocation was received? >>>>>>>>>>> >>>>>>>>>>> Best regards >>>>>>>>>>> Dominik >>>>>>>>>>> >>>>>>>>>>> __________________________________________________________________________ >>>>>>>>>>> Erweitern Sie FreeMail zu einem noch leistungsstarkeren >>>>>>>>>>> E-Mail-Postfach! >>>>>>>>>>> Mehr Infos unter http://freemail.web.de/home/landingpad/?mc=021131 >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>------------------------------------------------------------------------ >>>>>>>>>>>Do you Yahoo!? >>>>>>>>>>>New and Improved Yahoo! Mail >>>>>>>>>>><http://sg.rd.yahoo.com/mail/sg/footer/def/*http://sg.whatsnew.mail.yahoo.com> >>>>>>>>>>>- 1GB free storage! >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>-- >>>>>>>>>>Thanks, >>>>>>>>>>Deepal >>>>>>>>>>................................................................ >>>>>>>>>>~Future is Open~ >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>______________________________________________________________ >>>>>>>>>Verschicken Sie romantische, coole und witzige Bilder per SMS! >>>>>>>>>Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193 >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>-- >>>>>>>>Thanks, >>>>>>>>Deepal >>>>>>>>................................................................ >>>>>>>>~Future is Open~ >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>______________________________________________________________________ >>>>>>>XXL-Speicher, PC-Virenschutz, Spartarife & mehr: Nur im WEB.DE Club! >>>>>>>Jetzt gratis testen! http://freemail.web.de/home/landingpad/?mc=021130 >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>-- >>>>>>Thanks, >>>>>>Deepal >>>>>>................................................................ >>>>>>~Future is Open~ >>>>>> >>>>>> >>>>>> >>>>>> >>>>>______________________________________________________________ >>>>>Verschicken Sie romantische, coole und witzige Bilder per SMS! >>>>>Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193 >>>>> >>>>> >>>>> >>>>> >>>>-- >>>>Chathura Herath >>>>http://people.apache.org/~chathura/ >>>>http://chathurah.blogspot.com/ >>>> >>>> >>>______________________________________________________________ >>>Verschicken Sie romantische, coole und witzige Bilder per SMS! >>>Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193 >>> >>> >>> >>> >>-- >>Chathura Herath >>http://people.apache.org/~chathura/ >>http://chathurah.blogspot.com/ >> >> > > >______________________________________________________________ >Verschicken Sie romantische, coole und witzige Bilder per SMS! >Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193 > > > > > -- Thanks, Deepal ................................................................ ~Future is Open~
