[jira] Updated: (CXF-393) All JMS message properties are always copied from source to destination

["Gary Tully (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CXF-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Tully updated CXF-393:
---------------------------

    Attachment: cxf-393.rel.patch

this patch removes the automatic copying of JMS message string properties from request context to reply context.  JMS_SERVER_HEADERS is now replaced with JMS_SERVER_REQUEST_HEADERS. JMS_SERVER_RESPONSE_HEADERS can be modified to include properties in the reply.

> All JMS message properties are always copied from source to destination
> -----------------------------------------------------------------------
>
>                 Key: CXF-393
>                 URL: https://issues.apache.org/jira/browse/CXF-393
>             Project: CXF
>          Issue Type: Bug
>          Components: Transports
>    Affects Versions: 2.0-M1
>            Reporter: Gary Tully
>         Attachments: cxf-393.rel.patch
>
>
> Some JMS implementations are strict about the setting of properties. The properties valid on an incomming message are not valid for an outgoing message. CXF by default will copy all message properties from the input message to request headers and copy the headers to a reply. This can lead to failure to send reply messages. For example JMSX properties that indicate a message is a needs a reply have no business themselves in a reply.
> The fix would allow an exclued filter be specified on property read such that a set of known request propertys can be omitted/excluded from the headers. This could be applied on either the getter or setter. Since the setter is typically where the problem arises, limiting the JMS properties that can be set may be the best solution.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.