On 09/01/2011 12:51 PM, Daniel Kulp wrote: > On Wednesday, August 31, 2011 11:27:20 PM Aki Yoshida wrote: > >> For example, when a WS-RM client with a decoupled endpoint sends an >> application message, the WS-RM server returns simply an HTTP 202 >> response with no content, as the real response is returned to the >> decoupled endpoint. >> >> ... > > I guess I would need answers to a few questions.... > > 1) What does the RM spec say? I assume the new behavior is the correct > behavior?
I don't see anything in the RM spec covering decoupled endpoints, but WS-MakeConnection (http://docs.oasis-open.org/ws-rx/wsmc/200702/wsmc-1.1-spec-os.html) shows 202 responses when no data is available. In the absence of any other guidelines, this is probably best for WS-RM, too. Aki, I'd suggest eliminating or simplifying existing WS-RM unit tests when there is no spec justification for the behavior being tested. Tests based solely on the current implementation are not appropriate. I've spent a lot of time fighting these in the past, and I'm sure you're experiencing the same. - Dennis
