activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <>
Subject [jira] [Commented] (AMQNET-454) Add Apache Qpid provider to NMS
Date Mon, 10 Feb 2014 20:41:21 GMT


Timothy Bish commented on AMQNET-454:

Added the file to svn.

Before a release of this could be considered in the NMS family of libraries the code requires
a fairly complete set of unit tests to show usage and validate that the client meets the basic
contract specified in the NMS API.  There are a set of tests in the NMS API package that cover
a fair bit, but for client that need more special case consideration they will need their
own tests.   A point of reference is NMS.Stomp which doesn't implement every feature of the
NMS API and therefore has it's own tests to cover the bits that it does.  

> 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-connection-property-table-17.patch, Apache.NMS.AMQP-add-hello-world-example-11.patch,
Apache.NMS.AMQP-add-hello-world-example-retry-12.patch, 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-fix-helloworld-13.patch,
Apache.NMS.AMQP-fix-list-message-body-15.patch, Apache.NMS.AMQP-fix-map-message-body-14.patch,
Apache.NMS.AMQP-fix-replyTo-and-receive-timeouts-16.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, RELEASE.txt, 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