[
https://issues.apache.org/jira/browse/CXF-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved CXF-393.
----------------------------
Resolution: Fixed
Fix Version/s: 2.0-RC
fixed via http://svn.apache.org/viewvc?view=rev&rev=503780
> 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
> Fix For: 2.0-RC
>
> 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.
