Author: buildbot
Date: Fri Jul 10 22:24:10 2015
New Revision: 957816
Log:
Production update by buildbot for activemq
Modified:
websites/production/activemq/content/cache/cms.pageCache
websites/production/activemq/content/cache/main.pageCache
websites/production/activemq/content/cache/nms.pageCache
websites/production/activemq/content/openwire.html
websites/production/activemq/content/unix-shell-script.html
Modified: websites/production/activemq/content/cache/cms.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/activemq/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/activemq/content/cache/nms.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/activemq/content/openwire.html
==============================================================================
--- websites/production/activemq/content/openwire.html (original)
+++ websites/production/activemq/content/openwire.html Fri Jul 10 22:24:10 2015
@@ -72,26 +72,7 @@
<tbody>
<tr>
<td valign="top" width="100%">
-<div class="wiki-content maincontent"><p>OpenWire is our cross language <a
shape="rect" href="wire-protocol.html">Wire Protocol</a> to allow native access
to ActiveMQ from a number of different languages and platforms. The Java
OpenWire transport is the default transport in ActiveMQ 4.x or later. For other
languages see the following...</p>
-
-<ul><li><a shape="rect" class="external-link"
href="http://activemq.apache.org/nms/">NMS</a> for the C# API to Messaging and
the OpenWire implementation in C#</li><li><a shape="rect"
href="openwire-c-client.html">OpenWire C Client</a></li><li><a shape="rect"
href="openwire-cpp-client.html">OpenWire CPP Client</a></li></ul>
-
-
-<p><strong>Note</strong> that you can also use <a shape="rect"
href="stomp.html">Stomp</a> to access ActiveMQ from many different languages as
well as use <a shape="rect" href="how-do-i-access-activemq-from-c.html">GCJ</a>
or <a shape="rect" class="external-link"
href="http://activemq.apache.org/nms/">IKVM</a> to access the Java code for
ActiveMQ from C/C++ or .Net respectively without using OpenWire.</p>
-
-<h3 id="OpenWire-Howitworks">How it works</h3>
-
-<p>OpenWire works by code generating language specific commands and marshaling
code which understands the core OpenWire protocol. Then we can write language
specific extensions for the low level protocol to provide a nice and easy to
use client API in different languages.</p>
-
-<p>To give you an idea, <a shape="rect" class="external-link"
href="https://svn.apache.org/repos/asf/activemq/trunk/activemq-openwire-generator/src/main/java/org/apache/activemq/openwire/tool/">here</a>
are the Java classes which code generate the C#, Java, C, and CPP client
code.</p>
-
-<p>Since OpenWire automates the creation of language specific <a shape="rect"
href="wire-protocol.html">Wire Protocol</a> implementations; then its a matter
of wrapping the language specific TCP/IP socket code and wrapping the API in
some easy to use functions/classes.</p>
-
-<h3 id="OpenWire-Specification">Specification</h3>
-
-<p>For a detailed specification of what you will see on the wire:</p>
-
-<ul><li><a shape="rect" href="openwire-version-2-specification.html">OpenWire
Version 2 Specification</a></li></ul></div>
+<div class="wiki-content maincontent"><p>OpenWire is our cross language <a
shape="rect" href="wire-protocol.html">Wire Protocol</a> to allow native access
to ActiveMQ from a number of different languages and platforms. The Java
OpenWire transport is the default transport in ActiveMQ 4.x or later. For other
languages see the following...</p><ul><li class="confluence-link"><a
shape="rect" class="external-link"
href="http://activemq.apache.org/nms/">NMS</a> for the C# API to Messaging and
the OpenWire implementation in C#</li><li class="confluence-link"><a
shape="rect" href="cms/index.html">CMS</a> for the C++ API to Messaging and the
OpenWire implementation in C++</li></ul><p><strong>Note</strong> that you can
also use <a shape="rect" href="stomp.html">Stomp</a> to access ActiveMQ from
many different languages as well as use <a shape="rect"
href="how-do-i-access-activemq-from-c.html">GCJ</a> or <a shape="rect"
class="external-link" href="http://activemq.apache.org/nms/">IKVM</a> to ac
cess the Java code for ActiveMQ from C/C++ or .Net respectively without using
OpenWire.</p><h3 id="OpenWire-Howitworks">How it works</h3><p>OpenWire works by
code generating language specific commands and marshaling code which
understands the core OpenWire protocol. Then we can write language specific
extensions for the low level protocol to provide a nice and easy to use client
API in different languages.</p><p>To give you an idea, <a shape="rect"
class="external-link"
href="https://svn.apache.org/repos/asf/activemq/trunk/activemq-openwire-generator/src/main/java/org/apache/activemq/openwire/tool/">here</a>
are the Java classes which code generate the C#, Java, C, and CPP client
code.</p><p>Since OpenWire automates the creation of language specific <a
shape="rect" href="wire-protocol.html">Wire Protocol</a> implementations; then
its a matter of wrapping the language specific TCP/IP socket code and wrapping
the API in some easy to use functions/classes.</p><h3 id="OpenWire-Specifica
tion">Specification</h3><p>For a detailed specification of what you will see
on the wire:</p><ul><li><a shape="rect"
href="openwire-version-2-specification.html">OpenWire Version 2
Specification</a></li></ul></div>
</td>
<td valign="top">
<div class="navigation">
Modified: websites/production/activemq/content/unix-shell-script.html
==============================================================================
--- websites/production/activemq/content/unix-shell-script.html (original)
+++ websites/production/activemq/content/unix-shell-script.html Fri Jul 10
22:24:10 2015
@@ -82,12 +82,12 @@
<tbody>
<tr>
<td valign="top" width="100%">
-<div class="wiki-content maincontent"><h2
id="UnixShellScript-/*<![CDATA[*/div.rbtoc1436552408376{padding:0px;}div.rbtoc1436552408376ul{list-style:disc;margin-left:0px;}div.rbtoc1436552408376li{margin-left:0px;padding-left:0px;}/*]]>*/#UnixShellScript-Functionaloverview#UnixShellScript-Functionalover"><style
type="text/css">/*<![CDATA[*/
-div.rbtoc1436552408376 {padding: 0px;}
-div.rbtoc1436552408376 ul {list-style: disc;margin-left: 0px;}
-div.rbtoc1436552408376 li {margin-left: 0px;padding-left: 0px;}
+<div class="wiki-content maincontent"><h2
id="UnixShellScript-/*<![CDATA[*/div.rbtoc1436566815461{padding:0px;}div.rbtoc1436566815461ul{list-style:disc;margin-left:0px;}div.rbtoc1436566815461li{margin-left:0px;padding-left:0px;}/*]]>*/#UnixShellScript-Functionaloverview#UnixShellScript-Functionalover"><style
type="text/css">/*<![CDATA[*/
+div.rbtoc1436566815461 {padding: 0px;}
+div.rbtoc1436566815461 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1436566815461 li {margin-left: 0px;padding-left: 0px;}
-/*]]>*/</style></h2><div class="toc-macro rbtoc1436552408376">
+/*]]>*/</style></h2><div class="toc-macro rbtoc1436566815461">
<ul class="toc-indentation"><li><a shape="rect"
href="#UnixShellScript-"></a></li></ul>
<ul><li><a shape="rect" href="#UnixShellScript-Functionaloverview">Functional
overview</a></li><li><a shape="rect"
href="#UnixShellScript-Configuringtheinit-script">Configuring the
init-script</a>
<ul class="toc-indentation"><li><a shape="rect"
href="#UnixShellScript-Version5.11.0andhigher">Version 5.11.0 and higher</a>