activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chuck Rolke (JIRA)" <>
Subject [jira] [Commented] (AMQNET-454) Add Apache Qpid provider to NMS
Date Mon, 27 Jan 2014 23:32:41 GMT


Chuck Rolke commented on AMQNET-454:

I have created a *new Apache Qpid vendor kit* and checked it in at
Pending additions to Apache.NMS.AMQP Provider using AMQP protocol version 1.0 needed updates
to the base kit for required functions.

The release is in directory and is composed of the following:

* Qpid Proton 0.6 release.
* Qpid trunk 0.27 at r1561801. The pending Qpid 0.26 release does not have Amqp 1.0 .NET features
required for NMS.
* 16097 = Today's date in unix-day counting.

There is no plan to release too my versions of this kit as it is so big. Some measures could
be taken to reduce its size since the boost libraries are repeated across versions and don't
change. For now boost is mindlessly repeated in each kit.

This kit obsoletes the kit and 16034 could be deleted from version control.


> Add Apache Qpid provider to NMS
> -------------------------------
>                 Key: AMQNET-454
>                 URL:
>             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-copyrights-conn-str-fix-09.patch,
Apache.NMS.AMQP-fix-destination-to-use-qpid-address-10.patch, Apache.NMS.AMQP-object-lifecycle-04.patch,
Apache.NMS.AMQP-provider-configs-03.patch, Apache.NMS.AMQP-qpid-object-lifecycle-02.patch,
Apache.NMS.AMQP-set-connection-credentials-08.patch, vendor-QPid-nant-01.patch
> NMS includes various providers ActiveMQ, STOMP, MSMQ, EMS, and WCF. This issue proposes
to add [Apache Qpid|] as another provider.
> Qpid has a [Messaging .NET Binding|]
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|] by including
[Qpid Proton|] 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

View raw message