Hi Ben, it's strange that the offered sequence is not used by the server. (I assume you are not explicitly setting the destination policy to reject the offers.)
I just tried out a similar test case using 2.6.0-snapshot and saw the offered sequence used by the server. Maybe, can you run your test with 2.5.3-snapshot or 2.6.0-snapshot to see if the problem exists there as well? I am short of time today and I can look into it again next week. regards, aki 2012/3/16 Ben Pezzei <ben.pez...@gmail.com>: > Hi Aki, > > tnx for your reply, > > 2012/3/16 Aki Yoshida <elak...@googlemail.com>: >> I suppose you meant by "synchronous approach" a WS-RM scenario where >> each ack message must be returned to the caller in its http response >> synchronously. And do you have a request-response service, as you are >> talking about the offer option? > > Yeah, but actually I meant, that the client does not make any use of a > decoupled endpoint. Basically the setup is like described in: > https://issues.apache.org/jira/browse/CXF-3777 > >> Regarding the issue about CXF trying to send a message to www.w3.org, >> there was a similar issue CXF-3777 which was fixed in 2.4.3. I'll >> check how your case relates to this. > > I guess that in our situation we have to use an offerId (else the > communication > breaks earlier). > > The other thing which probably escapes my understanding is an example like: > http://rajikak.blogspot.com/2011/05/short-tutorial-on-ws-rm.html > > Why does the client send an SequenceAcknowledge for an Id (code > 5,offered id) which > was initially discarded by the server(Destination)? > > Which again leads me to another Question: The code in > org.apache.cxf.ws.rm.Servant > (line 156 in cxf 2.4.4) appears to be not working (on first sight). > > tnx & regards > Ben
