Date: Thu, 28 Mar 2024 08:54:32 +0000 (UTC) Message-ID: <1460125824.67179.1711616072273@cwiki-he-fi.apache.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_67178_2012026817.1711616072273" ------=_Part_67178_2012026817.1711616072273 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The NMS API (.Net Me= ssage Service API) providers a standard .NET interface to Messaging Sy= stems. There could be multiple implementations to different providers (including MSMQ). The NMS = API This allows you to build .NET applications in C#, VB, or any other .NET= language, using a single API to connect to multiple different providers us= ing a JMS style API.
NMS API currently supports all of the features of JMS in a simple pure C= # API and implementation apart from XA. Current features include
A provider implementation based on a pure C# implementation of OpenWire is provided for working with the Apache ActiveMQ br= oker. There are other provider implementations for working with Stomp, TIBCO, Microsoft Me= ssage Queue (MSMQ), and Windows Communication Foundation (WCF).
If you are curious you can browse the source code and tests for the entire project or download an NMS Provider.