You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Jim Gomes (JIRA)" <ji...@apache.org> on 2016/01/08 19:52:40 UTC
[jira] [Resolved] (AMQNET-185) Add new provider implementation for
IBM WebSphere MQ (formerly MQSeries)
[ https://issues.apache.org/jira/browse/AMQNET-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jim Gomes resolved AMQNET-185.
------------------------------
Resolution: Fixed
> Add new provider implementation for IBM WebSphere MQ (formerly MQSeries)
> ------------------------------------------------------------------------
>
> Key: AMQNET-185
> URL: https://issues.apache.org/jira/browse/AMQNET-185
> Project: ActiveMQ .Net
> Issue Type: New Feature
> Components: XMS
> Affects Versions: 1.2.0
> Reporter: Jim Gomes
> Assignee: Jim Gomes
> Priority: Minor
> Fix For: 1.8.0
>
> Attachments: Apache.NMS.XMS.7z
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> An additional provider implementation for interfacing with IBM WebSphere MQ would greatly enhance the cross-broker support of NMS. This new provider implementation can be implemented in a similar fashion to the TIBCO EMS provider. The new provider should be named Apache.NMS.XMS. The IBM WebSphere MQ .NET client is informally, but commonly, referred to as XMS .NET.
> The URI prefix for the provider should be XMS: in a similar way that EMS: prefix is used for TIBCO.
> A new Component module should be added to JIRA to track this provider. The Component module should be named XMS.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)