You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Guillaume Sauthier (JIRA)" <ji...@apache.org> on 2009/07/22 14:15:15 UTC
[jira] Closed: (CXF-2348) MessageContext properties
(HTTP_REQUEST_HEADERS & HTTP_RESPONSE_HEADERS) should not be available
during all the phases of the invocation
[ https://issues.apache.org/jira/browse/CXF-2348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guillaume Sauthier closed CXF-2348.
-----------------------------------
> MessageContext properties (HTTP_REQUEST_HEADERS & HTTP_RESPONSE_HEADERS) should not be available during all the phases of the invocation
> ----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CXF-2348
> URL: https://issues.apache.org/jira/browse/CXF-2348
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime
> Affects Versions: 2.0.11
> Environment: JOnAS 5.1.0
> Reporter: Guillaume Sauthier
> Assignee: Daniel Kulp
> Fix For: 2.0.12
>
> Attachments: cxf-tck-MessageContextProperties.patch
>
>
> The MessageContext.HTTP_REQUEST_HEADERS & MessageContext.HTTP_RESPONSE_HEADERS properties are currently available for all the phases/steps of a webservice invocation (requestor and endpoint side, inbound and outbound direction).
> They should only have a value at some well defined time:
> * HTTP_REQUEST_HEADERS should only have a value on the endpoint side with the inbound direction
> * HTTP_RESPONSE_HEADERS should only have a value on the requestor side with the outbound direction
> I'm not sure if the specification mandates that behavior, but some tests are failing because of the WrappedMessageContext heavy lifting that happened between CXF 2.0.9 and 2.0.10
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.