activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Gomes (JIRA)" <jira+amq...@apache.org>
Subject [jira] Commented: (AMQNET-185) Add new provider implementation for IBM WebSphere MQ (formerly MQSeries)
Date Wed, 07 Oct 2009 19:23:52 GMT

    [ https://issues.apache.org/activemq/browse/AMQNET-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=54651#action_54651
] 

Jim Gomes commented on AMQNET-185:
----------------------------------

The main NMS connection factory has support for the XMS provider.

> Add new provider implementation for IBM WebSphere MQ (formerly MQSeries)
> ------------------------------------------------------------------------
>
>                 Key: AMQNET-185
>                 URL: https://issues.apache.org/activemq/browse/AMQNET-185
>             Project: ActiveMQ .Net
>          Issue Type: New Feature
>    Affects Versions: 1.2.0
>            Reporter: Jim Gomes
>            Assignee: Jim Gomes
>            Priority: Minor
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message