activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r908251 - in /websites/production/activemq/content: cache/main.pageCache xml-configuration.html
Date Tue, 06 May 2014 21:20:37 GMT
Author: buildbot
Date: Tue May  6 21:20:37 2014
New Revision: 908251

Log:
Production update by buildbot for activemq

Modified:
    websites/production/activemq/content/cache/main.pageCache
    websites/production/activemq/content/xml-configuration.html

Modified: websites/production/activemq/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.

Modified: websites/production/activemq/content/xml-configuration.html
==============================================================================
--- websites/production/activemq/content/xml-configuration.html (original)
+++ websites/production/activemq/content/xml-configuration.html Tue May  6 21:20:37 2014
@@ -83,28 +83,14 @@
   <tbody>
         <tr>
         <td valign="top" width="100%">
-<div class="wiki-content maincontent"><p>We support an XML deployment descriptor
for configuring the ActiveMQ Message Broker. There are many things which can be configured
such as</p>
-<ul><li>transport connectors which consist of transport channels and wire formats
TODO: add a link to a page explaining what transport connectors are how to configure and use
them.</li><li>network connectors using network channels or discovery TODO: add
a link to a page explaining what network connectors are how to configure and use them.</li><li>discovery
agents TODO: add a link to a page explaining what discovery agents are how to configure and
use them.</li><li>persistence providers &amp; locations TODO: add a link to
a page explaining what persistence providers are how to configure and use them.</li><li>custom
message containers (such as last image caching etc)</li></ul>
-
-
-<p>So we decided that using XML would make this configuration much easier. From version
4.0 onwards we use <a shape="rect" class="external-link" href="http://xbean.org/" rel="nofollow">XBean</a>
to perform the XML configuration.</p>
-
-<p>For details of the XML see the <a shape="rect" href="xml-reference.html">Xml
Reference</a></p>
-    <div class="aui-message problem shadowed information-macro">
+<div class="wiki-content maincontent"><p>We support an XML deployment descriptor
for configuring the ActiveMQ Message Broker. There are many things which can be configured
such as</p><ul><li>transport connectors which consist of transport channels
and wire formats TODO: add a link to a page explaining what transport connectors are how to
configure and use them.</li><li>network connectors using network channels or discovery
TODO: add a link to a page explaining what network connectors are how to configure and use
them.</li><li>discovery agents TODO: add a link to a page explaining what discovery
agents are how to configure and use them.</li><li>persistence providers &amp;
locations TODO: add a link to a page explaining what persistence providers are how to configure
and use them.</li><li>custom message containers (such as last image caching etc)</li></ul><p>So
we decided that using XML would make this configuration much easier. From version 4.0 onwards
we use <a shape="rect" class="e
 xternal-link" href="http://xbean.org/" rel="nofollow">XBean</a> to perform the XML
configuration.</p><p>For details of the XML see the <a shape="rect" href="xml-reference.html">Xml
Reference</a></p>    <div class="aui-message problem shadowed information-macro">
                     <p class="title">Be careful with broker names and URIs</p>
                             <span class="aui-icon icon-problem">Icon</span>
                 <div class="message-content">
-                            
-<p>Make sure you do not use any strange characters in the names of brokers as they
are converted to URIs which <a shape="rect" class="external-link" href="http://java.sun.com/j2se/1.4.2/docs/api/java/net/URI.html"
rel="nofollow">do not allow things like underscores</a> in them etc.</p>
+                            <p>Make sure you do not use any strange characters in the
names of brokers as they are converted to URIs which <a shape="rect" class="external-link"
href="http://java.sun.com/j2se/1.4.2/docs/api/java/net/URI.html" rel="nofollow">do not
allow things like underscores</a> in them etc.</p>
                     </div>
     </div>
-
-
-<h2 id="XmlConfiguration-Examples">Examples</h2>
-
-<p>The default ActiveMQ configuration: <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/activemq/trunk/assembly/src/release/conf/activemq.xml">current
default config</a>.</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
+<h2 id="XmlConfiguration-Examples">Examples</h2><p>The default ActiveMQ
configuration: <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/activemq/trunk/assembly/src/release/conf/activemq.xml">current
default config</a>.</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
 <script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
 &lt;beans
   xmlns=&quot;http://www.springframework.org/schema/beans&quot;
@@ -253,69 +239,25 @@
 
 &lt;/beans&gt;
 ]]></script>
-</div></div>
-<p>From a binary distribution, from version 1.1 onwards there is an <em>activemq</em>
script allowing you to run a Message Broker as a stand alone process from the command line
easily providing the $ACTIVEMQ_HOME/bin directory is on your PATH.</p>
-
-<p><strong>AMQ 4.x</strong></p>
-
-<p>if myConfig.xml is in the classpath</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-activemq  xbean:myConfig.xml
+</div></div><p>From a binary distribution, from version 1.1 onwards there
is an <em>activemq</em> script allowing you to run a Message Broker as a stand
alone process from the command line easily providing the $ACTIVEMQ_HOME/bin directory is on
your PATH.</p><p><strong>AMQ 4.x</strong></p><p>if myConfig.xml
is in the classpath</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[activemq
 xbean:myConfig.xml
 ]]></script>
-</div></div>
-<p>or to use the file path system</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-activemq  xbean:file:../conf/myConfig.xml
+</div></div><p>or to use the file path system</p><div class="code
panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[activemq
 xbean:file:../conf/myConfig.xml
 ]]></script>
-</div></div>
-<p><strong>AMQ 3.x</strong></p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-activemq myConfig.xml
+</div></div><p><strong>AMQ 3.x</strong></p><div class="code
panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[activemq
myConfig.xml
 ]]></script>
