You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by "gregory.lebonniec" <ke...@yahoo.fr> on 2009/06/25 12:40:50 UTC
WS-Addressing and Asynchronous processes
Hello,
I have two questions concerning WS-Addressing and Asynchrony :
1. Concerning the CXF WS-Addressing example, I don't understand the purpose
of WS-Addressing in this case because when the client calls the service, it
is blocked (no callback method). So why send the response on another port if
the thread blocks on call ?
2. What I am looking for is to developp an asynchronous WS-Addressing
process with callback handling. In CXF, I have found async processes but the
mecanisms are "native" to CXF and the previous example is not dealing with
asynchrony. Is there a sample which mixes asynchronous process with
WS-Addressing ?
Thank you
Regards,
Greg
--
View this message in context: http://www.nabble.com/WS-Addressing-and-Asynchronous-processes-tp24200929p24200929.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: WS-Addressing and Asynchronous processes
Posted by Eoghan Glynn <eo...@gmail.com>.
2009/6/26 Daniel Kulp <dk...@apache.org>:
>
> Most likely, just add a jaxws binding file to the wsdl2java stuff in the ws-
> addressing sample to make it generate the async methods and update the client
> to use the async methods instead. (or in addition to)
>
> That SHOULD be all that is needed.
Just be sure also that you don't build the implementor against the
generated SEI with the additional *Async() methods.
Otherwise your impl class will have to needlessly add no-op
implementations of these methods, even though they'll never be called
on the server side. The jaxws_async demo uses the same generated code
for client and server, thus it falls into this trap.
Cheers,
Eoghan
>
> Dan
>
>
> On Thu June 25 2009 10:00:03 am gregory.lebonniec wrote:
>> That's totally what I want to do.
>> I am gonna try to mix the two examples...I promess ;-)
>>
>> Thank you everybody for your help !
>>
>> Eoghan Glynn-4 wrote:
>> > Hi Gregory,
>> >
>> > You're conflating asynchrony with decoupled addressing.
>> >
>> > JAX-WS asynch helps you to build asynchrony into the application (see
>> > the jaxws_async demo). This avoids tieing up an application-level
>> > thread for the duration of the invocation.
>> >
>> > WS-Addressing allows the response to be sent back over a separate
>> > server->client connection. This avoid tieing up a transport-level
>> > connection for the duration of the invocation.
>> >
>> > There are orthogonal concerns. JAX-WS async and/or WS-A can be used
>> > together or separately depending on what you want to achieve. There
>> > isn't a demo showing both together, but it shouldn't be hard for you
>> > to munge the two separate demos.
>> >
>> > Cheers,
>> > Eoghan
>> >
>> > 2009/6/25 gregory.lebonniec <ke...@yahoo.fr>:
>> >> Hello,
>> >>
>> >> I have two questions concerning WS-Addressing and Asynchrony :
>> >>
>> >> 1. Concerning the CXF WS-Addressing example, I don't understand the
>> >> purpose
>> >> of WS-Addressing in this case because when the client calls the service,
>> >> it
>> >> is blocked (no callback method). So why send the response on another
>> >> port if
>> >> the thread blocks on call ?
>> >> 2. What I am looking for is to developp an asynchronous WS-Addressing
>> >> process with callback handling. In CXF, I have found async processes but
>> >> the
>> >> mecanisms are "native" to CXF and the previous example is not dealing
>> >> with
>> >> asynchrony. Is there a sample which mixes asynchronous process with
>> >> WS-Addressing ?
>> >>
>> >> Thank you
>> >>
>> >> Regards,
>> >>
>> >> Greg
>> >> --
>> >> View this message in context:
>> >> http://www.nabble.com/WS-Addressing-and-Asynchronous-processes-tp2420092
>> >>9p24200929.html Sent from the cxf-user mailing list archive at
>> >> Nabble.com.
>
> --
> Daniel Kulp
> dkulp@apache.org
> http://www.dankulp.com/blog
>
Re: WS-Addressing and Asynchronous processes
Posted by Daniel Kulp <dk...@apache.org>.
Most likely, just add a jaxws binding file to the wsdl2java stuff in the ws-
addressing sample to make it generate the async methods and update the client
to use the async methods instead. (or in addition to)
That SHOULD be all that is needed.
Dan
On Thu June 25 2009 10:00:03 am gregory.lebonniec wrote:
> That's totally what I want to do.
> I am gonna try to mix the two examples...I promess ;-)
>
> Thank you everybody for your help !
>
> Eoghan Glynn-4 wrote:
> > Hi Gregory,
> >
> > You're conflating asynchrony with decoupled addressing.
> >
> > JAX-WS asynch helps you to build asynchrony into the application (see
> > the jaxws_async demo). This avoids tieing up an application-level
> > thread for the duration of the invocation.
> >
> > WS-Addressing allows the response to be sent back over a separate
> > server->client connection. This avoid tieing up a transport-level
> > connection for the duration of the invocation.
> >
> > There are orthogonal concerns. JAX-WS async and/or WS-A can be used
> > together or separately depending on what you want to achieve. There
> > isn't a demo showing both together, but it shouldn't be hard for you
> > to munge the two separate demos.
> >
> > Cheers,
> > Eoghan
> >
> > 2009/6/25 gregory.lebonniec <ke...@yahoo.fr>:
> >> Hello,
> >>
> >> I have two questions concerning WS-Addressing and Asynchrony :
> >>
> >> 1. Concerning the CXF WS-Addressing example, I don't understand the
> >> purpose
> >> of WS-Addressing in this case because when the client calls the service,
> >> it
> >> is blocked (no callback method). So why send the response on another
> >> port if
> >> the thread blocks on call ?
> >> 2. What I am looking for is to developp an asynchronous WS-Addressing
> >> process with callback handling. In CXF, I have found async processes but
> >> the
> >> mecanisms are "native" to CXF and the previous example is not dealing
> >> with
> >> asynchrony. Is there a sample which mixes asynchronous process with
> >> WS-Addressing ?
> >>
> >> Thank you
> >>
> >> Regards,
> >>
> >> Greg
> >> --
> >> View this message in context:
> >> http://www.nabble.com/WS-Addressing-and-Asynchronous-processes-tp2420092
> >>9p24200929.html Sent from the cxf-user mailing list archive at
> >> Nabble.com.
--
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog
Re: WS-Addressing and Asynchronous processes
Posted by "gregory.lebonniec" <ke...@yahoo.fr>.
That's totally what I want to do.
I am gonna try to mix the two examples...I promess ;-)
Thank you everybody for your help !
Eoghan Glynn-4 wrote:
>
> Hi Gregory,
>
> You're conflating asynchrony with decoupled addressing.
>
> JAX-WS asynch helps you to build asynchrony into the application (see
> the jaxws_async demo). This avoids tieing up an application-level
> thread for the duration of the invocation.
>
> WS-Addressing allows the response to be sent back over a separate
> server->client connection. This avoid tieing up a transport-level
> connection for the duration of the invocation.
>
> There are orthogonal concerns. JAX-WS async and/or WS-A can be used
> together or separately depending on what you want to achieve. There
> isn't a demo showing both together, but it shouldn't be hard for you
> to munge the two separate demos.
>
> Cheers,
> Eoghan
>
>
>
>
> 2009/6/25 gregory.lebonniec <ke...@yahoo.fr>:
>>
>> Hello,
>>
>> I have two questions concerning WS-Addressing and Asynchrony :
>>
>> 1. Concerning the CXF WS-Addressing example, I don't understand the
>> purpose
>> of WS-Addressing in this case because when the client calls the service,
>> it
>> is blocked (no callback method). So why send the response on another port
>> if
>> the thread blocks on call ?
>> 2. What I am looking for is to developp an asynchronous WS-Addressing
>> process with callback handling. In CXF, I have found async processes but
>> the
>> mecanisms are "native" to CXF and the previous example is not dealing
>> with
>> asynchrony. Is there a sample which mixes asynchronous process with
>> WS-Addressing ?
>>
>> Thank you
>>
>> Regards,
>>
>> Greg
>> --
>> View this message in context:
>> http://www.nabble.com/WS-Addressing-and-Asynchronous-processes-tp24200929p24200929.html
>> Sent from the cxf-user mailing list archive at Nabble.com.
>>
>>
>
>
--
View this message in context: http://www.nabble.com/WS-Addressing-and-Asynchronous-processes-tp24200929p24203785.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: WS-Addressing and Asynchronous processes
Posted by Eoghan Glynn <eo...@gmail.com>.
Hi Gregory,
You're conflating asynchrony with decoupled addressing.
JAX-WS asynch helps you to build asynchrony into the application (see
the jaxws_async demo). This avoids tieing up an application-level
thread for the duration of the invocation.
WS-Addressing allows the response to be sent back over a separate
server->client connection. This avoid tieing up a transport-level
connection for the duration of the invocation.
There are orthogonal concerns. JAX-WS async and/or WS-A can be used
together or separately depending on what you want to achieve. There
isn't a demo showing both together, but it shouldn't be hard for you
to munge the two separate demos.
Cheers,
Eoghan
2009/6/25 gregory.lebonniec <ke...@yahoo.fr>:
>
> Hello,
>
> I have two questions concerning WS-Addressing and Asynchrony :
>
> 1. Concerning the CXF WS-Addressing example, I don't understand the purpose
> of WS-Addressing in this case because when the client calls the service, it
> is blocked (no callback method). So why send the response on another port if
> the thread blocks on call ?
> 2. What I am looking for is to developp an asynchronous WS-Addressing
> process with callback handling. In CXF, I have found async processes but the
> mecanisms are "native" to CXF and the previous example is not dealing with
> asynchrony. Is there a sample which mixes asynchronous process with
> WS-Addressing ?
>
> Thank you
>
> Regards,
>
> Greg
> --
> View this message in context: http://www.nabble.com/WS-Addressing-and-Asynchronous-processes-tp24200929p24200929.html
> Sent from the cxf-user mailing list archive at Nabble.com.
>
>
AW: WS-Addressing and Asynchronous processes
Posted by Diefenbach Anne <Di...@fgan.de>.
Hi Gregory,
concerning your second question, there is a callback example in the samples directory. Is that what you're looking for?
Regards, Anne
> -----Ursprüngliche Nachricht-----
> Von: gregory.lebonniec [mailto:kergadic35@yahoo.fr]
> Gesendet: Donnerstag, 25. Juni 2009 12:41
> An: users@cxf.apache.org
> Betreff: WS-Addressing and Asynchronous processes
>
>
> Hello,
>
> I have two questions concerning WS-Addressing and Asynchrony :
>
> 1. Concerning the CXF WS-Addressing example, I don't understand the
> purpose
> of WS-Addressing in this case because when the client calls the service,
> it
> is blocked (no callback method). So why send the response on another port
> if
> the thread blocks on call ?
> 2. What I am looking for is to developp an asynchronous WS-Addressing
> process with callback handling. In CXF, I have found async processes but
> the
> mecanisms are "native" to CXF and the previous example is not dealing with
> asynchrony. Is there a sample which mixes asynchronous process with
> WS-Addressing ?
>
> Thank you
>
> Regards,
>
> Greg
> --
> View this message in context: http://www.nabble.com/WS-Addressing-and-
> Asynchronous-processes-tp24200929p24200929.html
> Sent from the cxf-user mailing list archive at Nabble.com.