Mailing-List: contact cxf-issues-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cxf-dev@incubator.apache.org
Message-ID: <6615547.1169829229167.JavaMail.jira@brutus>
Date: Fri, 26 Jan 2007 08:33:49 -0800 (PST)
From: "Gary Tully (JIRA)" <jira@apache.org>
To: cxf-issues@incubator.apache.org
Subject: [jira] Created: (CXF-393) All JMS message properties are always
 copied from source to destination
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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


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.