Slight clarification... the constraint would only apply when [reply to] is anonymous. Cheers, Christopher Ferris STSM, Emerging e-business Industry Architecture email: chrisfer@us.ibm.com blog: http://www.ibm.com/developerworks/blogs/dw_blog.jspa?blog=440 phone: +1 508 377 9295 public-ws-addressing-request@w3.org wrote on 02/21/2006 02:44:47 PM: > > Probably broken. > > I am in the process of submitting an issue to the WS-RX TC about > that. IMO, it probably needs to be (at least in the HTTP case) > a non-anon URI EPR in the CSR/Accept/AcksTo. > > Cheers, > > Christopher Ferris > STSM, Emerging e-business Industry Architecture > email: chrisfer@us.ibm.com > blog: http://www.ibm.com/developerworks/blogs/dw_blog.jspa?blog=440 > phone: +1 508 377 9295 > > public-ws-addressing-request@w3.org wrote on 02/21/2006 01:59:37 PM: > > > > > I'm a bit loath to send this to the whole WS-RX list, and I think there > > are enough WS-RXperts here to answer, so ... > > > > Suppose I use an ordinary request-response, with anonymous [reply > > endpoint], to create a sequence. In that request, I wsrm:Offer to > > create a sequence the other way. The receiver of the request responds > > with wsrm:Accept. This has wsrm:AcksTo anonymous. > > > > What happens? > > > >
Received on Tuesday, 21 February 2006 20:15:54 UTC