Charles, The CXF WS-RM layer expects the wsrm:AcksTo address to be non-anonymous, i.e. not equal to "http://www.w3.org/2005/08/addressing/anonymous<http://www.w3.org/2005/08/addressing/anonymous?id=2e7dfecf-f888-45c6-8c21-5a10038ea9bc> ".
This is in order to allow timely ACKs to be sent in the absence of a steady stream of non-oneway requests (on the responses to which, the pending ACKs could be piggy-backed). Because such a regular stream of incoming requests is not in general guaranteed, CXF requires that the AcksTo address is not anonymous. We will be able to relax this requirement when we move up to WS-RM 1.1 support (as this includes a mechanism for the client-side to probe for pending ACKs). Cheers, Eoghan On 15 February 2010 17:16, cmoulliard <[email protected]> wrote: > > Hi, > > I run an example of CXF using WS-RM spec 1.0 and I try to see the ACK. > Unfortunately, this is not the case. > > Is it possible to receive an ACK ? > Could this problem be related to ANONYMOUS TARGET (see text of the log here > after) ? > > 17:56:49,937 | INFO | 8...@qtp-32549725-0 | RetransmissionQueueImpl > | > missionQueueImpl$ResendCandidate 402 | Cannot resend to anonymous target. > Not sch > eduling a resend. > 17:56:49,953 | INFO | 8...@qtp-32549725-0 | LoggingOutInterceptor > | > ngOutInterceptor$LoggingCallback 170 | Outbound Message > .... > -------------------------------------- > 17:56:51,734 | WARN | r-Timer-15060249 | Proxy > | > org.apache.cxf.ws.rm.Proxy 72 | STANDALONE_ANON_ACKS_NOT_SUPPORTED > > > Kind regards, > > Charles > > ----- > Charles Moulliard > SOA Architect > > My Blog : http://cmoulliard.blogspot.com/ http://cmoulliard.blogspot.com/ > -- > View this message in context: > http://old.nabble.com/How-can-we-receive-ACK-using-CXF-and-WS-RM---tp27596956p27596956.html > Sent from the cxf-user mailing list archive at Nabble.com. > >
