You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Ali Sadik Kumlali <as...@yahoo.com> on 2006/03/16 14:55:39 UTC
[Axis2] Handling request-responseS type messaging
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 message for every line in CSV.
Thus, request-responseS type messaging occurs.
This seems very strange when I look at the async messaging
samples that come with Axis2. If I understand correctly, when
client sends a request in an async-non blocker way, it also
starts an http server to listen response. When the server finishes
processing, it sends the result back to the client's http server.
Consequently, each request has one response.
AFAIK, we are allowed to have one-way and request-response
type operations, but not request-responseS.
Is there a way to handle request-responseS type messaging
with Axis2? Or do I need to convince my boss to give these kind
of messaging up? :)
Thanks a lot,
Ali Sadik Kumlali
---------------------------------
Yahoo! Mail
Bring photos to life! New PhotoMail makes sharing a breeze.
Re: [Axis2] Handling request-responseS type messaging
Posted by Anne Thomas Manes <at...@gmail.com>.
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.)
Anne
On 3/17/06, Ali Sadik Kumlali <as...@yahoo.com> wrote:
>
> 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 Kumlali
>
> *Anne Thomas Manes <at...@gmail.com>* wrote:
>
> 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 message exchange could return an "ack", which
> would be easier to implement if you're using Axis 1.)
>
> Anne
>
> On 3/16/06, Al i Sadik Kumlali <as...@yahoo.com> wrote:
>
> > 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, and vice versa :)
>
> Eran,
>
> Our current implementation uses DocSoap XDK based custom codes. Since we
> are required to handle all the soap related stuff manually, we are able to
> support "IN-multiple OUT" type messaging. Actually, manual operations are
> one of the reasons we want to give DocSoap XDK up. Therefore, it would be
> great if I could find a robust way in Axis2 to support "IN-multiple OUT"
> type messaging.
>
> Anne,
>
> 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.
>
> Many thanks to you both!
>
> Ali Sadik Kumlali
>
>
> *Anne Thomas Manes < atmanes@gmail.com>* wrote:
>
> You can also implement the pattern using one-way messages.
>
> Anne
>
> On 3/16/06, Eran Chinthaka <chinthaka@opensource.lk > 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 across them so far, but our pipe model enables
> custom MEPs. If you really ne ed this we can give a try to implement the
>
> first custom MEP using Axi s2. (or you can convince your boss otherwise
> ;-) )
>
>
> -- Chinthaka
>
> Ali Sadik Kumlali wrote:
> > 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 message for every line in CSV.
> > Thus, request-responseS type messaging occurs.
> >
> > This seems very strange when I look at the async messaging
> > samples that come with Axis2. If I understand correctly, when
> > client sends a request in an async-non blocker way, it also
> > starts an http server to listen response. When the server finishes
> > processing, it sends the result back to the client's http server.
> > Consequently, each request has one response.
> >
> > AFAIK, we a re allowed to have one-way and request-response
>
> > type operations, but not request-responseS.
> >
> > Is there a way to handle request-responseS type messaging
> > with Axis2? Or do I ne ed to convince my boss to give these kind
> > of messaging up? :)
> >
> > Thanks a lot,
> >
> > Ali Sadik Kumlali
> >
> > ------------------------------------------------------------------------
>
> > Yahoo! Mail
> > Bring photos to life! New PhotoMail
> > <http://pa.yahoo.com/*http://us.rd.yahoo.com/evt=39174/*http://photomail.mail.yahoo.com
> >
> > makes sharing a breeze.
>
>
>
> ------------------------------
> Yahoo! Mail
> Use Photomail<http://pa.yahoo.com/*http://us.rd.yahoo.com/evt=38867/*http://photomail.mail.yahoo.com>to share photos without annoying attachments.
>
>
> ------------------------------
> Yahoo! Mail
> Bring photos to life! New PhotoMail
> <http://pa.yahoo.com/*http://us.rd.yahoo.com/evt=39174/*http://photomail.mail.yahoo.com>makes sharing a breeze.
>
>
Re: [Axis2] Handling request-responseS type messaging
Posted by Ali Sadik Kumlali <as...@yahoo.com>.
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 Kumlali
Anne Thomas Manes <at...@gmail.com> wrote: 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 message exchange could return an "ack", which would be easier to implement if you're using Axis 1.)
Anne
On 3/16/06, Ali Sadik Kumlali <as...@yahoo.com> wrote: 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, and vice versa :)
Eran,
Our current implementation uses DocSoap XDK based custom codes. Since we are required to handle all the soap related stuff manually, we are able to support "IN-multiple OUT" type messaging. Actually, manual operations are one of the reasons we want to give DocSoap XDK up. Therefore, it would be great if I could find a robust way in Axis2 to support "IN-multiple OUT" type messaging.
Anne,
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.
Many thanks to you both!
Ali Sadik Kumlali
Anne Thomas Manes < atmanes@gmail.com> wrote:
You can also implement the pattern using one-way messages.
Anne
On 3/16/06, Eran Chinthaka <chinthaka@opensource.lk > 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 across them so far, but our pipe model enables
custom MEPs. If you really ne ed this we can give a try to implement the
first custom MEP using Axis2. (or you can convince your boss otherwise ;-) )
-- Chinthaka
Ali Sadik Kumlali wrote:
> 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 message for every line in CSV.
> Thus, request-responseS type messaging occurs.
>
> This seems very strange when I look at the async messaging
> samples that come with Axis2. If I understand correctly, when
> client sends a request in an async-non blocker way, it also
> starts an http server to listen response. When the server finishes
> processing, it sends the result back to the client's http server.
> Consequently, each request has one response.
>
> AFAIK, we are allowed to have one-way and request-response
> type operations, but not request-responseS.
>
> Is there a way to handle request-responseS type messaging
> with Axis2? Or do I ne ed to convince my boss to give these kind
> of messaging up? :)
>
> Thanks a lot,
>
> Ali Sadik Kumlali
>
> ------------------------------------------------------------------------
> Yahoo! Mail
> Bring photos to life! New PhotoMail
> < http://pa.yahoo.com/*http://us.rd.yahoo.com/evt=39174/*http://photomail.mail.yahoo.com >
> makes sharing a breeze.
---------------------------------
Yahoo! Mail
Use Photomail to share photos without annoying attachments.
---------------------------------
Yahoo! Mail
Bring photos to life! New PhotoMail makes sharing a breeze.
Re: [Axis2] Handling request-responseS type messaging
Posted by Anne Thomas Manes <at...@gmail.com>.
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 message exchange could return an "ack", which
would be easier to implement if you're using Axis 1.)
Anne
On 3/16/06, Ali Sadik Kumlali <as...@yahoo.com> wrote:
>
> 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, and vice versa :)
>
> Eran,
>
> Our current implementation uses DocSoap XDK based custom codes. Since we
> are required to handle all the soap related stuff manually, we are able to
> support "IN-multiple OUT" type messaging. Actually, manual operations are
> one of the reasons we want to give DocSoap XDK up. Therefore, it would be
> great if I could find a robust way in Axis2 to support "IN-multiple OUT"
> type messaging.
>
> Anne,
>
> 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.
>
> Many thanks to you both!
>
> Ali Sadik Kumlali
>
>
> *Anne Thomas Manes <at...@gmail.com>* wrote:
>
> You can also implement the pattern using one-way messages.
>
> Anne
>
> On 3/16/06, Eran Chinthaka <chinthaka@opensource.lk > 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 across them so far, but our pipe model enables
> custom MEPs. If you really ne ed this we can give a try to implement the
>
> first custom MEP using Axis2. (or you can convince your boss otherwise ;-)
> )
>
> -- Chinthaka
>
> Ali Sadik Kumlali wrote:
> > 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 message for every line in CSV.
> > Thus, request-responseS type messaging occurs.
> >
> > This seems very strange when I look at the async messaging
> > samples that come with Axis2. If I understand correctly, when
> > client sends a request in an async-non blocker way, it also
> > starts an http server to listen response. When the server finishes
> > processing, it sends the result back to the client's http server.
> > Consequently, each request has one response.
> >
> > AFAIK, we are allowed to have one-way and request-response
> > type operations, but not request-responseS.
> >
> > Is there a way to handle request-responseS type messaging
> > with Axis2? Or do I ne ed to convince my boss to give these kind
> > of messaging up? :)
> >
> > Thanks a lot,
> >
> > Ali Sadik Kumlali
> >
> > ------------------------------------------------------------------------
>
> > Yahoo! Mail
> > Bring photos to life! New PhotoMail
> > <http://pa.yahoo.com/*http://us.rd.yahoo.com/evt=39174/*http://photomail.mail.yahoo.com
> >
> > makes sharing a breeze.
>
>
>
> ------------------------------
> Yahoo! Mail
> Use Photomail<http://pa.yahoo.com/*http://us.rd.yahoo.com/evt=38867/*http://photomail.mail.yahoo.com>to share photos without annoying attachments.
>
>
Re: [Axis2] Handling request-responseS type messaging
Posted by Ali Sadik Kumlali <as...@yahoo.com>.
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, and vice versa :)
Eran,
Our current implementation uses DocSoap XDK based custom codes. Since we are required to handle all the soap related stuff manually, we are able to support "IN-multiple OUT" type messaging. Actually, manual operations are one of the reasons we want to give DocSoap XDK up. Therefore, it would be great if I could find a robust way in Axis2 to support "IN-multiple OUT" type messaging.
Anne,
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 CSV. It sends results to the client without waiting a response.
Many thanks to you both!
Ali Sadik Kumlali
Anne Thomas Manes <at...@gmail.com> wrote: You can also implement the pattern using one-way messages.
Anne
On 3/16/06, Eran Chinthaka <chinthaka@opensource.lk > 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 across them so far, but our pipe model enables
custom MEPs. If you really need this we can give a try to implement the
first custom MEP using Axis2. (or you can convince your boss otherwise ;-) )
-- Chinthaka
Ali Sadik Kumlali wrote:
> 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 message for every line in CSV.
> Thus, request-responseS type messaging occurs.
>
> This seems very strange when I look at the async messaging
> samples that come with Axis2. If I understand correctly, when
> client sends a request in an async-non blocker way, it also
> starts an http server to listen response. When the server finishes
> processing, it sends the result back to the client's http server.
> Consequently, each request has one response.
>
> AFAIK, we are allowed to have one-way and request-response
> type operations, but not request-responseS.
>
> Is there a way to handle request-responseS type messaging
> with Axis2? Or do I ne ed to convince my boss to give these kind
> of messaging up? :)
>
> Thanks a lot,
>
> Ali Sadik Kumlali
>
> ------------------------------------------------------------------------
> Yahoo! Mail
> Bring photos to life! New PhotoMail
> <http://pa.yahoo.com/*http://us.rd.yahoo.com/evt=39174/*http://photomail.mail.yahoo.com >
> makes sharing a breeze.
---------------------------------
Yahoo! Mail
Use Photomail to share photos without annoying attachments.
Re: [Axis2] Handling request-responseS type messaging
Posted by Anne Thomas Manes <at...@gmail.com>.
You can also implement the pattern using one-way messages.
Anne
On 3/16/06, Eran Chinthaka <ch...@opensource.lk> 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 across them so far, but our pipe model enables
> custom MEPs. If you really need this we can give a try to implement the
> first custom MEP using Axis2. (or you can convince your boss otherwise ;-)
> )
>
> -- Chinthaka
>
> Ali Sadik Kumlali wrote:
> > 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 message for every line in CSV.
> > Thus, request-responseS type messaging occurs.
> >
> > This seems very strange when I look at the async messaging
> > samples that come with Axis2. If I understand correctly, when
> > client sends a request in an async-non blocker way, it also
> > starts an http server to listen response. When the server finishes
> > processing, it sends the result back to the client's http server.
> > Consequently, each request has one response.
> >
> > AFAIK, we are allowed to have one-way and request-response
> > type operations, but not request-responseS.
> >
> > Is there a way to handle request-responseS type messaging
> > with Axis2? Or do I ne ed to convince my boss to give these kind
> > of messaging up? :)
> >
> > Thanks a lot,
> >
> > Ali Sadik Kumlali
> >
> > ------------------------------------------------------------------------
> > Yahoo! Mail
> > Bring photos to life! New PhotoMail
> > <
> http://pa.yahoo.com/*http://us.rd.yahoo.com/evt=39174/*http://photomail.mail.yahoo.com
> >
> > makes sharing a breeze.
>
>
Re: [Axis2] Handling request-responseS type messaging
Posted by Eran Chinthaka <ch...@opensource.lk>.
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 implement the
first custom MEP using Axis2. (or you can convince your boss otherwise ;-) )
-- Chinthaka
Ali Sadik Kumlali wrote:
> 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 message for every line in CSV.
> Thus, request-responseS type messaging occurs.
>
> This seems very strange when I look at the async messaging
> samples that come with Axis2. If I understand correctly, when
> client sends a request in an async-non blocker way, it also
> starts an http server to listen response. When the server finishes
> processing, it sends the result back to the client's http server.
> Consequently, each request has one response.
>
> AFAIK, we are allowed to have one-way and request-response
> type operations, but not request-responseS.
>
> Is there a way to handle request-responseS type messaging
> with Axis2? Or do I ne ed to convince my boss to give these kind
> of messaging up? :)
>
> Thanks a lot,
>
> Ali Sadik Kumlali
>
> ------------------------------------------------------------------------
> Yahoo! Mail
> Bring photos to life! New PhotoMail
> <http://pa.yahoo.com/*http://us.rd.yahoo.com/evt=39174/*http://photomail.mail.yahoo.com>
> makes sharing a breeze.