riginal request due to the lack of a
response.
The key point to note is that RM has no concept of an over-arching message
exchange pattern such as request-response. It only guarantees delivery of
sequences of *individual* messages.
Cheers,
Eoghan
2009/8/6 EVENO Manuel
>
> Wouldn'
> -Original Message-
> From: EVENO Manuel [mailto:mev...@generali.fr]
> Sent: Thursday, August 06, 2009 10:39 AM
> To: users@cxf.apache.org
> Subject: RE: Asynchronous Invocation and connection keep alive on the
> TCP level
>
>
> Do you have example or docu
Do you have example or documentation of a "decoupled response endpoint"
or the callbacks-tyle mecanism you wrote about ?
I can find anything on the CXF Wiki ...
Manuel
-Message d'origine-
De : Eoghan Glynn [mailto:eogl...@gmail.com]
Envoyé : jeudi 6 août 2009 16:04
À : users@cxf.apache.
ow and where the timeout fired, and whether this
led to a timeout exception being propagated to the application layer.
Remember that WS-RM is all about resending lost messages, not about recovering
from failures exposed to the application layer.
Cheers,
Eoghan
2009/8/6 EVENO Manuel
>
> I
of view.
Cheers,
Eoghan
[1] http://specs.xmlsoap.org/ws/2005/02/rm/ws-reliablemessaging.pdf
2009/8/4 EVENO Manuel
>
> Hi Eoghan,
>
> I'll try to expose the problem I want to solve here :
> As WebService are not transactional, so in classic web services
> there's a
Here the log files again which seems to have been filtered ...
De : EVENO Manuel
Envoyé : lundi 3 août 2009 14:22
À : users@cxf.apache.org
Objet : WS-ReliableMessaging
Hi everyone,
I'm trying to create an sample with CXF and WS-ReliableMessaging.
