Re: [Axis2] Handling request-responseS type messaging

2006-03-17 Thread Anne Thomas Manes
Ali, Do you mean; 1) Client sends request without waiting a response to it. Request has a CSV tag which has many lines to process. 2) Server processes the message and sends a result for each line in CS V. It sends results to the client without waiting a response.Yes. (Or alternatively, each

Re: [Axis2] Handling request-responseS type messaging

2006-03-17 Thread Ali Sadik Kumlali
Thank you Anne. But, AFAIK, WSDL does not support IN-Multiple OUT as operation type. If WSDL does not has signature for multiple results, how can client assume that it must wait for more than one results?Thanks a lot,Ali Sadik KumlaliAnne Thomas Manes [EMAIL PROTECTED] wrote: Ali, Do you mean;

Re: [Axis2] Handling request-responseS type messaging

2006-03-17 Thread Anne Thomas Manes
Add a decrementing count element to the message. In any case, the client should know the cardinality of its initial request message. Therefore it should know how many response messages it expects to receive. (Note that these response messages are, technically, request messages.) AnneOn 3/17/06,

[Axis2] Handling request-responseS type messaging

2006-03-16 Thread Ali Sadik Kumlali
Dear all,There is an interesting messaging pattern between my company and its partner. Partner sends a message containing a tag named CSV that has multiple lines in it. Although we process all of them separately, we assume it as one message. After processing has been completed, we send a result

Re: [Axis2] Handling request-responseS type messaging

2006-03-16 Thread Eran Chinthaka
Hi Ali, Interesting scenario. First of all, Axis2 supports IN only and IN-OUT invocations by *default.* But thats doesn't mean we can not do IN-multiple OUT meps. Yes, we haven't come across them so far, but our pipe model enables custom MEPs. If you really need this we can give a try to

Re: [Axis2] Handling request-responseS type messaging

2006-03-16 Thread Anne Thomas Manes
You can also implement the pattern using one-way messages.AnneOn 3/16/06, Eran Chinthaka [EMAIL PROTECTED] wrote:Hi Ali,Interesting scenario.First of all, Axis2 supports IN only and IN-OUT invocations by *default.* But thats doesn't mean we can not do IN-multiple OUT meps.Yes, we haven't come

Re: [Axis2] Handling request-responseS type messaging

2006-03-16 Thread Ali Sadik Kumlali
Hi Eran, Hi Anne!What a quick response! What a good community! Thank you very very much. I love this community and hope companies discover the power of open-source products. I post your responses to my colleagues in the company to let them recognize that support does not always mean money,