Author: buildbot
Date: Fri Sep 26 16:20:39 2014
New Revision: 923709
Log:
Production update by buildbot for activemq
Modified:
websites/production/activemq/content/cache/nms.pageCache
websites/production/activemq/content/nms/index.html
websites/production/activemq/content/nms/nms-providers.html
websites/production/activemq/content/nms/nms.html
Modified: websites/production/activemq/content/cache/nms.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/activemq/content/nms/index.html
==============================================================================
--- websites/production/activemq/content/nms/index.html (original)
+++ websites/production/activemq/content/nms/index.html Fri Sep 26 16:20:39 2014
@@ -78,11 +78,7 @@
<p>The <a shape="rect" href="apachenms.html">NMS API</a> 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 using a JMS style API.</p>
-<h3 id="Index-NMSProviders">NMS Providers</h3>
-
-<p>An NMS Provider is a .NET Assembly that provides an implementation of the
NMS API that provides connectivity with a particular Messaging Service or an
implementation of a standard Messaging Protocol. Currently, the following
providers are available:</p>
-
-<ul><li><a shape="rect"
href="apachenmsactivemq.html"><strong>ActiveMQ</strong></a> client which
communicates with ActiveMQ using its own native wire protocol and provides many
<a shape="rect" href="activemq-advanced-features.html">advanced features</a>
beyond the standard NMS API.</li><li><a shape="rect"
href="apachenmsstomp.html"><strong>STOMP</strong></a> which connects to any <a
shape="rect" class="external-link" href="http://stomp.codehaus.org/";
rel="nofollow">STOMP Broker</a>.  Also, when coupled with <a shape="rect"
class="external-link" href="http://stomp.codehaus.org/StompConnect";
rel="nofollow">StompConnect</a>, NMS can be used to communicate with pretty
much any existing MOM provider! (Or at least those that support JMS which most
MOM providers do).</li><li><a shape="rect"
href="apachenmsmsmq.html"><strong>MSMQ</strong></a> is an implementation of NMS
using Microsoft's MSMQ API.</li><li><a shape="rect"
href="apachenmsems.html"><strong>EMS</strong></a> provider for ta
lking to TIBCO's EMS message broker.  To use this, you will need to
following TIBCO's licensing requirements to acquire the TIBCO client assembly
DLL.  NMS does not ship with the TIBCO client assembly.</li><li><a
shape="rect" href="apachenmswcf.html"><strong>WCF</strong></a> provides support
of Windows Communications Framework.</li></ul>
+<h3 id="Index-NMSProviders">NMS Providers</h3><p>An NMS Provider is a .NET
Assembly that provides an implementation of the NMS API that provides
connectivity with a particular Messaging Service or an implementation of a
standard Messaging Protocol. Currently, the following providers are
available:</p><ul><li><a shape="rect"
href="apachenmsactivemq.html"><strong>ActiveMQ</strong></a> client which
communicates with ActiveMQ using its own native wire protocol and provides many
<a shape="rect" href="activemq-advanced-features.html">advanced features</a>
beyond the standard NMS API.</li><li><a shape="rect"
href="apachenmsstomp.html"><strong>STOMP</strong></a> which connects to any <a
shape="rect" class="external-link" href="http://stomp.codehaus.org/";
rel="nofollow">STOMP Broker</a>.  Also, when coupled with <a shape="rect"
class="external-link" href="http://stomp.codehaus.org/StompConnect";
rel="nofollow">StompConnect</a>, NMS can be used to communicate with pretty
much any existing
MOM provider! (Or at least those that support JMS which most MOM providers
do).</li><li><a shape="rect"
href="apachenmsmsmq.html"><strong>MSMQ</strong></a> is an implementation of NMS
using Microsoft's MSMQ API.</li><li><a shape="rect"
href="apachenmsems.html"><strong>EMS</strong></a> provider for talking to
TIBCO's EMS message broker.  To use this, you will need to following
TIBCO's licensing requirements to acquire the TIBCO client assembly DLL. 
NMS does not ship with the TIBCO client assembly.</li><li><a shape="rect"
href="apachenmswcf.html"><strong>WCF</strong></a> provides support of Windows
Communications Framework.</li><li><a shape="rect"
href="apachenmsamqp.html"><strong>AMQP</strong></a> is an implementation of NMS
using the <a shape="rect" class="external-link"
href="https://qpid.apache.org/components/messaging-api/index.html";>Apache Qpid
Messaging API</a>. AMQP 1.0 protocol support is provided by <a shape="rect"
class="external-link" href="https://qpid.apache.
org/proton/index.html">Apache Qpid Proton</a>.</li></ul>
<h3 id="Index-News">News</h3>
Modified: websites/production/activemq/content/nms/nms-providers.html
==============================================================================
--- websites/production/activemq/content/nms/nms-providers.html (original)
+++ websites/production/activemq/content/nms/nms-providers.html Fri Sep 26
16:20:39 2014
@@ -72,11 +72,7 @@
<tbody>
<tr>
<td valign="top" width="100%">
-<div class="wiki-content maincontent"><h3 id="NMSProviders-NMSProviders">NMS
Providers</h3>
-
-<p>An NMS Provider is a .NET Assembly that provides an implementation of the
NMS API that provides connectivity with a particular Messaging Service or an
implementation of a standard Messaging Protocol. Currently, the following
providers are available:</p>
-
-<ul><li><a shape="rect"
href="apachenmsactivemq.html"><strong>ActiveMQ</strong></a> client which
communicates with ActiveMQ using its own native wire protocol and provides many
<a shape="rect" href="activemq-advanced-features.html">advanced features</a>
beyond the standard NMS API.</li><li><a shape="rect"
href="apachenmsstomp.html"><strong>STOMP</strong></a> which connects to any <a
shape="rect" class="external-link" href="http://stomp.codehaus.org/";
rel="nofollow">STOMP Broker</a>.  Also, when coupled with <a shape="rect"
class="external-link" href="http://stomp.codehaus.org/StompConnect";
rel="nofollow">StompConnect</a>, NMS can be used to communicate with pretty
much any existing MOM provider! (Or at least those that support JMS which most
MOM providers do).</li><li><a shape="rect"
href="apachenmsmsmq.html"><strong>MSMQ</strong></a> is an implementation of NMS
using Microsoft's MSMQ API.</li><li><a shape="rect"
href="apachenmsems.html"><strong>EMS</strong></a> provider for ta
lking to TIBCO's EMS message broker.  To use this, you will need to
following TIBCO's licensing requirements to acquire the TIBCO client assembly
DLL.  NMS does not ship with the TIBCO client assembly.</li><li><a
shape="rect" href="apachenmswcf.html"><strong>WCF</strong></a> provides support
of Windows Communications Framework.</li></ul></div>
+<div class="wiki-content maincontent"><h3 id="NMSProviders-NMSProviders">NMS
Providers</h3><p>An NMS Provider is a .NET Assembly that provides an
implementation of the NMS API that provides connectivity with a particular
Messaging Service or an implementation of a standard Messaging Protocol.
Currently, the following providers are available:</p><ul><li><a shape="rect"
href="apachenmsactivemq.html"><strong>ActiveMQ</strong></a> client which
communicates with ActiveMQ using its own native wire protocol and provides many
<a shape="rect" href="activemq-advanced-features.html">advanced features</a>
beyond the standard NMS API.</li><li><a shape="rect"
href="apachenmsstomp.html"><strong>STOMP</strong></a> which connects to any <a
shape="rect" class="external-link" href="http://stomp.codehaus.org/";
rel="nofollow">STOMP Broker</a>.  Also, when coupled with <a shape="rect"
class="external-link" href="http://stomp.codehaus.org/StompConnect";
rel="nofollow">StompConnect</a>, NMS can be used
to communicate with pretty much any existing MOM provider! (Or at least those
that support JMS which most MOM providers do).</li><li><a shape="rect"
href="apachenmsmsmq.html"><strong>MSMQ</strong></a> is an implementation of NMS
using Microsoft's MSMQ API.</li><li><a shape="rect"
href="apachenmsems.html"><strong>EMS</strong></a> provider for talking to
TIBCO's EMS message broker.  To use this, you will need to following
TIBCO's licensing requirements to acquire the TIBCO client assembly DLL. 
NMS does not ship with the TIBCO client assembly.</li><li><a shape="rect"
href="apachenmswcf.html"><strong>WCF</strong></a> provides support of Windows
Communications Framework.</li><li><a shape="rect"
href="apachenmsamqp.html"><strong>AMQP</strong></a> is an implementation of NMS
using the <a shape="rect" class="external-link"
href="https://qpid.apache.org/components/messaging-api/index.html";>Apache Qpid
Messaging API</a>. AMQP 1.0 protocol support is provided by <a shape="rect" cla
ss="external-link" href="https://qpid.apache.org/proton/index.html";>Apache
Qpid Proton</a>.</li></ul></div>
</td>
<td valign="top">
<div class="navigation">
Modified: websites/production/activemq/content/nms/nms.html
==============================================================================
--- websites/production/activemq/content/nms/nms.html (original)
+++ websites/production/activemq/content/nms/nms.html Fri Sep 26 16:20:39 2014
@@ -76,11 +76,7 @@
<p>The NMS API provides your client with a common API model for working with
Message Oriented Middleware, but to make use of the API you need to download
one of the NMS Provider libraries. The NMS Providers libraries are what makes
it possible for your code to connect to your Message Broker. Follow the links
below to read more about the <a shape="rect" href="nms-providers.html">NMS
Provider</a> for your Message broker and <a shape="rect"
href="download.html">download</a> a release bundle.</p>
-<h3 id="NMS-NMSProviders">NMS Providers</h3>
-
-<p>An NMS Provider is a .NET Assembly that provides an implementation of the
NMS API that provides connectivity with a particular Messaging Service or an
implementation of a standard Messaging Protocol. Currently, the following
providers are available:</p>
-
-<ul><li><a shape="rect"
href="apachenmsactivemq.html"><strong>ActiveMQ</strong></a> client which
communicates with ActiveMQ using its own native wire protocol and provides many
<a shape="rect" href="activemq-advanced-features.html">advanced features</a>
beyond the standard NMS API.</li><li><a shape="rect"
href="apachenmsstomp.html"><strong>STOMP</strong></a> which connects to any <a
shape="rect" class="external-link" href="http://stomp.codehaus.org/";
rel="nofollow">STOMP Broker</a>.  Also, when coupled with <a shape="rect"
class="external-link" href="http://stomp.codehaus.org/StompConnect";
rel="nofollow">StompConnect</a>, NMS can be used to communicate with pretty
much any existing MOM provider! (Or at least those that support JMS which most
MOM providers do).</li><li><a shape="rect"
href="apachenmsmsmq.html"><strong>MSMQ</strong></a> is an implementation of NMS
using Microsoft's MSMQ API.</li><li><a shape="rect"
href="apachenmsems.html"><strong>EMS</strong></a> provider for ta
lking to TIBCO's EMS message broker.  To use this, you will need to
following TIBCO's licensing requirements to acquire the TIBCO client assembly
DLL.  NMS does not ship with the TIBCO client assembly.</li><li><a
shape="rect" href="apachenmswcf.html"><strong>WCF</strong></a> provides support
of Windows Communications Framework.</li></ul>
+<h3 id="NMS-NMSProviders">NMS Providers</h3><p>An NMS Provider is a .NET
Assembly that provides an implementation of the NMS API that provides
connectivity with a particular Messaging Service or an implementation of a
standard Messaging Protocol. Currently, the following providers are
available:</p><ul><li><a shape="rect"
href="apachenmsactivemq.html"><strong>ActiveMQ</strong></a> client which
communicates with ActiveMQ using its own native wire protocol and provides many
<a shape="rect" href="activemq-advanced-features.html">advanced features</a>
beyond the standard NMS API.</li><li><a shape="rect"
href="apachenmsstomp.html"><strong>STOMP</strong></a> which connects to any <a
shape="rect" class="external-link" href="http://stomp.codehaus.org/";
rel="nofollow">STOMP Broker</a>.  Also, when coupled with <a shape="rect"
class="external-link" href="http://stomp.codehaus.org/StompConnect";
rel="nofollow">StompConnect</a>, NMS can be used to communicate with pretty
much any existing M
OM provider! (Or at least those that support JMS which most MOM providers
do).</li><li><a shape="rect"
href="apachenmsmsmq.html"><strong>MSMQ</strong></a> is an implementation of NMS
using Microsoft's MSMQ API.</li><li><a shape="rect"
href="apachenmsems.html"><strong>EMS</strong></a> provider for talking to
TIBCO's EMS message broker.  To use this, you will need to following
TIBCO's licensing requirements to acquire the TIBCO client assembly DLL. 
NMS does not ship with the TIBCO client assembly.</li><li><a shape="rect"
href="apachenmswcf.html"><strong>WCF</strong></a> provides support of Windows
Communications Framework.</li><li><a shape="rect"
href="apachenmsamqp.html"><strong>AMQP</strong></a> is an implementation of NMS
using the <a shape="rect" class="external-link"
href="https://qpid.apache.org/components/messaging-api/index.html";>Apache Qpid
Messaging API</a>. AMQP 1.0 protocol support is provided by <a shape="rect"
class="external-link" href="https://qpid.apache.or
g/proton/index.html">Apache Qpid Proton</a>.</li></ul>
<h2 id="NMS-Buildingthecode">Building the code</h2>
