[
https://issues.apache.org/jira/browse/CXF-3768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095931#comment-13095931
]
Aki Yoshida commented on CXF-3768:
----------------------------------
Regarding the related jira tickets, I found
CXF-366
mods to partial response mechanism to facilitate wider interop
CXF-981
Partial responses are always sent when WS-A is enabled
CXF-366 and CXF-981 both talk about suppressing the superfluous http 200
responses. Additionally, CXF-366 talks about accepting HTTP 200 with no
content, which is already implemented in CXF.
So, the patch for this CXF-3768 which suppresses the transmission of HTTP 200
empty SOAP envelope responses, I suppose these both issues can be resolved as
well.
I will also create a separate jira ticket to make the client side change that
is required for letting the CXF client handle HTTP 202 for the CreateSequence
call when the CreateSequenceResponse is sent back to the decoupled endpoint.
regards, aki
> HTTP response code 202 is not set for WS-Addressing partial responses
> ---------------------------------------------------------------------
>
> Key: CXF-3768
> URL: https://issues.apache.org/jira/browse/CXF-3768
> Project: CXF
> Issue Type: Bug
> Components: WS-* Components
> Affects Versions: 2.4.2
> Reporter: Dmytro Rud
> Assignee: Aki Yoshida
>
> When asyncronous processing is requested by specifying an endpoint reference
> in the request's ReplyTo WSA header, an immediate acknowledgement should be
> sent with HTTP code 202. Older CXF versions (e.g. 2.2.11) implemented this
> requirement in the method
> {{org.apache.cxf.transport.http.AbstractHTTPDestination#markPartialResponse}},
> but the newer ones (2.4.1, 2.4.2) do not set the HTTP response code
> explicitely, therefore acknowledgements are delivered with code 200.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
