cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <>
Subject [jira] Assigned: (CXF-2030) JMS transport is not usable with IBM MQI interface endpoints
Date Fri, 13 Feb 2009 16:14:59 GMT


Daniel Kulp reassigned CXF-2030:

    Assignee: Daniel Kulp

> JMS transport is not usable with IBM MQI interface endpoints
> ------------------------------------------------------------
>                 Key: CXF-2030
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>          Components: Transports
>    Affects Versions: 2.1.3
>            Reporter: Marat Bedretdinov
>            Assignee: Daniel Kulp
>             Fix For: 2.1.5
>         Attachments:
> Currently JMS client transport is missing "use MessageID as correlationID" capability.

> It is currently impossible to use CXF for two way exchanges with IBM MQ MQI interfaced
endpoints (native MQ apps) because native MQI messages are missing MQRFH2 header and the correlationID
is loaded into MQMD header instead. 
> The only portable way of loading correlationID into MQMD header using JMS APIs is to
form a correlationID that would comply with "A provider specific message ID" description as
per IBM doc bellow.
> So there are two ways of addressing this issue.
> 1. Provide "use Message ID as correlation ID" capability
> 2. Generate CorrelationID complaint with IBM MQI format
> 1st option would take a bit of time do implement properly, that is avoid creating/deleteing
a consumer for each potential reply. 2nd option is much easier to do.
> I'm going to attach a patch with tests for the 2nd option shortly. This fix would also
enable CXF partition a given queue into virtual message spaces with a static correlationID
and selector prefix.

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

View raw message