-</div></div>
-<p>Or to use the default config file its just</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-activemq
+</div></div><p>Or to use the default config file its just</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[activemq
 ]]></script>
-</div></div>
-<p>If you have a source distribution you can run a broker using Maven specifying one
of these configuration files as follows<br clear="none">
-under the assembly module run :</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-maven server -Dconfig=xbean:file:src/release/conf/activemq.xml
+</div></div><p>If you have a source distribution you can run a broker using
Maven specifying one of these configuration files as follows<br clear="none"> under
the assembly module run :</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[maven
server -Dconfig=xbean:file:src/release/conf/activemq.xml
 ]]></script>
-</div></div>
-<p>If your <a shape="rect" href="initial-configuration.html">classpath is set
up correctly</a> you can achieve the same thing from the command line</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-java org.apache.activemq.broker.Main  xbean:file:src/release/conf/activemq.xml
+</div></div><p>If your <a shape="rect" href="initial-configuration.html">classpath
is set up correctly</a> you can achieve the same thing from the command line</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[java
org.apache.activemq.broker.Main  xbean:file:src/release/conf/activemq.xml
 ]]></script>
-</div></div>
-
-<h2 id="XmlConfiguration-Configuringembeddedbrokers">Configuring embedded brokers</h2>
-
-<p>You can also use the XML Configuration to configure <a shape="rect" href="how-do-i-embed-a-broker-inside-a-connection.html">embedded
brokers</a>. For example using the JNDI configuration mechanism you can do the following<br
clear="none">
-<a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/activemq/trunk/activemq-core/src/test/java/org/apache/activemq/config/BrokerXmlConfigFromJNDITest.java">BrokerXmlConfigFromJNDITest</a><br
clear="none">
-Or of you want to explicitly configure the embedded broker via Java code you can do the following<br
clear="none">
-<a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/activemq/trunk/assembly/src/test/java/org/apache/activemq/config/BrokerXmlConfigStartTest.java">BrokerXmlConfigStartTest</a></p>
-
-<h2 id="XmlConfiguration-UserSubmittedConfigurations">User Submitted Configurations</h2>
-
-<p>We have a page which allows users to submit details of their configurations.</p>
-<ul><li><a shape="rect" href="user-submitted-configurations.html">User
Submitted Configurations</a></li></ul>
-
-
-<h2 id="XmlConfiguration-Background">Background</h2>
-
-<p>Since ActiveMQ has so many strategy pattern plugins for transports, wire formats,
persistence and many other things, we wanted to leave the configuration format open so that
you the developer can configure and extend ActiveMQ in any direction you wish.</p>
-
-<p>So we use the <a shape="rect" class="external-link" href="http://www.springframework.org/docs/reference/beans.html#beans-basics"
rel="nofollow">Spring XML</a> configuration file format, which allows any beans /
POJOs to be wired together and configured. However often Spring's XML can be kinda verbose
at times, so we have implemented an ActiveMQ extension to the Spring XML which knows about
the common, standard ActiveMQ things you're likely to do (e.g. tags like connector, wireFormat,
serverTransport, persistence) - but at any time you can fall back to the normal Spring way
of doing things (with tags like bean, property etc).</p>
-
-<p>To see documentation of the XML file we use or to get access to the XSD/DTD see
the <a shape="rect" href="xml-reference.html">Xml Reference</a></p></div>
+</div></div><h2 id="XmlConfiguration-Configuringembeddedbrokers">Configuring
embedded brokers</h2><p>You can also use the XML Configuration to configure <a
shape="rect" href="how-do-i-embed-a-broker-inside-a-connection.html">embedded brokers</a>.
For example using the JNDI configuration mechanism you can do the following<br clear="none">
<a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/activemq/trunk/activemq-unit-tests/src/test/java/org/apache/activemq/config/BrokerXmlConfigFromJNDITest.java">BrokerXmlConfigFromJNDITest</a><br
clear="none"> Or of you want to explicitly configure the embedded broker via Java code
you can do the following<br clear="none"> <a shape="rect" class="external-link" href="https://svn.apache.org/repos/asf/activemq/trunk/assembly/src/test/java/org/apache/activemq/config/BrokerXmlConfigStartTest.java">BrokerXmlConfigStartTest</a></p><h2
id="XmlConfiguration-UserSubmittedConfigurations">User Submitted Configurations</h2><p>We
have a p
 age which allows users to submit details of their configurations.</p><ul><li><a
shape="rect" href="user-submitted-configurations.html">User Submitted Configurations</a></li></ul><h2
id="XmlConfiguration-Background">Background</h2><p>Since ActiveMQ has so many
strategy pattern plugins for transports, wire formats, persistence and many other things,
we wanted to leave the configuration format open so that you the developer can configure and
extend ActiveMQ in any direction you wish.</p><p>So we use the <a shape="rect"
class="external-link" href="http://www.springframework.org/docs/reference/beans.html#beans-basics"
rel="nofollow">Spring XML</a> configuration file format, which allows any beans /
POJOs to be wired together and configured. However often Spring's XML can be kinda verbose
at times, so we have implemented an ActiveMQ extension to the Spring XML which knows about
the common, standard ActiveMQ things you're likely to do (e.g. tags like connector, wireFormat,
serverTransport,
  persistence) - but at any time you can fall back to the normal Spring way of doing things
(with tags like bean, property etc).</p><p>To see documentation of the XML file
we use or to get access to the XSD/DTD see the <a shape="rect" href="xml-reference.html">Xml
Reference</a></p></div>
         </td>
         <td valign="top">
           <div class="navigation">



Mime
View raw message