[
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-24-tidy-up.patch
Patch -24 cleans up stray issues:
* warning in XML comment
* test code including common from main
* Studio 2010 test project should use Framework 4.0
* Studio 2010 test project needs to include test files
The AMQP provider has much better exposure in the test packages.
The tests run equally well against Qpidd and ActiveMQ 5.10 brokers.
> 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-21-Add-Map-Text-Message-tests.patch,
> Apache.NMS.AMQP-22-add-more-tests.patch,
> Apache.NMS.AMQP-23a-MessageDeliveryTest.cs.patch,
> Apache.NMS.AMQP-23b-MSConnectionFactoryTest.cs.patch,
> Apache.NMS.AMQP-23c-NmsConsoleTracer.cs.patch,
> Apache.NMS.AMQP-23d-addTraceStatements.patch,
> Apache.NMS.AMQP-23e-addFilesToTestProject.patch,
> Apache.NMS.AMQP-24-tidy-up.patch,
> Apache.NMS.AMQP-Add-message-cloning-19.patch,
> 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-hello-world-to-vs2008-18.patch,
> Apache.NMS.AMQP-add-message-conversions-06.patch,
> Apache.NMS.AMQP-add-message-test-20.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|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.2#6252)
