cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CXF-3691) CXF and Tibco BW : JMS transport does not copy protocol headers in the destination message
Date Tue, 30 Aug 2011 21:45:14 GMT

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

Daniel Kulp resolved CXF-3691.
------------------------------

       Resolution: Fixed
    Fix Version/s: 2.4.3
         Assignee: Daniel Kulp

> CXF and Tibco BW : JMS transport does not copy protocol headers in the destination message
> ------------------------------------------------------------------------------------------
>
>                 Key: CXF-3691
>                 URL: https://issues.apache.org/jira/browse/CXF-3691
>             Project: CXF
>          Issue Type: Bug
>          Components: Transports
>    Affects Versions: 2.4
>         Environment: CXF 2.4 , Tibco BW 5.6
>            Reporter: Villetard
>            Assignee: Daniel Kulp
>             Fix For: 2.4.3
>
>
> An old workaround for integrating CXF and Tibco BW was using an interceptor, for setting
a property "SoapAction" (expected by Tibco BW and case-sensitive): https://issues.apache.org/jira/browse/CXF-2612
> But it doesnt work no more with CXF 2.4. The method org.apache.cxf.transport.jms.JMSUtils.buidJMSMessageFromCXF()
no more uses addProtocolHeaders(...) to build the JMS message, so the custom message properties
are not transmitted....

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message