activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chuck Rolke (JIRA)" <jira+amq...@apache.org>
Subject [jira] [Updated] (AMQNET-454) Add Apache Qpid provider to NMS
Date Mon, 13 Jan 2014 16:46:51 GMT

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

Chuck Rolke updated AMQNET-454:
-------------------------------

    Attachment: Apache.NMS.AMQP-connectionProperties-07.patch

Rooted at activemq-dotnet/Apache.NMS.Amqp this patch:
1. Provides a way to specify any and all Qpid connection options through the normal IConnection
factory interface.
2. Uses AMQP 1.0 connection version by default but allows users to specify AMQP 0.10 through
the connection factory or through connection properties.
3. Fixes a buglet that started connections unexpectedly during the creation of a Session.
4. Adds AmqpProvider-specific connection property accessors.


> Add Apache Qpid provider to NMS
> -------------------------------
>
>                 Key: AMQNET-454
>                 URL: https://issues.apache.org/jira/browse/AMQNET-454
>             Project: ActiveMQ .Net
>          Issue Type: New Feature
>          Components: NMS
>    Affects Versions: 1.6.0
>            Reporter: Chuck Rolke
>            Assignee: Jim Gomes
>         Attachments: Apache.NMS.AMQP-add-message-conversions-06.patch, Apache.NMS.AMQP-add-topic-05.patch,
Apache.NMS.AMQP-connectionProperties-07.patch, Apache.NMS.AMQP-object-lifecycle-04.patch,
Apache.NMS.AMQP-provider-configs-03.patch, Apache.NMS.AMQP-qpid-object-lifecycle-02.patch,
vendor-QPid-nant-01.patch
>
>
> NMS includes various providers ActiveMQ, STOMP, MSMQ, EMS, and WCF. This issue proposes
to add [Apache Qpid|http://qpid.apache.org/index.html] as another provider.
> Qpid has a [Messaging .NET Binding|http://qpid.apache.org/releases/qpid-0.24/programming/book/ch05.html]
that is layered on top of the native C++ Qpid Messaging client. The Qpid .NET binding is attractive
as the hook for tying in Qpid as an NMS provider.
> The proposed NMS provider supports [AMQP 1.0|http://qpid.apache.org/amqp.html] by including
[Qpid Proton|http://qpid.apache.org/proton/index.html] libraries.
> From a high level this addition to Active.NMS would consist of two parts
> * Add Qpid as a vendor kit. This includes both the Qpid .NET Binding and Qpid Proton
in a single kit.
> * Add the new provider with code linking NMS to Qpid



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message