On Wednesday 22 September 2010 8:24:39 am Aki Yoshida wrote:
Hi,
regarding this HTTP 202 problem for a piggybacked WS-RM ack response,
I created the jira entry:
CXF-3004
Inconsistent HTTP response code 202 returned for WS-RM piggybacked Ack
response message
I'll try an take a look.
Hi,
regarding this HTTP 202 problem for a piggybacked WS-RM ack response,
I created the jira entry:
CXF-3004
Inconsistent HTTP response code 202 returned for WS-RM piggybacked Ack
response message
regards, aki
I noticed an inconsistent HTTP response code in the WS-RM server side
implementation that can lead to interoperability issues. This can be
observed in the sample demo scenario.
The WS-RM spec refers to WS-I Basic Profile for its HTTP binding
behavior and the profile states:
- R An INSTANCE
