[hornetq-commits] JBoss hornetq SVN: r7857 - in trunk/docs/user-manual: en and 1 other directory.
do-not-reply at jboss.org
do-not-reply at jboss.org
Fri Aug 21 05:38:08 EDT 2009
Author: jmesnil
Date: 2009-08-21 05:38:07 -0400 (Fri, 21 Aug 2009)
New Revision: 7857
Modified:
trunk/docs/user-manual/build.xml
trunk/docs/user-manual/en/appserver-integration.xml
trunk/docs/user-manual/en/architecture.xml
trunk/docs/user-manual/en/client-classpath.xml
trunk/docs/user-manual/en/client-reconnection.xml
trunk/docs/user-manual/en/clusters.xml
trunk/docs/user-manual/en/command-buffering.xml
trunk/docs/user-manual/en/configuration-index.xml
trunk/docs/user-manual/en/configuring-transports.xml
trunk/docs/user-manual/en/connection-ttl.xml
trunk/docs/user-manual/en/core-bridges.xml
trunk/docs/user-manual/en/diverts.xml
trunk/docs/user-manual/en/duplicate-detection.xml
trunk/docs/user-manual/en/embedding-hornetq.xml
trunk/docs/user-manual/en/examples.xml
trunk/docs/user-manual/en/filter-expressions.xml
trunk/docs/user-manual/en/flow-control.xml
trunk/docs/user-manual/en/ha.xml
trunk/docs/user-manual/en/intercepting-operations.xml
trunk/docs/user-manual/en/interoperability.xml
trunk/docs/user-manual/en/jms-core-mapping.xml
trunk/docs/user-manual/en/large-messages.xml
trunk/docs/user-manual/en/last-value-queues.xml
trunk/docs/user-manual/en/libaio.xml
trunk/docs/user-manual/en/logging.xml
trunk/docs/user-manual/en/management.xml
trunk/docs/user-manual/en/master.xml
trunk/docs/user-manual/en/message-expiry.xml
trunk/docs/user-manual/en/message-grouping.xml
trunk/docs/user-manual/en/messaging-concepts.xml
trunk/docs/user-manual/en/paging.xml
trunk/docs/user-manual/en/perf-tuning.xml
trunk/docs/user-manual/en/persistence.xml
trunk/docs/user-manual/en/pre-acknowledge.xml
trunk/docs/user-manual/en/preface.xml
trunk/docs/user-manual/en/project-info.xml
trunk/docs/user-manual/en/queue-attributes.xml
trunk/docs/user-manual/en/scheduled-messages.xml
trunk/docs/user-manual/en/security.xml
trunk/docs/user-manual/en/send-guarantees.xml
trunk/docs/user-manual/en/thread-pooling.xml
trunk/docs/user-manual/en/transaction-config.xml
trunk/docs/user-manual/en/undelivered-messages.xml
trunk/docs/user-manual/en/using-core.xml
trunk/docs/user-manual/en/using-jms.xml
trunk/docs/user-manual/en/using-server.xml
trunk/docs/user-manual/en/wildcard-routing.xml
trunk/docs/user-manual/en/wildcard-syntax.xml
Log:
update user manual
* added CC licence header to source + in the book's legal notice
* added image to the cover (works only with PDF though...)
* fixed remaining references to JBoss Messaging / JBM
Modified: trunk/docs/user-manual/build.xml
===================================================================
--- trunk/docs/user-manual/build.xml 2009-08-21 09:35:43 UTC (rev 7856)
+++ trunk/docs/user-manual/build.xml 2009-08-21 09:38:07 UTC (rev 7857)
@@ -1,4 +1,4 @@
-<project name="hornetq.user-manual" default="all" basedir=".">
+<project name="HornetQ User Manual" default="all" basedir=".">
<property name="build.dir" value="build"/>
<property name="pdf.name" value="HornetQ_UserManual.pdf"/>
Modified: trunk/docs/user-manual/en/appserver-integration.xml
===================================================================
--- trunk/docs/user-manual/en/appserver-integration.xml 2009-08-21 09:35:43 UTC (rev 7856)
+++ trunk/docs/user-manual/en/appserver-integration.xml 2009-08-21 09:38:07 UTC (rev 7857)
@@ -1,23 +1,44 @@
<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ============================================================================= -->
+<!-- Copyright © 2009 Red Hat, Inc. and others. -->
+<!-- -->
+<!-- The text of and illustrations in this document are licensed by Red Hat under -->
+<!-- a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). -->
+<!-- -->
+<!-- An explanation of CC-BY-SA is available at -->
+<!-- -->
+<!-- http://creativecommons.org/licenses/by-sa/3.0/. -->
+<!-- -->
+<!-- In accordance with CC-BY-SA, if you distribute this document or an adaptation -->
+<!-- of it, you must provide the URL for the original version. -->
+<!-- -->
+<!-- Red Hat, as the licensor of this document, waives the right to enforce, -->
+<!-- and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent -->
+<!-- permitted by applicable law. -->
+<!-- ============================================================================= -->
+
<chapter id="appserver-integration">
<title>Application Server Integration and Java EE</title>
- <para>HornetQ can be easily installed in JBoss Application Server 5.1 or later. For details on
- installing HornetQ in the JBoss Application Server refer to quick-start guide.</para>
- <para>Since HornetQ also provides a JCA adaptor, it should also be possible to integrate HornetQ
- as a JMS provider in other JEE compliant app servers. For instructions on how to integrate a
- remote JCA adaptor into another application sever, please consult that application server's
- instructions.</para>
+ <para>HornetQ can be easily installed in JBoss Application Server 5.1 or later. For
+ details on installing HornetQ in the JBoss Application Server refer to quick-start
+ guide.</para>
+ <para>Since HornetQ also provides a JCA adaptor, it should also be possible to integrate
+ HornetQ as a JMS provider in other JEE compliant app servers. For instructions on
+ how to integrate a remote JCA adaptor into another application sever, please consult that
+ application server's instructions.</para>
<para>A JCA Adapter basically controls the incoming of messages to Message Driven Beans and the
outgoing of messages from other JEE components.</para>
<para>This section explains the basics behind configuring the different JEE components in the
AS.</para>
<section>
<title>Configuring Message Driven Beans</title>
- <para>The delivery of messages to an MDB using HornetQ is configured on the JCA Adapter via
- a configuration file <literal>ra.xml</literal> which can be found under in the <literal
- >jms-ra.rar</literal> archive of directory. By default this is configured to consume
- messages using an InVM connector from the instance of HornetQ running within the
- application server. A full list of what is configurable is found later in this chapter. </para>
+ <para>The delivery of messages to an MDB using HornetQ is configured on the JCA
+ Adapter via a configuration file <literal>ra.xml</literal> which can be found under in
+ the <literal>jms-ra.rar</literal> archive of directory. By default this is configured to
+ consume messages using an InVM connector from the instance of HornetQ running
+ within the application server. A full list of what is configurable is found later in
+ this chapter. </para>
<para>All MDB's however need to have the destination type and the destination configured.
The following example shows how this can be done via annotations.</para>
<programlisting>@MessageDriven(name = "MDBExample",
@@ -38,7 +59,7 @@
<para>When an MDB is using Container Managed Transactions, the delivery of the message
is done within the scope of an XA transaction. The commit or rollback of this
transaction is controlled by the container itself. If the transaction is rolled back
- then the HornetQ Message delivery semantics will kick in (by default this is to try
+ then the message delivery semantics will kick in (by default this is to try
and redeliver the message up to 10 times before sending to a DLQ). Using annotations
this would be configured as follows:</para>
<programlisting>@MessageDriven(name = "MDB_CMP_TxRequiredExample",
@@ -541,7 +562,7 @@
factories that are used by Java EE components. These Connection Factories can be
defined inside a configuration file that matches the name <literal
>*-ds.xml</literal>. You'll find a default <literal>jms-ds.xml</literal>
- configuration under the <literal>hornetq.sar</literal> directory in the JBoss AS
+ configuration under the <literal>messaging.sar</literal> directory in the Jboss AS
deployment. The connection factories defined in the config file inherit their
properties from the main <literal>ra.xml</literal> configuration but can also be
overridden, the following example show how to define one.</para>
@@ -549,7 +570,7 @@
adapter in the JBoss Application Server. If you are using another JEE application
server please refer to your application servers documentation for how to do
this.</para>
- <programlisting><![CDATA[<tx-connection-factory>
+ <programlisting><tx-connection-factory>
<jndi-name>RemoteJmsXA</jndi-name>
<xa-transaction/>
<rar-name>jms-ra.rar</rar-name>
@@ -563,7 +584,7 @@
<config-property name="ConnectionParameters" type="String">
hornetq.remoting.netty.port=5445</config-property>
<max-pool-size>20</max-pool-size>
-</tx-connection-factory>]]></programlisting>
+</tx-connection-factory></programlisting>
<para>In this example the connection factory will be bound to JNDI with the name
<literal>RemoteJmsXA</literal> and can be looked up in the usual way using JNDI
or defined within the EJB or MDB as such:</para>
@@ -614,13 +635,13 @@
<para>A bridge is deployed inside a JBoss AS instance. The instance can be the same instance
as either the source or target server. Or could be on a third, separate JBoss AS
instance.</para>
- <para>The bridge can also be used to bridge messages from other non HornetQ JMS servers, as
- long as they are JMS 1.1 compliant.<note>
+ <para>The bridge can also be used to bridge messages from other non HornetQ JMS
+ servers, as long as they are JMS 1.1 compliant.<note>
<para>Don't confuse a JMS bridge with a core bridge. A JMS bridge can be used to
bridge any two JMS 1.1 compliant JMS providers and uses the JMS API. A core
bridge (described in <xref linkend="core-bridges"/>) is used to bridge any two
- HornetQ instances and uses the core API. Always use a core bridge if you can in
- preference to a JMS bridge. The core bridge will typically provide better
+ HornetQ instances and uses the core API. Always use a core bridge if you
+ can in preference to a JMS bridge. The core bridge will typically provide better
performance than a JMS bridge. Also the core bridge can provide <emphasis>once
and only once</emphasis> delivery guarantees without using XA.</para>
</note></para>
@@ -913,7 +934,8 @@
<para>The source and target connection factory factories are used to create the
connection factory used to create the connection for the source or target
server.</para>
- <para>The configuration example above uses the default implementation provided by HornetQ that looks up the connection factory using JNDI. For other Application
+ <para>The configuration example above uses the default implementation provided by HornetQ
+ that looks up the connection factory using JNDI. For other Application
Servers or JMS providers a new implementation may have to be provided. This can
easily be done by implementing the interface <literal
>org.hornetq.jms.bridge.ConnectionFactoryFactory</literal>.</para>
@@ -921,7 +943,8 @@
<section>
<title>Source and Target Destination Factories</title>
<para>Again, similarly, these are used to create or lookup up the destinations.</para>
- <para>In the configuration example above, we have used the default provided by HornetQ that looks up the destination using JNDI.</para>
+ <para>In the configuration example above, we have used the default provided by HornetQ
+ that looks up the destination using JNDI.</para>
<para>A new implementation can be provided by implementing <literal
>org.hornetq.jms.bridge.DestinationFactory</literal> interface.</para>
</section>
@@ -952,8 +975,8 @@
<title>ONCE_AND_ONLY_ONCE</title>
<para>This QoS mode ensures messages will reach the destination from the source once
and only once. (Sometimes this mode is known as "exactly once"). If both the
- source and the destination are on the same HornetQ server instance then this can
- be achieved by sending and acknowledging the messages in the same local
+ source and the destination are on the same HornetQ server instance then
+ this can be achieved by sending and acknowledging the messages in the same local
transaction. If the source and destination are on different servers this is
achieved by enlisting the sending and consuming sessions in a JTA transaction.
The JTA transaction is controlled by JBoss Transactions JTA * implementation
@@ -991,32 +1014,33 @@
or lose network connectivity. For more information on XA Recovery,please refer to <ulink
url="http://www.jboss.org/community/wiki/JBossTransactions">JBoss
Transactions</ulink>.</para>
- <para>When HornetQ is integrated with JBoss AS, it can take advantage of JBoss Transactions
- to provide recovery of messaging resources. If messages are involved in a XA
- transaction, in the event of a server crash, the recovery manager will ensure that the
- transactions are recovered and the messages will either be committed or rolled back
+ <para>When HornetQ is integrated with JBoss AS, it can take advantage of JBoss
+ Transactions to provide recovery of messaging resources. If messages are involved in a
+ XA transaction, in the event of a server crash, the recovery manager will ensure that
+ the transactions are recovered and the messages will either be committed or rolled back
(depending on the transaction outcome) when the server is restarted.</para>
<section>
<title>XA Recovery Configuration</title>
- <para>To enable HornetQs XA Recovery, the Recovery Manager must be configured to connect
- to HornetQ to recover its resources. The following property must be added to the
- <literal>jta</literal> section of <literal>conf/jbossts-properties.xml</literal>
- of JBoss AS profiles:</para>
+ <para>To enable HornetQs XA Recovery, the Recovery Manager must be configured to
+ connect to HornetQ to recover its resources. The following property must be
+ added to the <literal>jta</literal> section of <literal
+ >conf/jbossts-properties.xml</literal> of JBoss AS profiles:</para>
<programlisting>
<properties depends="arjuna" name="jta">
...
- <property name="com.arjuna.ats.jta.recovery.XAResourceRecovery.HORNETQ1"
+ <property name="com.arjuna.ats.jta.recovery.XAResourceRecovery.HornetQ1"
value="org.hornetq.jms.server.recovery.HornetQXAResourceRecovery;[connection configuration]"/>
</properties>
</programlisting>
<para>The <literal>[connection configuration]</literal> contains all the information
- required to connect to HornetQ node under the form <literal>[connector factory class
- name],[user name], [password], [connector parameters]</literal>. </para>
+ required to connect to HornetQ node under the form <literal>[connector
+ factory class name],[user name], [password], [connector parameters]</literal>. </para>
<itemizedlist>
<listitem>
<para><literal>[connector factory class name]</literal> corresponds to the name
- of the <literal>ConnectorFactory</literal> used to connect to HornetQ. Values can be <literal
+ of the <literal>ConnectorFactory</literal> used to connect to HornetQ.
+ Values can be <literal
>org.hornetq.core.remoting.impl.invm.InVMConnectorFactory</literal> or
<literal
>org.hornetq.integration.transports.netty.NettyConnectorFactory</literal></para>
@@ -1077,8 +1101,9 @@
<property name="com.arjuna.ats.jta.recovery.XAResourceRecovery.HORNETQ1"
value="org.hornetq.jms.server.recovery.HornetQXAResourceRecovery;org.hornetq.integration.transports.netty.NettyConnectorFactory, admin, adminpass, hornetq.remoting.netty.port=8888"/>
</programlisting>
- <para>Configuring HornetQ with an invm acceptor and configuring the Recovery Manager
- with an invm connector is the recommended way to enable XA Recovery.</para>
+ <para>Configuring HornetQ with an invm acceptor and configuring the Recovery
+ Manager with an invm connector is the recommended way to enable XA
+ Recovery.</para>
</section>
</section>
<section>
Modified: trunk/docs/user-manual/en/architecture.xml
===================================================================
--- trunk/docs/user-manual/en/architecture.xml 2009-08-21 09:35:43 UTC (rev 7856)
+++ trunk/docs/user-manual/en/architecture.xml 2009-08-21 09:38:07 UTC (rev 7857)
@@ -1,4 +1,23 @@
<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ============================================================================= -->
+<!-- Copyright © 2009 Red Hat, Inc. and others. -->
+<!-- -->
+<!-- The text of and illustrations in this document are licensed by Red Hat under -->
+<!-- a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). -->
+<!-- -->
+<!-- An explanation of CC-BY-SA is available at -->
+<!-- -->
+<!-- http://creativecommons.org/licenses/by-sa/3.0/. -->
+<!-- -->
+<!-- In accordance with CC-BY-SA, if you distribute this document or an adaptation -->
+<!-- of it, you must provide the URL for the original version. -->
+<!-- -->
+<!-- Red Hat, as the licensor of this document, waives the right to enforce, -->
+<!-- and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent -->
+<!-- permitted by applicable law. -->
+<!-- ============================================================================= -->
+
<chapter id="architecture">
<title>Architecture</title>
<para>In this section we will give an overview of the HornetQ high level
Modified: trunk/docs/user-manual/en/client-classpath.xml
===================================================================
--- trunk/docs/user-manual/en/client-classpath.xml 2009-08-21 09:35:43 UTC (rev 7856)
+++ trunk/docs/user-manual/en/client-classpath.xml 2009-08-21 09:38:07 UTC (rev 7857)
@@ -1,4 +1,23 @@
<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ============================================================================= -->
+<!-- Copyright © 2009 Red Hat, Inc. and others. -->
+<!-- -->
+<!-- The text of and illustrations in this document are licensed by Red Hat under -->
+<!-- a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). -->
+<!-- -->
+<!-- An explanation of CC-BY-SA is available at -->
+<!-- -->
+<!-- http://creativecommons.org/licenses/by-sa/3.0/. -->
+<!-- -->
+<!-- In accordance with CC-BY-SA, if you distribute this document or an adaptation -->
+<!-- of it, you must provide the URL for the original version. -->
+<!-- -->
+<!-- Red Hat, as the licensor of this document, waives the right to enforce, -->
+<!-- and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent -->
+<!-- permitted by applicable law. -->
+<!-- ============================================================================= -->
+
<chapter id="client-classpath">
<title>The Client Classpath</title>
<para>In this chapter we explain which jars you need on the Java classpath of a HornetQ
@@ -30,7 +49,8 @@
</section>
<section>
<title>JNDI</title>
- <para>If you're looking up JNDI objects from the JNDI server co-located with the HornetQ standalone server you'll also need the jar <literal>jnp-client.jar</literal>
+ <para>If you're looking up JNDI objects from the JNDI server co-located with the HornetQ
+ standalone server you'll also need the jar <literal>jnp-client.jar</literal>
jar on your client classpath as well as any other jars mentioned previously.</para>
</section>
</chapter>
Modified: trunk/docs/user-manual/en/client-reconnection.xml
===================================================================
--- trunk/docs/user-manual/en/client-reconnection.xml 2009-08-21 09:35:43 UTC (rev 7856)
+++ trunk/docs/user-manual/en/client-reconnection.xml 2009-08-21 09:38:07 UTC (rev 7857)
@@ -1,4 +1,23 @@
<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ============================================================================= -->
+<!-- Copyright © 2009 Red Hat, Inc. and others. -->
+<!-- -->
+<!-- The text of and illustrations in this document are licensed by Red Hat under -->
+<!-- a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). -->
+<!-- -->
+<!-- An explanation of CC-BY-SA is available at -->
+<!-- -->
+<!-- http://creativecommons.org/licenses/by-sa/3.0/. -->
+<!-- -->
+<!-- In accordance with CC-BY-SA, if you distribute this document or an adaptation -->
+<!-- of it, you must provide the URL for the original version. -->
+<!-- -->
+<!-- Red Hat, as the licensor of this document, waives the right to enforce, -->
+<!-- and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent -->
+<!-- permitted by applicable law. -->
+<!-- ============================================================================= -->
+
<chapter id="client-reconnection">
<title>Client Reconnection</title>
<para>HornetQ clients can be configured to automatically reconnect to the server in the
Modified: trunk/docs/user-manual/en/clusters.xml
===================================================================
--- trunk/docs/user-manual/en/clusters.xml 2009-08-21 09:35:43 UTC (rev 7856)
+++ trunk/docs/user-manual/en/clusters.xml 2009-08-21 09:38:07 UTC (rev 7857)
@@ -1,4 +1,23 @@
<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ============================================================================= -->
+<!-- Copyright © 2009 Red Hat, Inc. and others. -->
+<!-- -->
+<!-- The text of and illustrations in this document are licensed by Red Hat under -->
+<!-- a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). -->
+<!-- -->
+<!-- An explanation of CC-BY-SA is available at -->
+<!-- -->
+<!-- http://creativecommons.org/licenses/by-sa/3.0/. -->
+<!-- -->
+<!-- In accordance with CC-BY-SA, if you distribute this document or an adaptation -->
+<!-- of it, you must provide the URL for the original version. -->
+<!-- -->
+<!-- Red Hat, as the licensor of this document, waives the right to enforce, -->
+<!-- and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent -->
+<!-- permitted by applicable law. -->
+<!-- ============================================================================= -->
+
<chapter id="clusters">
<title>Clusters</title>
<section>
@@ -21,7 +40,8 @@
<para>Nodes can be connected together to form a cluster in many different topologies, we
will discuss a couple of the more common topologies later in this chapter.</para>
<para>We'll also discuss client side load balancing, where we can balance client connections
- across the nodes of the cluster, and we'll consider message redistribution where HornetQ will redistribute messages between nodes to avoid starvation.</para>
+ across the nodes of the cluster, and we'll consider message redistribution where HornetQ
+ will redistribute messages between nodes to avoid starvation.</para>
<para>Another important part of clustering is <emphasis>server discovery</emphasis> where
servers can broadcast their connection details so clients or other servers can connect
to them with the minimum of configuration.</para>
@@ -59,7 +79,8 @@
connection settings for a live and (optional) backup server and broadcasts them on
the network. It also defines the UDP address and port settings. </para>
<para>Broadcast groups are defined in the server configuration file <literal
- >hornetq-configuration.xml</literal>. There can be many broadcast groups per HornetQ server. All broadcast groups must be defined in a <literal
+ >hornetq-configuration.xml</literal>. There can be many broadcast groups per HornetQ
+ server. All broadcast groups must be defined in a <literal
>broadcast-groups</literal> element.</para>
<para>Let's take a look at an example broadcast group from <literal
>hornetq-configuration.xml</literal>:</para>
@@ -403,7 +424,8 @@
connections created using a single factory can be made to different nodes of the
cluster. This allows connections to spread smoothly across the nodes of a cluster and
not be "clumped" on any particular node.</para>
- <para>The load balancing policy to be used by the client factory is configurable. HornetQ provides two out-of-the-box load balancing policies and you can also implement
+ <para>The load balancing policy to be used by the client factory is configurable. HornetQ
+ provides two out-of-the-box load balancing policies and you can also implement
your own and use that.</para>
<para>The out-of-the-box policies are</para>
<itemizedlist>
@@ -599,7 +621,8 @@
it doesn't solve: What happens if the consumers on a queue close after the messages have
been sent to the node? If there are no consumers on the queue the message won't get
consumed and we have a <emphasis>starvation</emphasis> situation.</para>
- <para>This is where message redistribution comes in. With message redistribution HornetQ can be configured to automatically <emphasis>redistribute</emphasis> messages
+ <para>This is where message redistribution comes in. With message redistribution HornetQ
+ can be configured to automatically <emphasis>redistribute</emphasis> messages
from queues which have no consumers back to other nodes in the cluster which do have
matching consumers.</para>
<para>Message redistribution can be configured to kick in immediately after the last
Modified: trunk/docs/user-manual/en/command-buffering.xml
===================================================================
--- trunk/docs/user-manual/en/command-buffering.xml 2009-08-21 09:35:43 UTC (rev 7856)
+++ trunk/docs/user-manual/en/command-buffering.xml 2009-08-21 09:38:07 UTC (rev 7857)
@@ -1,4 +1,23 @@
<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ============================================================================= -->
+<!-- Copyright © 2009 Red Hat, Inc. and others. -->
+<!-- -->
+<!-- The text of and illustrations in this document are licensed by Red Hat under -->
+<!-- a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). -->
+<!-- -->
+<!-- An explanation of CC-BY-SA is available at -->
+<!-- -->
+<!-- http://creativecommons.org/licenses/by-sa/3.0/. -->
+<!-- -->
+<!-- In accordance with CC-BY-SA, if you distribute this document or an adaptation -->
+<!-- of it, you must provide the URL for the original version. -->
+<!-- -->
+<!-- Red Hat, as the licensor of this document, waives the right to enforce, -->
+<!-- and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent -->
+<!-- permitted by applicable law. -->
+<!-- ============================================================================= -->
+
<chapter id="command-buffering">
<title>Command Buffering</title>
<para>As HornetQ clients send commands to their servers they store each sent command in
Modified: trunk/docs/user-manual/en/configuration-index.xml
===================================================================
--- trunk/docs/user-manual/en/configuration-index.xml 2009-08-21 09:35:43 UTC (rev 7856)
+++ trunk/docs/user-manual/en/configuration-index.xml 2009-08-21 09:38:07 UTC (rev 7857)
@@ -1,4 +1,23 @@
<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ============================================================================= -->
+<!-- Copyright © 2009 Red Hat, Inc. and others. -->
+<!-- -->
+<!-- The text of and illustrations in this document are licensed by Red Hat under -->
+<!-- a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). -->
+<!-- -->
+<!-- An explanation of CC-BY-SA is available at -->
+<!-- -->
+<!-- http://creativecommons.org/licenses/by-sa/3.0/. -->
+<!-- -->
+<!-- In accordance with CC-BY-SA, if you distribute this document or an adaptation -->
+<!-- of it, you must provide the URL for the original version. -->
+<!-- -->
+<!-- Red Hat, as the licensor of this document, waives the right to enforce, -->
+<!-- and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent -->
+<!-- permitted by applicable law. -->
+<!-- ============================================================================= -->
+
<chapter id="configuration-index">
<title>Configuration Reference</title>
<para>This section is a quick index for looking up configuration. Click on the element name to
Modified: trunk/docs/user-manual/en/configuring-transports.xml
===================================================================
--- trunk/docs/user-manual/en/configuring-transports.xml 2009-08-21 09:35:43 UTC (rev 7856)
+++ trunk/docs/user-manual/en/configuring-transports.xml 2009-08-21 09:38:07 UTC (rev 7857)
@@ -1,4 +1,23 @@
<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ============================================================================= -->
+<!-- Copyright © 2009 Red Hat, Inc. and others. -->
+<!-- -->
+<!-- The text of and illustrations in this document are licensed by Red Hat under -->
+<!-- a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). -->
+<!-- -->
+<!-- An explanation of CC-BY-SA is available at -->
+<!-- -->
+<!-- http://creativecommons.org/licenses/by-sa/3.0/. -->
+<!-- -->
+<!-- In accordance with CC-BY-SA, if you distribute this document or an adaptation -->
+<!-- of it, you must provide the URL for the original version. -->
+<!-- -->
+<!-- Red Hat, as the licensor of this document, waives the right to enforce, -->
+<!-- and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent -->
+<!-- permitted by applicable law. -->
+<!-- ============================================================================= -->
+
<chapter id="configuring-transports">
<title>Configuring the Transport</title>
<para>HornetQ has a fully pluggable and highly flexible transport layer and defines its
@@ -297,7 +316,8 @@
<title>Configuring Netty Servlet</title>
<para>We also provide a Netty servlet transport for use with HornetQ. The
servlet transport allows HornetQ traffic to be tunneled over HTTP to a
- servlet running in a servlet engine which then redirects it to an in-VM HornetQ server.</para>
+ servlet running in a servlet engine which then redirects it to an in-VM HornetQ
+ server.</para>
<para>The servlet transport differs from the Netty HTTP transport in that, with the HTTP
transport HornetQ effectively acts a web server listening for HTTP traffic
on, e.g. port 80 or 8080, whereas with the servlet transport HornetQ traffic is proxied
@@ -395,7 +415,7 @@
<param key="hornetq.remoting.netty.servletpath" value="/messaging/HornetQServlet" type="String"/>
<param key="hornetq.remoting.netty.sslenabled" value="true" type="Boolean"/>
<param key="hornetq.remoting.netty.keystorepath" value="path to a keystoree" type="String"/>
- <param key="hornetq.remoting.netty.keystorepassword" value="keysore password" type="String"/>
+ <param key="hornetq.remoting.netty.keystorepassword" value="keystore password" type="String"/>
</connector>
</programlisting></para>
<para>You will also have to configure the Application server to use a KeyStore. Edit the
Modified: trunk/docs/user-manual/en/connection-ttl.xml
===================================================================
--- trunk/docs/user-manual/en/connection-ttl.xml 2009-08-21 09:35:43 UTC (rev 7856)
+++ trunk/docs/user-manual/en/connection-ttl.xml 2009-08-21 09:38:07 UTC (rev 7857)
@@ -1,7 +1,27 @@
<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ============================================================================= -->
+<!-- Copyright © 2009 Red Hat, Inc. and others. -->
+<!-- -->
+<!-- The text of and illustrations in this document are licensed by Red Hat under -->
+<!-- a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). -->
+<!-- -->
+<!-- An explanation of CC-BY-SA is available at -->
+<!-- -->
+<!-- http://creativecommons.org/licenses/by-sa/3.0/. -->
+<!-- -->
+<!-- In accordance with CC-BY-SA, if you distribute this document or an adaptation -->
+<!-- of it, you must provide the URL for the original version. -->
+<!-- -->
+<!-- Red Hat, as the licensor of this document, waives the right to enforce, -->
+<!-- and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent -->
+<!-- permitted by applicable law. -->
+<!-- ============================================================================= -->
+
<chapter id="connection-ttl">
<title>Dead Connections and Session Multiplexing</title>
- <para>In this section we will discuss connection time-to-live (TTL) and explain how HornetQ deals with crashed clients and clients which have exited without cleanly closing
+ <para>In this section we will discuss connection time-to-live (TTL) and explain how HornetQ
+ deals with crashed clients and clients which have exited without cleanly closing
their resources. We'll also discuss how HornetQ multiplexes several sessions on a
single connection.</para>
<section id="dead.connections">
Modified: trunk/docs/user-manual/en/core-bridges.xml
===================================================================
--- trunk/docs/user-manual/en/core-bridges.xml 2009-08-21 09:35:43 UTC (rev 7856)
+++ trunk/docs/user-manual/en/core-bridges.xml 2009-08-21 09:38:07 UTC (rev 7857)
@@ -1,4 +1,23 @@
<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ============================================================================= -->
+<!-- Copyright © 2009 Red Hat, Inc. and others. -->
+<!-- -->
+<!-- The text of and illustrations in this document are licensed by Red Hat under -->
+<!-- a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). -->
+<!-- -->
+<!-- An explanation of CC-BY-SA is available at -->
+<!-- -->
+<!-- http://creativecommons.org/licenses/by-sa/3.0/. -->
+<!-- -->
+<!-- In accordance with CC-BY-SA, if you distribute this document or an adaptation -->
+<!-- of it, you must provide the URL for the original version. -->
+<!-- -->
+<!-- Red Hat, as the licensor of this document, waives the right to enforce, -->
+<!-- and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent -->
+<!-- permitted by applicable law. -->
+<!-- ============================================================================= -->
+
<chapter id="core-bridges">
<title>Core Bridges</title>
<para>The function of a bridge is to consume messages from a source queue, and forward them to a
@@ -81,7 +100,8 @@
<listitem>
<para><literal>filter-string</literal>. An optional filter string can be supplied.
If specified then only messages which match the filter expression specified in
- the filter string will be forwarded. The filter string follows the HornetQ filter expression syntax described in <xref linkend="filter-expressions" />.</para>
+ the filter string will be forwarded. The filter string follows the HornetQ
+ filter expression syntax described in <xref linkend="filter-expressions" />.</para>
</listitem>
<listitem>
<para><literal>transformer-class-name</literal>. An optional transformer-class-name
Modified: trunk/docs/user-manual/en/diverts.xml
===================================================================
--- trunk/docs/user-manual/en/diverts.xml 2009-08-21 09:35:43 UTC (rev 7856)
+++ trunk/docs/user-manual/en/diverts.xml 2009-08-21 09:38:07 UTC (rev 7857)
@@ -1,4 +1,23 @@
<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ============================================================================= -->
+<!-- Copyright © 2009 Red Hat, Inc. and others. -->
+<!-- -->
+<!-- The text of and illustrations in this document are licensed by Red Hat under -->
+<!-- a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). -->
+<!-- -->
+<!-- An explanation of CC-BY-SA is available at -->
+<!-- -->
+<!-- http://creativecommons.org/licenses/by-sa/3.0/. -->
+<!-- -->
+<!-- In accordance with CC-BY-SA, if you distribute this document or an adaptation -->
+<!-- of it, you must provide the URL for the original version. -->
+<!-- -->
+<!-- Red Hat, as the licensor of this document, waives the right to enforce, -->
+<!-- and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent -->
+<!-- permitted by applicable law. -->
+<!-- ============================================================================= -->
+
<chapter id="diverts">
<title>Diverting and Splitting Message Flows</title>
<para>HornetQ allows you to configure objects called <emphasis>diverts</emphasis> with
@@ -63,7 +82,8 @@
change the messages body or properties before it is diverted. In this example the
transformer simply adds a header that records the time the divert happened.</para>
<para>This example is actually diverting messages to a local store and forward queue, which
- is configured with a bridge which forwards the message to an address on another HornetQ server. Please see the example for more details.</para>
+ is configured with a bridge which forwards the message to an address on another HornetQ
+ server. Please see the example for more details.</para>
</section>
<section>
<title>Non-exclusive Divert</title>
Modified: trunk/docs/user-manual/en/duplicate-detection.xml
===================================================================
--- trunk/docs/user-manual/en/duplicate-detection.xml 2009-08-21 09:35:43 UTC (rev 7856)
+++ trunk/docs/user-manual/en/duplicate-detection.xml 2009-08-21 09:38:07 UTC (rev 7857)
@@ -1,9 +1,29 @@
<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ============================================================================= -->
+<!-- Copyright © 2009 Red Hat, Inc. and others. -->
+<!-- -->
+<!-- The text of and illustrations in this document are licensed by Red Hat under -->
+<!-- a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). -->
+<!-- -->
+<!-- An explanation of CC-BY-SA is available at -->
+<!-- -->
+<!-- http://creativecommons.org/licenses/by-sa/3.0/. -->
+<!-- -->
+<!-- In accordance with CC-BY-SA, if you distribute this document or an adaptation -->
+<!-- of it, you must provide the URL for the original version. -->
+<!-- -->
+<!-- Red Hat, as the licensor of this document, waives the right to enforce, -->
+<!-- and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent -->
+<!-- permitted by applicable law. -->
+<!-- ============================================================================= -->
+
<chapter id="duplicate-detection">
<title>Duplicate Message Detection</title>
<para>HornetQ includes powerful automatic duplicate message detection, filtering out
duplicate messages without you having to code your own fiddly duplicate detection logic at
- the application level. This chapter will explain what duplicate detection is, how HornetQ uses it and how and where to configure it.</para>
+ the application level. This chapter will explain what duplicate detection is, how HornetQ
+ uses it and how and where to configure it.</para>
<para>When sending messages from a client to a server, or indeed from a server to another
server, if the target server or connection fails sometime after sending the message, but
before the sender receives a response that the send (or commit) was processed successfully
Modified: trunk/docs/user-manual/en/embedding-hornetq.xml
===================================================================
--- trunk/docs/user-manual/en/embedding-hornetq.xml 2009-08-21 09:35:43 UTC (rev 7856)
+++ trunk/docs/user-manual/en/embedding-hornetq.xml 2009-08-21 09:38:07 UTC (rev 7857)
@@ -1,4 +1,23 @@
<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ============================================================================= -->
+<!-- Copyright © 2009 Red Hat, Inc. and others. -->
+<!-- -->
+<!-- The text of and illustrations in this document are licensed by Red Hat under -->
+<!-- a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). -->
+<!-- -->
+<!-- An explanation of CC-BY-SA is available at -->
+<!-- -->
+<!-- http://creativecommons.org/licenses/by-sa/3.0/. -->
+<!-- -->
+<!-- In accordance with CC-BY-SA, if you distribute this document or an adaptation -->
+<!-- of it, you must provide the URL for the original version. -->
+<!-- -->
+<!-- Red Hat, as the licensor of this document, waives the right to enforce, -->
+<!-- and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent -->
+<!-- permitted by applicable law. -->
+<!-- ============================================================================= -->
+
<chapter id="embedding-hornetq">
<title>Embedding HornetQ</title>
<para>HornetQ is designed as set of simple Plain Old Java Objects (POJOs). This means
@@ -10,13 +29,14 @@
<para>Examples of applications that might want to do this include any application that needs
very high performance, transactional, persistent messaging but doesn't want the hassle of
writing it all from scratch.</para>
- <para>Embedding JBM can be done in very few easy steps. Instantiate the configuration object,
+ <para>Embedding HornetQ can be done in very few easy steps. Instantiate the configuration object,
instantiate the server, start it, and you have a HornetQ running in your virtual
machine. It's as simple and easy as that.</para>
<section>
<title>POJO instantiation</title>
<para>You can follow this step-by-step guide:</para>
- <para>Create the configuration object - this contains configuration information for a HornetQ server. If you want to configure it from a file on the classpath, use <literal
+ <para>Create the configuration object - this contains configuration information for a HornetQ.
+ If you want to configure it from a file on the classpath, use <literal
>FileConfigurationImpl</literal></para>
<programlisting>import org.hornetq.core.config.Configuration;
import org.hornetq.core.config.impl.FileConfiguration;
@@ -46,20 +66,20 @@
config.setAcceptorConfigurations(transports);</programlisting>
<para>You need to instantiate and start HornetQ server. The class <literal
- >org.hornetq.core.serverMessaging</literal> has a few static methods for
+ >org.hornetq.core.server.Messaging</literal> has a few static methods for
creating servers with common configurations.</para>
- <programlisting>import org.hornetq.core.server.HornetQ;
-import org.hornetq.core.server.HornetQServer;
+ <programlisting>import org.hornetq.core.server.Messaging;
+import org.hornetq.core.server.MessagingServer;
...
-HornetQServer server = HornetQ.newHornetQServer(config);
+MessagingServer server = Messaging.newMessagingServer(config);
server.start();</programlisting>
- <para>You also have the option of instantiating <literal>HornetQServerImpl</literal>
+ <para>You also have the option of instantiating <literal>MessagingServerImpl</literal>
directly:</para>
- <programlisting>HornetQServer server =
- new HornetQServerImpl(config);
+ <programlisting>MessagingServer server =
+ new MessagingServerImpl(config);
server.start();</programlisting>
</section>
<section>
@@ -71,7 +91,7 @@
which are part of the HornetQ distribution provide a very complete
implementation of what's needed to bootstrap the server using JBoss Micro Container. </para>
<para>When using JBoss Micro Container, you need to provide a XML declaring the <literal
- >HornetQServer</literal> and <literal>Configuration</literal> object, you can also
+ >MessagingServer</literal> and <literal>Configuration</literal> object, you can also
inject a security manager and a MBean server if you want, but those are optional.</para>
<para>A very basic XML Bean declaration for the JBoss Micro Container would be:</para>
<programlisting><?xml version="1.0" encoding="UTF-8"?>
@@ -84,8 +104,8 @@
</bean>
<!-- The core server -->
- <bean name="HornetQServer"
- class="org.hornetq.core.server.impl.HornetQServerImpl">
+ <bean name="MessagingServer"
+ class="org.hornetq.core.server.impl.MessagingServerImpl">
<constructor>
<parameter>
<inject bean="Configuration"/>
Modified: trunk/docs/user-manual/en/examples.xml
===================================================================
--- trunk/docs/user-manual/en/examples.xml 2009-08-21 09:35:43 UTC (rev 7856)
+++ trunk/docs/user-manual/en/examples.xml 2009-08-21 09:38:07 UTC (rev 7857)
@@ -1,4 +1,23 @@
<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ============================================================================= -->
+<!-- Copyright © 2009 Red Hat, Inc. and others. -->
+<!-- -->
+<!-- The text of and illustrations in this document are licensed by Red Hat under -->
+<!-- a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). -->
+<!-- -->
+<!-- An explanation of CC-BY-SA is available at -->
+<!-- -->
+<!-- http://creativecommons.org/licenses/by-sa/3.0/. -->
+<!-- -->
+<!-- In accordance with CC-BY-SA, if you distribute this document or an adaptation -->
+<!-- of it, you must provide the URL for the original version. -->
+<!-- -->
+<!-- Red Hat, as the licensor of this document, waives the right to enforce, -->
+<!-- and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent -->
+<!-- permitted by applicable law. -->
+<!-- ============================================================================= -->
+
<chapter id="examples">
<title>Examples</title>
<para>The HornetQ distribution comes with a wide variety of run out-of-the-box examples
@@ -50,7 +69,8 @@
</section>
<section>
<title>Automatic Reconnect</title>
- <para>The <literal>reconnect-same-node</literal> example demonstrates how HornetQ connections can be configured to be resilient to temporary network
+ <para>The <literal>reconnect-same-node</literal> example demonstrates how HornetQ
+ connections can be configured to be resilient to temporary network
failures.</para>
<para> In the case of a network failure being detected, either as a result of a failure
to read/write to the connection, or the failure of a pong to arrive back from the
@@ -165,7 +185,8 @@
</section>
<section>
<title>HTTP Transport</title>
- <para>The <literal>http-transport</literal> example shows you how to configure HornetQ to use the HTTP protocol as its transport layer.</para>
+ <para>The <literal>http-transport</literal> example shows you how to configure HornetQ
+ to use the HTTP protocol as its transport layer.</para>
</section>
<section>
<title>Instantiate JMS Objects Directly</title>
@@ -285,7 +306,8 @@
</section>
<section id="producer-rate-limiting-example">
<title>Message Producer Rate Limiting</title>
- <para>The <literal>producer-rte-limit</literal> example demonstrates how, with HornetQ, you can specify a maximum send rate at which a JMS message producer will
+ <para>The <literal>producer-rte-limit</literal> example demonstrates how, with HornetQ,
+ you can specify a maximum send rate at which a JMS message producer will
send messages.</para>
</section>
<section id="examples.message-priority">
@@ -312,7 +334,8 @@
<para>By default, HornetQ consumers buffer messages from the server in a client
side buffer before you actually receive them on the client side. This improves
performance since otherwise every time you called receive() or had processed the
- last message in a <literal>MessageListener onMessage()</literal> method, the HornetQ client would have to go the server to request the next message, which
+ last message in a <literal>MessageListener onMessage()</literal> method, the HornetQ
+ client would have to go the server to request the next message, which
would then get sent to the client side, if one was available.</para>
<para>This would involve a network round trip for every message and really reduce
performance. Therefore, by default, HornetQ pre-fetches messages into a
@@ -369,13 +392,15 @@
</section>
<section id="asynchronous-send-acknowledgements-example">
<title>Send Acknowledgements</title>
- <para>The <literal>send-acknowledgements</literal> example shows you how to use HornetQ's advanced <emphasis>asynchronous send acknowledgements</emphasis> feature
+ <para>The <literal>send-acknowledgements</literal> example shows you how to use HornetQ's
+ advanced <emphasis>asynchronous send acknowledgements</emphasis> feature
to obtain acknowledgement from the server that sends have been received and
processed in a separate stream to the sent messages. </para>
</section>
<section>
<title>Static Message Selector</title>
- <para>The <literal>static-selector</literal> example shows you how to configure a HornetQ core queue with static message selectors (filters).</para>
+ <para>The <literal>static-selector</literal> example shows you how to configure a HornetQ
+ core queue with static message selectors (filters).</para>
</section>
<section>
<title>Static Message Selector Using JMS</title>
@@ -384,7 +409,8 @@
</section>
<section>
<title>SSL Transport</title>
- <para>The <literal>ssl-enabled</literal> shows you how to configure SSL with HornetQ to send and receive message.</para>
+ <para>The <literal>ssl-enabled</literal> shows you how to configure SSL with HornetQ
+ to send and receive message.</para>
</section>
<section>
<title>Symmetric Cluster</title>
@@ -477,7 +503,8 @@
</section>
<section>
<title>Resource Adapter Configuration</title>
- <para>This example demonstrates how to configure several properties on the HornetQ JCA resource adaptor.</para>
+ <para>This example demonstrates how to configure several properties on the HornetQ
+ JCA resource adaptor.</para>
</section>
<section id="jms-bridge-example">
<title>JMS Bridge</title>
Modified: trunk/docs/user-manual/en/filter-expressions.xml
===================================================================
--- trunk/docs/user-manual/en/filter-expressions.xml 2009-08-21 09:35:43 UTC (rev 7856)
+++ trunk/docs/user-manual/en/filter-expressions.xml 2009-08-21 09:38:07 UTC (rev 7857)
@@ -1,4 +1,23 @@
<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ============================================================================= -->
+<!-- Copyright © 2009 Red Hat, Inc. and others. -->
+<!-- -->
+<!-- The text of and illustrations in this document are licensed by Red Hat under -->
+<!-- a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). -->
+<!-- -->
+<!-- An explanation of CC-BY-SA is available at -->
+<!-- -->
+<!-- http://creativecommons.org/licenses/by-sa/3.0/. -->
+<!-- -->
+<!-- In accordance with CC-BY-SA, if you distribute this document or an adaptation -->
+<!-- of it, you must provide the URL for the original version. -->
+<!-- -->
+<!-- Red Hat, as the licensor of this document, waives the right to enforce, -->
+<!-- and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent -->
+<!-- permitted by applicable law. -->
+<!-- ============================================================================= -->
+
<chapter id="filter-expressions">
<title>Filter Expressions</title>
<para>HornetQ provides a powerful filter language based on a subset of the SQL 92
@@ -29,7 +48,8 @@
</listitem>
</itemizedlist>
<para>There are some differences between JMS selector expressions and HornetQ core
- filter expressions. Whereas JMS selector expressions operate on a JMS message, HornetQ core filter expressions operate on a core message.</para>
+ filter expressions. Whereas JMS selector expressions operate on a JMS message, HornetQ
+ core filter expressions operate on a core message.</para>
<para>The following identifiers can be used in a core filter expressions to refer to attributes
of the core message in an expression:</para>
<itemizedlist>
Modified: trunk/docs/user-manual/en/flow-control.xml
===================================================================
--- trunk/docs/user-manual/en/flow-control.xml 2009-08-21 09:35:43 UTC (rev 7856)
+++ trunk/docs/user-manual/en/flow-control.xml 2009-08-21 09:38:07 UTC (rev 7857)
@@ -1,4 +1,23 @@
<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ============================================================================= -->
+<!-- Copyright © 2009 Red Hat, Inc. and others. -->
+<!-- -->
+<!-- The text of and illustrations in this document are licensed by Red Hat under -->
+<!-- a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). -->
+<!-- -->
+<!-- An explanation of CC-BY-SA is available at -->
+<!-- -->
+<!-- http://creativecommons.org/licenses/by-sa/3.0/. -->
+<!-- -->
+<!-- In accordance with CC-BY-SA, if you distribute this document or an adaptation -->
+<!-- of it, you must provide the URL for the original version. -->
+<!-- -->
+<!-- Red Hat, as the licensor of this document, waives the right to enforce, -->
+<!-- and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent -->
+<!-- permitted by applicable law. -->
+<!-- ============================================================================= -->
+
<chapter id="flow-control">
<title>Flow Control</title>
<para>Flow control is used to limit the flow of data between a client and server, or a server and
Modified: trunk/docs/user-manual/en/ha.xml
===================================================================
--- trunk/docs/user-manual/en/ha.xml 2009-08-21 09:35:43 UTC (rev 7856)
+++ trunk/docs/user-manual/en/ha.xml 2009-08-21 09:38:07 UTC (rev 7857)
@@ -1,4 +1,23 @@
<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ============================================================================= -->
+<!-- Copyright © 2009 Red Hat, Inc. and others. -->
+<!-- -->
+<!-- The text of and illustrations in this document are licensed by Red Hat under -->
+<!-- a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). -->
+<!-- -->
+<!-- An explanation of CC-BY-SA is available at -->
+<!-- -->
+<!-- http://creativecommons.org/licenses/by-sa/3.0/. -->
+<!-- -->
+<!-- In accordance with CC-BY-SA, if you distribute this document or an adaptation -->
+<!-- of it, you must provide the URL for the original version. -->
+<!-- -->
+<!-- Red Hat, as the licensor of this document, waives the right to enforce, -->
+<!-- and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent -->
+<!-- permitted by applicable law. -->
+<!-- ============================================================================= -->
+
<chapter id="ha">
<title>High Availability and Failover</title>
<para>We define high availability as the <emphasis>ability for the system to continue
@@ -128,7 +147,8 @@
the <literal>hornetq-jms.xml</literal> file when you define the connection factory, or if
using core by setting the property directly on the <literal
>ClientSessionFactoryImpl</literal> instance after creation. The default value for
- this property is <literal>false</literal>, this means that by default <emphasis>HornetQ clients will not failover to a backup server if the live server is simply
+ this property is <literal>false</literal>, this means that by default <emphasis>HornetQ
+ clients will not failover to a backup server if the live server is simply
shutdown cleanly.</emphasis></para>
<para>For a fully functional example of automatic failover, please see <xref
linkend="automatic-failover"/>.</para>
Modified: trunk/docs/user-manual/en/intercepting-operations.xml
===================================================================
--- trunk/docs/user-manual/en/intercepting-operations.xml 2009-08-21 09:35:43 UTC (rev 7856)
+++ trunk/docs/user-manual/en/intercepting-operations.xml 2009-08-21 09:38:07 UTC (rev 7857)
@@ -1,4 +1,23 @@
<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ============================================================================= -->
+<!-- Copyright © 2009 Red Hat, Inc. and others. -->
+<!-- -->
+<!-- The text of and illustrations in this document are licensed by Red Hat under -->
+<!-- a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). -->
+<!-- -->
+<!-- An explanation of CC-BY-SA is available at -->
+<!-- -->
+<!-- http://creativecommons.org/licenses/by-sa/3.0/. -->
+<!-- -->
+<!-- In accordance with CC-BY-SA, if you distribute this document or an adaptation -->
+<!-- of it, you must provide the URL for the original version. -->
+<!-- -->
+<!-- Red Hat, as the licensor of this document, waives the right to enforce, -->
+<!-- and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent -->
+<!-- permitted by applicable law. -->
+<!-- ============================================================================= -->
+
<chapter id="intercepting-operations">
<title>Intercepting Operations</title>
<para>HornetQ supports <emphasis>interceptors</emphasis> to intercept packets entering
Modified: trunk/docs/user-manual/en/interoperability.xml
===================================================================
--- trunk/docs/user-manual/en/interoperability.xml 2009-08-21 09:35:43 UTC (rev 7856)
+++ trunk/docs/user-manual/en/interoperability.xml 2009-08-21 09:38:07 UTC (rev 7857)
@@ -1,4 +1,23 @@
<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ============================================================================= -->
+<!-- Copyright © 2009 Red Hat, Inc. and others. -->
+<!-- -->
+<!-- The text of and illustrations in this document are licensed by Red Hat under -->
+<!-- a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). -->
+<!-- -->
+<!-- An explanation of CC-BY-SA is available at -->
+<!-- -->
+<!-- http://creativecommons.org/licenses/by-sa/3.0/. -->
+<!-- -->
+<!-- In accordance with CC-BY-SA, if you distribute this document or an adaptation -->
+<!-- of it, you must provide the URL for the original version. -->
+<!-- -->
+<!-- Red Hat, as the licensor of this document, waives the right to enforce, -->
+<!-- and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent -->
+<!-- permitted by applicable law. -->
+<!-- ============================================================================= -->
+
<chapter id="interoperability">
<title>Interoperability</title>
<section>
@@ -17,8 +36,8 @@
<programlisting>java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
java.naming.provider.url=jnp://localhost:1099
java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces</programlisting>
- <para>Make sure this file is in the classpath along with the StompConnect jar and the HornetQ jars and simply run <literal>java
- org.codehaus.stomp.jms.Main</literal>.</para>
+ <para>Make sure this file is in the classpath along with the StompConnect jar and the HornetQ
+ jars and simply run <literal>java org.codehaus.stomp.jms.Main</literal>.</para>
<para>HornetQ will shortly be implementing the Stomp protocol directly, so you won't
have to use StompConnect to be able to use HornetQ with Stomp clients.</para>
</section>
Modified: trunk/docs/user-manual/en/jms-core-mapping.xml
===================================================================
--- trunk/docs/user-manual/en/jms-core-mapping.xml 2009-08-21 09:35:43 UTC (rev 7856)
+++ trunk/docs/user-manual/en/jms-core-mapping.xml 2009-08-21 09:38:07 UTC (rev 7857)
@@ -1,4 +1,23 @@
<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ============================================================================= -->
+<!-- Copyright © 2009 Red Hat, Inc. and others. -->
+<!-- -->
+<!-- The text of and illustrations in this document are licensed by Red Hat under -->
+<!-- a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). -->
+<!-- -->
+<!-- An explanation of CC-BY-SA is available at -->
+<!-- -->
+<!-- http://creativecommons.org/licenses/by-sa/3.0/. -->
+<!-- -->
+<!-- In accordance with CC-BY-SA, if you distribute this document or an adaptation -->
+<!-- of it, you must provide the URL for the original version. -->
+<!-- -->
+<!-- Red Hat, as the licensor of this document, waives the right to enforce, -->
+<!-- and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent -->
+<!-- permitted by applicable law. -->
+<!-- ============================================================================= -->
+
<chapter id="jms-core-mapping">
<title>Mapping JMS Concepts to the Core API</title>
<para>This chapter describes how JMS destinations are mapped to HornetQ core
Modified: trunk/docs/user-manual/en/large-messages.xml
===================================================================
--- trunk/docs/user-manual/en/large-messages.xml 2009-08-21 09:35:43 UTC (rev 7856)
+++ trunk/docs/user-manual/en/large-messages.xml 2009-08-21 09:38:07 UTC (rev 7857)
@@ -1,4 +1,23 @@
<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ============================================================================= -->
+<!-- Copyright © 2009 Red Hat, Inc. and others. -->
+<!-- -->
+<!-- The text of and illustrations in this document are licensed by Red Hat under -->
+<!-- a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). -->
+<!-- -->
+<!-- An explanation of CC-BY-SA is available at -->
+<!-- -->
+<!-- http://creativecommons.org/licenses/by-sa/3.0/. -->
+<!-- -->
+<!-- In accordance with CC-BY-SA, if you distribute this document or an adaptation -->
+<!-- of it, you must provide the URL for the original version. -->
+<!-- -->
+<!-- Red Hat, as the licensor of this document, waives the right to enforce, -->
+<!-- and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent -->
+<!-- permitted by applicable law. -->
+<!-- ============================================================================= -->
+
<chapter id="large-messages">
<title>Large Messages</title>
<para>HornetQ supports sending and receiving of huge messages, even when the client and
Modified: trunk/docs/user-manual/en/last-value-queues.xml
===================================================================
--- trunk/docs/user-manual/en/last-value-queues.xml 2009-08-21 09:35:43 UTC (rev 7856)
+++ trunk/docs/user-manual/en/last-value-queues.xml 2009-08-21 09:38:07 UTC (rev 7857)
@@ -1,4 +1,23 @@
<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ============================================================================= -->
+<!-- Copyright © 2009 Red Hat, Inc. and others. -->
+<!-- -->
+<!-- The text of and illustrations in this document are licensed by Red Hat under -->
+<!-- a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). -->
+<!-- -->
+<!-- An explanation of CC-BY-SA is available at -->
+<!-- -->
+<!-- http://creativecommons.org/licenses/by-sa/3.0/. -->
+<!-- -->
+<!-- In accordance with CC-BY-SA, if you distribute this document or an adaptation -->
+<!-- of it, you must provide the URL for the original version. -->
+<!-- -->
+<!-- Red Hat, as the licensor of this document, waives the right to enforce, -->
+<!-- and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent -->
+<!-- permitted by applicable law. -->
+<!-- ============================================================================= -->
+
<chapter id="last-value-queues">
<title>Last-Value Queues</title>
<para>Last-Value queues are special queues which discard any messages when a newer message with
Modified: trunk/docs/user-manual/en/libaio.xml
===================================================================
--- trunk/docs/user-manual/en/libaio.xml 2009-08-21 09:35:43 UTC (rev 7856)
+++ trunk/docs/user-manual/en/libaio.xml 2009-08-21 09:38:07 UTC (rev 7857)
@@ -1,4 +1,23 @@
<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ============================================================================= -->
+<!-- Copyright © 2009 Red Hat, Inc. and others. -->
+<!-- -->
+<!-- The text of and illustrations in this document are licensed by Red Hat under -->
+<!-- a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). -->
+<!-- -->
+<!-- An explanation of CC-BY-SA is available at -->
+<!-- -->
+<!-- http://creativecommons.org/licenses/by-sa/3.0/. -->
+<!-- -->
+<!-- In accordance with CC-BY-SA, if you distribute this document or an adaptation -->
+<!-- of it, you must provide the URL for the original version. -->
+<!-- -->
+<!-- Red Hat, as the licensor of this document, waives the right to enforce, -->
+<!-- and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent -->
+<!-- permitted by applicable law. -->
+<!-- ============================================================================= -->
+
<chapter id="libaio">
<title>Libaio Native Libraries</title>
<para>HornetQ distributes a native library, used as a bridge between HornetQ and
@@ -19,7 +38,7 @@
<para>libHornetQAIO_ia64.so - Itanium 64 bits</para>
</listitem>
</itemizedlist>
- <para>When using libaio, HornetQ will aways try loading these files as long as they are
+ <para>When using libaio, HornetQ will always try loading these files as long as they are
on the <link linkend="using-server.library.path">library path</link>.</para>
<section>
<title>Compiling the native libraries</title>
Modified: trunk/docs/user-manual/en/logging.xml
===================================================================
--- trunk/docs/user-manual/en/logging.xml 2009-08-21 09:35:43 UTC (rev 7856)
+++ trunk/docs/user-manual/en/logging.xml 2009-08-21 09:38:07 UTC (rev 7857)
@@ -1,4 +1,23 @@
<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ============================================================================= -->
+<!-- Copyright © 2009 Red Hat, Inc. and others. -->
+<!-- -->
+<!-- The text of and illustrations in this document are licensed by Red Hat under -->
+<!-- a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). -->
+<!-- -->
+<!-- An explanation of CC-BY-SA is available at -->
+<!-- -->
+<!-- http://creativecommons.org/licenses/by-sa/3.0/. -->
+<!-- -->
+<!-- In accordance with CC-BY-SA, if you distribute this document or an adaptation -->
+<!-- of it, you must provide the URL for the original version. -->
+<!-- -->
+<!-- Red Hat, as the licensor of this document, waives the right to enforce, -->
+<!-- and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent -->
+<!-- permitted by applicable law. -->
+<!-- ============================================================================= -->
+
<chapter id="logging">
<title>Logging</title>
<para>HornetQ uses standard <ulink url="http://java.sun.com/j2se/1.4.2/docs/guide/util/logging/">JDK
Modified: trunk/docs/user-manual/en/management.xml
===================================================================
--- trunk/docs/user-manual/en/management.xml 2009-08-21 09:35:43 UTC (rev 7856)
+++ trunk/docs/user-manual/en/management.xml 2009-08-21 09:38:07 UTC (rev 7857)
@@ -1,4 +1,23 @@
<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ============================================================================= -->
+<!-- Copyright © 2009 Red Hat, Inc. and others. -->
+<!-- -->
+<!-- The text of and illustrations in this document are licensed by Red Hat under -->
+<!-- a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). -->
+<!-- -->
+<!-- An explanation of CC-BY-SA is available at -->
+<!-- -->
+<!-- http://creativecommons.org/licenses/by-sa/3.0/. -->
+<!-- -->
+<!-- In accordance with CC-BY-SA, if you distribute this document or an adaptation -->
+<!-- of it, you must provide the URL for the original version. -->
+<!-- -->
+<!-- Red Hat, as the licensor of this document, waives the right to enforce, -->
+<!-- and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent -->
+<!-- permitted by applicable law. -->
+<!-- ============================================================================= -->
+
<chapter id="management">
<title>Management</title>
<para>HornetQ has an extensive management API that allows a user to modify a server
@@ -449,7 +468,8 @@
<para>HornetQ can be managed using <ulink
url="http://java.sun.com/javase/technologies/core/mntr-mgmt/javamanagement/"
>JMX</ulink>. </para>
- <para>The management API is exposed by HornetQ using MBeans interfaces. HornetQ registers its resources with the domain <literal
+ <para>The management API is exposed by HornetQ using MBeans interfaces. HornetQ
+ registers its resources with the domain <literal
>org.hornetq</literal>.</para>
<para>For example, the <literal>ObjectName</literal> to manage a JMS Queue <literal
>exampleQueue</literal> is:</para>
@@ -798,7 +818,8 @@
<title>Example</title>
<para>See <xref linkend="examples.management-notifications" /> for an example which
shows how to use a
- JMS <literal>MessageListener</literal> to receive management notifications from HornetQ server.</para>
+ JMS <literal>MessageListener</literal> to receive management notifications from HornetQ
+ server.</para>
</section>
</section>
<section id="management.message-counters">
Modified: trunk/docs/user-manual/en/master.xml
===================================================================
--- trunk/docs/user-manual/en/master.xml 2009-08-21 09:35:43 UTC (rev 7856)
+++ trunk/docs/user-manual/en/master.xml 2009-08-21 09:38:07 UTC (rev 7857)
@@ -1,4 +1,23 @@
<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ============================================================================= -->
+<!-- Copyright © 2009 Red Hat, Inc. and others. -->
+<!-- -->
+<!-- The text of and illustrations in this document are licensed by Red Hat under -->
+<!-- a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). -->
+<!-- -->
+<!-- An explanation of CC-BY-SA is available at -->
+<!-- -->
+<!-- http://creativecommons.org/licenses/by-sa/3.0/. -->
+<!-- -->
+<!-- In accordance with CC-BY-SA, if you distribute this document or an adaptation -->
+<!-- of it, you must provide the URL for the original version. -->
+<!-- -->
+<!-- Red Hat, as the licensor of this document, waives the right to enforce, -->
+<!-- and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent -->
+<!-- permitted by applicable law. -->
+<!-- ============================================================================= -->
+
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.3CR3//EN"
"../../../lib/docbook-support/support/docbook-dtd/docbookx.dtd" [
<!ENTITY appserver-integration SYSTEM "appserver-integration.xml">
@@ -50,8 +69,77 @@
]>
<book lang="en">
<bookinfo>
- <graphic fileref="images/hornetQ-banner_final.png" align="center"/>
- <title>HornetQ 2.0 User Manual </title>
+ <title>HornetQ User Manual</title>
+ <subtitle>Putting the buzz in messaging</subtitle>
+ <legalnotice>
+ <para>Copyright © 2009 Red Hat, Inc. and others.</para>
+ <para>The text of and illustrations in this document are licensed by Red Hat under
+ a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA").</para>
+ <para>An explanation of CC-BY-SA is available at
+ <ulink url="http://creativecommons.org/licenses/by-sa/3.0/">http://creativecommons.org/licenses/by-sa/3.0/</ulink>.
+ In accordance with CC-BY-SA, if you distribute this document or an adaptation
+ of it, you must provide the URL for the original version.</para>
+ <para>Red Hat, as the licensor of this document, waives the right to enforce,
+ and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent
+ permitted by applicable law.</para>
+ </legalnotice>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/hornetQ_logo_600px.png" format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase>HornetQ - Putting the buzz in messaging</phrase>
+ </textobject>
+ </mediaobject>
</bookinfo>
- <toc/>&preface;&messaging-concepts;&architecture;&using-server;&using-jms;&using-core;&jms-core-mapping;&client-classpath;&examples;&wildcard-routing;&wildcard-syntax;&filter-expressions;&persistence;&configuring-transports;&connection-ttl;&transaction-config;&flow-control;&command-buffering;&send-guarantees;&undelivered-messages;&message-expiry;&large-messages;&paging;&queue-attributes;&scheduled-messages;&last-value-queues;&message-grouping;&pre-acknowledge;&management;&security;&appserver-integration;&client-reconnection;&diverts;&core-bridges;&duplicate-detection;&clusters;&ha;&libaio;&thread-pooling;&logging;&embedding-hornetq;&intercepting-operations;&interoperability;&perf-tuning;&configuration-index;&project-info;
+
+ <toc></toc>
+
+ &preface;
+ &messaging-concepts;
+ &architecture;
+ &using-server;
+ &using-jms;
+ &using-core;
+ &jms-core-mapping;
+ &client-classpath;
+ &examples;
+ &wildcard-routing;
+ &wildcard-syntax;
+ &filter-expressions;
+ &persistence;
+ &configuring-transports;
+ &connection-ttl;
+ &transaction-config;
+ &flow-control;
+ &command-buffering;
+ &send-guarantees;
+ &undelivered-messages;
+ &message-expiry;
+ &large-messages;
+ &paging;
+ &queue-attributes;
+ &scheduled-messages;
+ &last-value-queues;
+ &message-grouping;
+ &pre-acknowledge;
+ &management;
+ &security;
+ &appserver-integration;
+ &client-reconnection;
+ &diverts;
+ &core-bridges;
+ &duplicate-detection;
+ &clusters;
+ &ha;
+ &libaio;
+ &thread-pooling;
+ &logging;
+ &embedding-hornetq;
+ &intercepting-operations;
+ &interoperability;
+ &perf-tuning;
+ &configuration-index;
+ &project-info;
+
</book>
Modified: trunk/docs/user-manual/en/message-expiry.xml
===================================================================
--- trunk/docs/user-manual/en/message-expiry.xml 2009-08-21 09:35:43 UTC (rev 7856)
+++ trunk/docs/user-manual/en/message-expiry.xml 2009-08-21 09:38:07 UTC (rev 7857)
@@ -1,4 +1,23 @@
<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ============================================================================= -->
+<!-- Copyright © 2009 Red Hat, Inc. and others. -->
+<!-- -->
+<!-- The text of and illustrations in this document are licensed by Red Hat under -->
+<!-- a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). -->
+<!-- -->
+<!-- An explanation of CC-BY-SA is available at -->
+<!-- -->
+<!-- http://creativecommons.org/licenses/by-sa/3.0/. -->
+<!-- -->
+<!-- In accordance with CC-BY-SA, if you distribute this document or an adaptation -->
+<!-- of it, you must provide the URL for the original version. -->
+<!-- -->
+<!-- Red Hat, as the licensor of this document, waives the right to enforce, -->
+<!-- and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent -->
+<!-- permitted by applicable law. -->
+<!-- ============================================================================= -->
+
<chapter id="message-expiry">
<title>Message Expiry</title>
<para>Messages can be set with an optional <emphasis>time to live</emphasis> when sending them.
Modified: trunk/docs/user-manual/en/message-grouping.xml
===================================================================
--- trunk/docs/user-manual/en/message-grouping.xml 2009-08-21 09:35:43 UTC (rev 7856)
+++ trunk/docs/user-manual/en/message-grouping.xml 2009-08-21 09:38:07 UTC (rev 7857)
@@ -1,4 +1,23 @@
<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ============================================================================= -->
+<!-- Copyright © 2009 Red Hat, Inc. and others. -->
+<!-- -->
+<!-- The text of and illustrations in this document are licensed by Red Hat under -->
+<!-- a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). -->
+<!-- -->
+<!-- An explanation of CC-BY-SA is available at -->
+<!-- -->
+<!-- http://creativecommons.org/licenses/by-sa/3.0/. -->
+<!-- -->
+<!-- In accordance with CC-BY-SA, if you distribute this document or an adaptation -->
+<!-- of it, you must provide the URL for the original version. -->
+<!-- -->
+<!-- Red Hat, as the licensor of this document, waives the right to enforce, -->
+<!-- and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent -->
+<!-- permitted by applicable law. -->
+<!-- ============================================================================= -->
+
<chapter id="message-grouping">
<title>Message Grouping</title>
<para>Message groups are sets of messages that has the following characteristics:</para>
@@ -43,7 +62,7 @@
producer.send(message);
</programlisting>
<para>Alternatively, you can set <literal>autogroup</literal> to true on the <literal
- >HornetQConnectionFactory</literal> which will pick a random unique id. This can also be
+ >HornetQConnectonFactory</literal> which will pick a random unique id. This can also be
set in the <literal>hornetq-jms.xml</literal> file like this:</para>
<programlisting><connection-factory name="ConnectionFactory">
<connector-ref connector-name="netty-connector"/>
Modified: trunk/docs/user-manual/en/messaging-concepts.xml
===================================================================
--- trunk/docs/user-manual/en/messaging-concepts.xml 2009-08-21 09:35:43 UTC (rev 7856)
+++ trunk/docs/user-manual/en/messaging-concepts.xml 2009-08-21 09:38:07 UTC (rev 7857)
@@ -1,4 +1,23 @@
<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ============================================================================= -->
+<!-- Copyright © 2009 Red Hat, Inc. and others. -->
+<!-- -->
+<!-- The text of and illustrations in this document are licensed by Red Hat under -->
+<!-- a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). -->
+<!-- -->
+<!-- An explanation of CC-BY-SA is available at -->
+<!-- -->
+<!-- http://creativecommons.org/licenses/by-sa/3.0/. -->
+<!-- -->
+<!-- In accordance with CC-BY-SA, if you distribute this document or an adaptation -->
+<!-- of it, you must provide the URL for the original version. -->
+<!-- -->
+<!-- Red Hat, as the licensor of this document, waives the right to enforce, -->
+<!-- and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent -->
+<!-- permitted by applicable law. -->
+<!-- ============================================================================= -->
+
<chapter id="messaging-concepts">
<title>Messaging Concepts</title>
<para>HornetQ is an asynchronous messaging system, an example of <ulink
Modified: trunk/docs/user-manual/en/paging.xml
===================================================================
--- trunk/docs/user-manual/en/paging.xml 2009-08-21 09:35:43 UTC (rev 7856)
+++ trunk/docs/user-manual/en/paging.xml 2009-08-21 09:38:07 UTC (rev 7857)
@@ -1,4 +1,23 @@
<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ============================================================================= -->
+<!-- Copyright © 2009 Red Hat, Inc. and others. -->
+<!-- -->
+<!-- The text of and illustrations in this document are licensed by Red Hat under -->
+<!-- a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). -->
+<!-- -->
+<!-- An explanation of CC-BY-SA is available at -->
+<!-- -->
+<!-- http://creativecommons.org/licenses/by-sa/3.0/. -->
+<!-- -->
+<!-- In accordance with CC-BY-SA, if you distribute this document or an adaptation -->
+<!-- of it, you must provide the URL for the original version. -->
+<!-- -->
+<!-- Red Hat, as the licensor of this document, waives the right to enforce, -->
+<!-- and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent -->
+<!-- permitted by applicable law. -->
+<!-- ============================================================================= -->
+
<chapter id="paging">
<title>Paging</title>
<para>HornetQ transparently supports huge queues containing millions of messages while
Modified: trunk/docs/user-manual/en/perf-tuning.xml
===================================================================
--- trunk/docs/user-manual/en/perf-tuning.xml 2009-08-21 09:35:43 UTC (rev 7856)
+++ trunk/docs/user-manual/en/perf-tuning.xml 2009-08-21 09:38:07 UTC (rev 7857)
@@ -1,4 +1,23 @@
<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ============================================================================= -->
+<!-- Copyright © 2009 Red Hat, Inc. and others. -->
+<!-- -->
+<!-- The text of and illustrations in this document are licensed by Red Hat under -->
+<!-- a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). -->
+<!-- -->
+<!-- An explanation of CC-BY-SA is available at -->
+<!-- -->
+<!-- http://creativecommons.org/licenses/by-sa/3.0/. -->
+<!-- -->
+<!-- In accordance with CC-BY-SA, if you distribute this document or an adaptation -->
+<!-- of it, you must provide the URL for the original version. -->
+<!-- -->
+<!-- Red Hat, as the licensor of this document, waives the right to enforce, -->
+<!-- and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent -->
+<!-- permitted by applicable law. -->
+<!-- ============================================================================= -->
+
<chapter id="perf-tuning">
<title>Performance Tuning</title>
<para>In this chapter we'll discuss how to tune HornetQ for optimum performance.</para>
@@ -22,7 +41,8 @@
</listitem>
<listitem>
<para><literal>journal-aio-flush-on-sync</literal>. If you don't have many producers
- in your system you may consider setting journal-aio-flush-on-sync to true. HornetQ by default is optimized by the case where you have many producers. We
+ in your system you may consider setting journal-aio-flush-on-sync to true. HornetQ
+ by default is optimized by the case where you have many producers. We
try to combine multiple writes in a single OS operation. However if that's not
your case setting this option to true will give you a performance boost.</para>
<para>On the other hand when you have multiple producers, keeping <literal
Modified: trunk/docs/user-manual/en/persistence.xml
===================================================================
--- trunk/docs/user-manual/en/persistence.xml 2009-08-21 09:35:43 UTC (rev 7856)
+++ trunk/docs/user-manual/en/persistence.xml 2009-08-21 09:38:07 UTC (rev 7857)
@@ -1,4 +1,23 @@
<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ============================================================================= -->
+<!-- Copyright © 2009 Red Hat, Inc. and others. -->
+<!-- -->
+<!-- The text of and illustrations in this document are licensed by Red Hat under -->
+<!-- a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). -->
+<!-- -->
+<!-- An explanation of CC-BY-SA is available at -->
+<!-- -->
+<!-- http://creativecommons.org/licenses/by-sa/3.0/. -->
+<!-- -->
+<!-- In accordance with CC-BY-SA, if you distribute this document or an adaptation -->
+<!-- of it, you must provide the URL for the original version. -->
+<!-- -->
+<!-- Red Hat, as the licensor of this document, waives the right to enforce, -->
+<!-- and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent -->
+<!-- permitted by applicable law. -->
+<!-- ============================================================================= -->
+
<chapter id="persistence">
<title>Persistence</title>
<para>In this chapter we will describe how persistence works with HornetQ and how to
@@ -30,7 +49,8 @@
<para>The journal also fully supports transactional operation if required, supporting both local
and XA transactions.</para>
<para>The majority of the journal is written in Java, however we abstract out the interaction
- with the actual file system to allow different pluggable implementations. We ship HornetQ with two implementations:</para>
+ with the actual file system to allow different pluggable implementations. HornetQ ships
+ with two implementations:</para>
<itemizedlist>
<listitem>
<para>Java <ulink url="http://en.wikipedia.org/wiki/New_I/O">NIO</ulink>.</para>
Modified: trunk/docs/user-manual/en/pre-acknowledge.xml
===================================================================
--- trunk/docs/user-manual/en/pre-acknowledge.xml 2009-08-21 09:35:43 UTC (rev 7856)
+++ trunk/docs/user-manual/en/pre-acknowledge.xml 2009-08-21 09:38:07 UTC (rev 7857)
@@ -1,4 +1,23 @@
<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ============================================================================= -->
+<!-- Copyright © 2009 Red Hat, Inc. and others. -->
+<!-- -->
+<!-- The text of and illustrations in this document are licensed by Red Hat under -->
+<!-- a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). -->
+<!-- -->
+<!-- An explanation of CC-BY-SA is available at -->
+<!-- -->
+<!-- http://creativecommons.org/licenses/by-sa/3.0/. -->
+<!-- -->
+<!-- In accordance with CC-BY-SA, if you distribute this document or an adaptation -->
+<!-- of it, you must provide the URL for the original version. -->
+<!-- -->
+<!-- Red Hat, as the licensor of this document, waives the right to enforce, -->
+<!-- and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent -->
+<!-- permitted by applicable law. -->
+<!-- ============================================================================= -->
+
<chapter id="pre-acknowledge">
<title>Pre-Acknowledge Mode</title>
<para>JMS specifies 3 acknowledgement modes:</para>
Modified: trunk/docs/user-manual/en/preface.xml
===================================================================
--- trunk/docs/user-manual/en/preface.xml 2009-08-21 09:35:43 UTC (rev 7856)
+++ trunk/docs/user-manual/en/preface.xml 2009-08-21 09:38:07 UTC (rev 7857)
@@ -1,7 +1,26 @@
<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ============================================================================= -->
+<!-- Copyright © 2009 Red Hat, Inc. and others. -->
+<!-- -->
+<!-- The text of and illustrations in this document are licensed by Red Hat under -->
+<!-- a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). -->
+<!-- -->
+<!-- An explanation of CC-BY-SA is available at -->
+<!-- -->
+<!-- http://creativecommons.org/licenses/by-sa/3.0/. -->
+<!-- -->
+<!-- In accordance with CC-BY-SA, if you distribute this document or an adaptation -->
+<!-- of it, you must provide the URL for the original version. -->
+<!-- -->
+<!-- Red Hat, as the licensor of this document, waives the right to enforce, -->
+<!-- and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent -->
+<!-- permitted by applicable law. -->
+<!-- ============================================================================= -->
+
<chapter id="preface">
<title>Preface</title>
- <para>The goal of HornetQ is simple and uncompromising; to bring unrivalled levels of
+ <para>The goal of HornetQ is simple and uncompromising; to bring unrivaled levels of
performance and reliability to messaging, and to be the fastest, best featured and most
scalable multi-protocol messaging system.</para>
<para>Why use HornetQ? Here are just a few of the reasons:</para>
@@ -23,11 +42,12 @@
and others you won't find anywhere else.</para>
</listitem>
<listitem>
- <para>Elegant POJO based design with minimal third party dependencies. Run HornetQ stand-alone, run it in integrated in your favourite JEE application
+ <para>Elegant POJO based design with minimal third party dependencies. Run HornetQ
+ stand-alone, run it in integrated in your favourite JEE application
server, or run it embedded inside your own product.</para>
</listitem>
<listitem>
- <para>Seamless high availabilty. We provide server replication and completely
+ <para>Seamless high availability. We provide server replication and completely
transparent client failover so you don't have to worry about coding your client
specially for an HA environment.</para>
</listitem>
Modified: trunk/docs/user-manual/en/project-info.xml
===================================================================
--- trunk/docs/user-manual/en/project-info.xml 2009-08-21 09:35:43 UTC (rev 7856)
+++ trunk/docs/user-manual/en/project-info.xml 2009-08-21 09:38:07 UTC (rev 7857)
@@ -1,22 +1,51 @@
<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ============================================================================= -->
+<!-- Copyright © 2009 Red Hat, Inc. and others. -->
+<!-- -->
+<!-- The text of and illustrations in this document are licensed by Red Hat under -->
+<!-- a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). -->
+<!-- -->
+<!-- An explanation of CC-BY-SA is available at -->
+<!-- -->
+<!-- http://creativecommons.org/licenses/by-sa/3.0/. -->
+<!-- -->
+<!-- In accordance with CC-BY-SA, if you distribute this document or an adaptation -->
+<!-- of it, you must provide the URL for the original version. -->
+<!-- -->
+<!-- Red Hat, as the licensor of this document, waives the right to enforce, -->
+<!-- and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent -->
+<!-- permitted by applicable law. -->
+<!-- ============================================================================= -->
+
<chapter id="project-info">
<title>Project Information</title>
- <para>The HornetQ project page is <ulink url="http://www.hornetq.org"
- >here</ulink>. You can download any releases from there.</para>
- <para>If you have any user questions please use our <ulink
- url="http://www.jboss.org/index.html?module=bb&op=viewforum&f=238">user
- forum</ulink></para>
- <para>If you have development related questions, please use our <ulink
- url="http://www.jboss.org/index.html?module=bb&op=viewforum&f=153">development
- forum</ulink></para>
- <para>Pop in and chat to us in our <ulink url="irc://irc.freenode.net:6667/hornetq">IRC channel</ulink></para>
- <para>HornetQ Subversion TRUNK is <ulink url="http://anonsvn.jboss.org/repos/messaging/trunk">here</ulink></para>
- <para>All our release tags are <ulink url="http://anonsvn.jboss.org/repos/messaging/tags">here</ulink></para>
+ <para>The official HornetQ project page is <ulink
+ url="http://hornetq.org/">http://hornetq.org/</ulink>.</para>
+
+ <section id="download.software">
+ <title>Software Download</title>
+ <para>The software can be download from the Download page:<ulink
+ url="http://hornetq.org/downloads.html">http://hornetq.org/downloads.html</ulink></para>
+ </section>
+
+ <section id="download.svn">
+ <title>Project Information</title>
+ <para>If you have any user questions please use our <ulink
+ url="http://n2.nabble.com/hornetq-users-f3404100.html">user
+ forum</ulink></para>
+ <para>If you have development related questions, please use our <ulink
+ url="http://n2.nabble.com/hornetq-dev-f3404069.html">development
+ forum</ulink></para>
+ <para>Pop in and chat to us in our <ulink url="irc://irc.freenode.net:6667/hornetq">IRC channel</ulink></para>
+ <para>HornetQ Subversion trunk is <ulink url="http://anonsvn.jboss.org/repos/hornetq/trunk">http://anonsvn.jboss.org/repos/hornetq/trunk</ulink></para>
+ <para>All release tags are availble from <ulink url="http://anonsvn.jboss.org/repos/hornetq/tags">http://anonsvn.jboss.org/repos/hornetq/tags</ulink></para>
+ </section>
<para>Red Hat kindly employs developers to work full time on HornetQ, the motley crew are:
<itemizedlist>
<listitem><para> <ulink url="http://jbossfox.blogspot.com">Tim Fox</ulink> (project lead)</para></listitem>
<listitem><para>Howard Gao</para></listitem>
- <listitem><para>Jeff Mesnil</para></listitem>
+ <listitem><para><ulink url="http://jmesnil.net/weblog/">Jeff Mesnil</ulink></para></listitem>
<listitem><para>Clebert Suconic</para></listitem>
<listitem><para>Andy Taylor</para></listitem>
</itemizedlist>
Modified: trunk/docs/user-manual/en/queue-attributes.xml
===================================================================
--- trunk/docs/user-manual/en/queue-attributes.xml 2009-08-21 09:35:43 UTC (rev 7856)
+++ trunk/docs/user-manual/en/queue-attributes.xml 2009-08-21 09:38:07 UTC (rev 7857)
@@ -1,4 +1,23 @@
<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ============================================================================= -->
+<!-- Copyright © 2009 Red Hat, Inc. and others. -->
+<!-- -->
+<!-- The text of and illustrations in this document are licensed by Red Hat under -->
+<!-- a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). -->
+<!-- -->
+<!-- An explanation of CC-BY-SA is available at -->
+<!-- -->
+<!-- http://creativecommons.org/licenses/by-sa/3.0/. -->
+<!-- -->
+<!-- In accordance with CC-BY-SA, if you distribute this document or an adaptation -->
+<!-- of it, you must provide the URL for the original version. -->
+<!-- -->
+<!-- Red Hat, as the licensor of this document, waives the right to enforce, -->
+<!-- and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent -->
+<!-- permitted by applicable law. -->
+<!-- ============================================================================= -->
+
<chapter id="queue-attributes">
<title>Queue Attributes</title>
<para>Queue attributes can be set in one of two ways. Either by configuring them using the
Modified: trunk/docs/user-manual/en/scheduled-messages.xml
===================================================================
--- trunk/docs/user-manual/en/scheduled-messages.xml 2009-08-21 09:35:43 UTC (rev 7856)
+++ trunk/docs/user-manual/en/scheduled-messages.xml 2009-08-21 09:38:07 UTC (rev 7857)
@@ -1,4 +1,23 @@
<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ============================================================================= -->
+<!-- Copyright © 2009 Red Hat, Inc. and others. -->
+<!-- -->
+<!-- The text of and illustrations in this document are licensed by Red Hat under -->
+<!-- a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). -->
+<!-- -->
+<!-- An explanation of CC-BY-SA is available at -->
+<!-- -->
+<!-- http://creativecommons.org/licenses/by-sa/3.0/. -->
+<!-- -->
+<!-- In accordance with CC-BY-SA, if you distribute this document or an adaptation -->
+<!-- of it, you must provide the URL for the original version. -->
+<!-- -->
+<!-- Red Hat, as the licensor of this document, waives the right to enforce, -->
+<!-- and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent -->
+<!-- permitted by applicable law. -->
+<!-- ============================================================================= -->
+
<chapter id="scheduled-messages">
<title>Scheduled Messages</title>
<para>Scheduled messages differ from normal messages in that they won't be delivered until a
Modified: trunk/docs/user-manual/en/security.xml
===================================================================
--- trunk/docs/user-manual/en/security.xml 2009-08-21 09:35:43 UTC (rev 7856)
+++ trunk/docs/user-manual/en/security.xml 2009-08-21 09:38:07 UTC (rev 7857)
@@ -1,4 +1,23 @@
<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ============================================================================= -->
+<!-- Copyright © 2009 Red Hat, Inc. and others. -->
+<!-- -->
+<!-- The text of and illustrations in this document are licensed by Red Hat under -->
+<!-- a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). -->
+<!-- -->
+<!-- An explanation of CC-BY-SA is available at -->
+<!-- -->
+<!-- http://creativecommons.org/licenses/by-sa/3.0/. -->
+<!-- -->
+<!-- In accordance with CC-BY-SA, if you distribute this document or an adaptation -->
+<!-- of it, you must provide the URL for the original version. -->
+<!-- -->
+<!-- Red Hat, as the licensor of this document, waives the right to enforce, -->
+<!-- and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent -->
+<!-- permitted by applicable law. -->
+<!-- ============================================================================= -->
+
<chapter id="security">
<title>Security</title>
<para>This chapter describes how security works with HornetQ and how you can configure
@@ -184,7 +203,7 @@
default security manager that reads used by the standalone server.</para>
<para>HornetQ ships with two other security manager implementations you can use
off-the-shelf; one a JAAS security manager and another for integrating with JBoss
- Application Server security, alternatively you could write your own implementation by
+ Application Sever security, alternatively you could write your own implementation by
implementing the <literal>org.hornetq.core.security.SecurityManager</literal>
interface, and specifying the classname of your implementation in the <literal
>hornetq-jboss-beans.xml</literal> file.</para>
Modified: trunk/docs/user-manual/en/send-guarantees.xml
===================================================================
--- trunk/docs/user-manual/en/send-guarantees.xml 2009-08-21 09:35:43 UTC (rev 7856)
+++ trunk/docs/user-manual/en/send-guarantees.xml 2009-08-21 09:38:07 UTC (rev 7857)
@@ -1,4 +1,23 @@
<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ============================================================================= -->
+<!-- Copyright © 2009 Red Hat, Inc. and others. -->
+<!-- -->
+<!-- The text of and illustrations in this document are licensed by Red Hat under -->
+<!-- a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). -->
+<!-- -->
+<!-- An explanation of CC-BY-SA is available at -->
+<!-- -->
+<!-- http://creativecommons.org/licenses/by-sa/3.0/. -->
+<!-- -->
+<!-- In accordance with CC-BY-SA, if you distribute this document or an adaptation -->
+<!-- of it, you must provide the URL for the original version. -->
+<!-- -->
+<!-- Red Hat, as the licensor of this document, waives the right to enforce, -->
+<!-- and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent -->
+<!-- permitted by applicable law. -->
+<!-- ============================================================================= -->
+
<chapter id="send-guarantees">
<title>Guarantees of Transactional and Non-Transactional Sends and Asynchronous Send
Acknowledgements</title>
@@ -24,7 +43,8 @@
</section>
<section id="non-transactional-sends">
<title>Guarantees of Non Transactional Message Sends</title>
- <para>If you are sending messages to a server using a non transacted session, HornetQ can be configured to block the call to send until the message has definitely
+ <para>If you are sending messages to a server using a non transacted session, HornetQ
+ can be configured to block the call to send until the message has definitely
reached the server, and a response has been sent back to the client. This can be
configured individually for persistent and non-persistent messages, and is determined by
the following two parameters:</para>
@@ -49,7 +69,8 @@
performance of sending messages will be limited by the network round trip time (RTT) of
your network, rather than the bandwidth of your network. For better performance we
recommend either batching many messages sends together in a transaction since with a
- transactional session, only the commit / rollback blocks not every send, or, using HornetQ's advanced <emphasis>asynchronous send acknowledgements feature</emphasis>
+ transactional session, only the commit / rollback blocks not every send, or, using HornetQ's
+ advanced <emphasis>asynchronous send acknowledgements feature</emphasis>
described in <xref linkend="asynchronous-send-acknowledgements" />.</para>
<para>If you are using JMS and you're using the JMS service on the server to load your JMS
connection factory instances into JNDI then these parameters can be configured in
@@ -103,7 +124,8 @@
blocking! These figures aren't an exact science but you can clearly see that being
limited by network RTT can have serious effect on performance.</para>
<para>To remedy this, HornetQ provides an advanced new feature called
- <emphasis>asynchronous send acknowledgements</emphasis>. With this feature, HornetQ can be configured to send messages without blocking in one direction and
+ <emphasis>asynchronous send acknowledgements</emphasis>. With this feature, HornetQ
+ can be configured to send messages without blocking in one direction and
asynchronously getting acknowledgement from the server that the messages were received
in a separate stream. By de-coupling the send from the acknowledgement of the send, the
system is not limited by the network RTT, but is limited by the network bandwidth.
Modified: trunk/docs/user-manual/en/thread-pooling.xml
===================================================================
--- trunk/docs/user-manual/en/thread-pooling.xml 2009-08-21 09:35:43 UTC (rev 7856)
+++ trunk/docs/user-manual/en/thread-pooling.xml 2009-08-21 09:38:07 UTC (rev 7857)
@@ -1,4 +1,23 @@
<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ============================================================================= -->
+<!-- Copyright © 2009 Red Hat, Inc. and others. -->
+<!-- -->
+<!-- The text of and illustrations in this document are licensed by Red Hat under -->
+<!-- a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). -->
+<!-- -->
+<!-- An explanation of CC-BY-SA is available at -->
+<!-- -->
+<!-- http://creativecommons.org/licenses/by-sa/3.0/. -->
+<!-- -->
+<!-- In accordance with CC-BY-SA, if you distribute this document or an adaptation -->
+<!-- of it, you must provide the URL for the original version. -->
+<!-- -->
+<!-- Red Hat, as the licensor of this document, waives the right to enforce, -->
+<!-- and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent -->
+<!-- permitted by applicable law. -->
+<!-- ============================================================================= -->
+
<chapter id="thread-pooling">
<title>Thread management</title>
<para>This chapter describes how HornetQ uses and pools threads and how you can manage
Modified: trunk/docs/user-manual/en/transaction-config.xml
===================================================================
--- trunk/docs/user-manual/en/transaction-config.xml 2009-08-21 09:35:43 UTC (rev 7856)
+++ trunk/docs/user-manual/en/transaction-config.xml 2009-08-21 09:38:07 UTC (rev 7857)
@@ -1,4 +1,23 @@
<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ============================================================================= -->
+<!-- Copyright © 2009 Red Hat, Inc. and others. -->
+<!-- -->
+<!-- The text of and illustrations in this document are licensed by Red Hat under -->
+<!-- a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). -->
+<!-- -->
+<!-- An explanation of CC-BY-SA is available at -->
+<!-- -->
+<!-- http://creativecommons.org/licenses/by-sa/3.0/. -->
+<!-- -->
+<!-- In accordance with CC-BY-SA, if you distribute this document or an adaptation -->
+<!-- of it, you must provide the URL for the original version. -->
+<!-- -->
+<!-- Red Hat, as the licensor of this document, waives the right to enforce, -->
+<!-- and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent -->
+<!-- permitted by applicable law. -->
+<!-- ============================================================================= -->
+
<chapter id="transaction-config">
<title>Resource Manager Configuration</title>
<para>HornetQ has its own Resource Manager for handling the lifespan of XA transactions.
Modified: trunk/docs/user-manual/en/undelivered-messages.xml
===================================================================
--- trunk/docs/user-manual/en/undelivered-messages.xml 2009-08-21 09:35:43 UTC (rev 7856)
+++ trunk/docs/user-manual/en/undelivered-messages.xml 2009-08-21 09:38:07 UTC (rev 7857)
@@ -1,4 +1,23 @@
<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ============================================================================= -->
+<!-- Copyright © 2009 Red Hat, Inc. and others. -->
+<!-- -->
+<!-- The text of and illustrations in this document are licensed by Red Hat under -->
+<!-- a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). -->
+<!-- -->
+<!-- An explanation of CC-BY-SA is available at -->
+<!-- -->
+<!-- http://creativecommons.org/licenses/by-sa/3.0/. -->
+<!-- -->
+<!-- In accordance with CC-BY-SA, if you distribute this document or an adaptation -->
+<!-- of it, you must provide the URL for the original version. -->
+<!-- -->
+<!-- Red Hat, as the licensor of this document, waives the right to enforce, -->
+<!-- and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent -->
+<!-- permitted by applicable law. -->
+<!-- ============================================================================= -->
+
<chapter id="undelivered-messages">
<title>Message Redelivery and Undelivered Messages</title>
<para>Messages can be delivered unsuccessfully (e.g. if the transacted session used to consume
Modified: trunk/docs/user-manual/en/using-core.xml
===================================================================
--- trunk/docs/user-manual/en/using-core.xml 2009-08-21 09:35:43 UTC (rev 7856)
+++ trunk/docs/user-manual/en/using-core.xml 2009-08-21 09:38:07 UTC (rev 7857)
@@ -1,4 +1,23 @@
<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ============================================================================= -->
+<!-- Copyright © 2009 Red Hat, Inc. and others. -->
+<!-- -->
+<!-- The text of and illustrations in this document are licensed by Red Hat under -->
+<!-- a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). -->
+<!-- -->
+<!-- An explanation of CC-BY-SA is available at -->
+<!-- -->
+<!-- http://creativecommons.org/licenses/by-sa/3.0/. -->
+<!-- -->
+<!-- In accordance with CC-BY-SA, if you distribute this document or an adaptation -->
+<!-- of it, you must provide the URL for the original version. -->
+<!-- -->
+<!-- Red Hat, as the licensor of this document, waives the right to enforce, -->
+<!-- and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent -->
+<!-- permitted by applicable law. -->
+<!-- ============================================================================= -->
+
<chapter id="using-core">
<title>Using Core</title>
<para>HornetQ core is a completely JMS-agnostic messaging system with its own core
Modified: trunk/docs/user-manual/en/using-jms.xml
===================================================================
--- trunk/docs/user-manual/en/using-jms.xml 2009-08-21 09:35:43 UTC (rev 7856)
+++ trunk/docs/user-manual/en/using-jms.xml 2009-08-21 09:38:07 UTC (rev 7857)
@@ -1,4 +1,23 @@
<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ============================================================================= -->
+<!-- Copyright © 2009 Red Hat, Inc. and others. -->
+<!-- -->
+<!-- The text of and illustrations in this document are licensed by Red Hat under -->
+<!-- a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). -->
+<!-- -->
+<!-- An explanation of CC-BY-SA is available at -->
+<!-- -->
+<!-- http://creativecommons.org/licenses/by-sa/3.0/. -->
+<!-- -->
+<!-- In accordance with CC-BY-SA, if you distribute this document or an adaptation -->
+<!-- of it, you must provide the URL for the original version. -->
+<!-- -->
+<!-- Red Hat, as the licensor of this document, waives the right to enforce, -->
+<!-- and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent -->
+<!-- permitted by applicable law. -->
+<!-- ============================================================================= -->
+
<chapter id="using-jms">
<title>Using JMS</title>
<para>Although HornetQ provides a JMS agnostic messaging API, many users will be more
@@ -88,7 +107,7 @@
is the port used by the JNDI server and may vary depending on how you have configured
your JNDI server.</para>
<para>In the default standalone configuration, JNDI server ports are configured in the
- <literal>hornetq-jboss-beans.xml</literal> file where the JNDIServer bean is confgured,
+ <literal>hornetq-jboss-beans.xml</literal> file where the JNDIServer bean is configured,
here's a snippet from the file:</para>
<programlisting>
<bean name="JNDIServer" class="org.jnp.server.Main">
Modified: trunk/docs/user-manual/en/using-server.xml
===================================================================
--- trunk/docs/user-manual/en/using-server.xml 2009-08-21 09:35:43 UTC (rev 7856)
+++ trunk/docs/user-manual/en/using-server.xml 2009-08-21 09:38:07 UTC (rev 7857)
@@ -1,4 +1,23 @@
<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ============================================================================= -->
+<!-- Copyright © 2009 Red Hat, Inc. and others. -->
+<!-- -->
+<!-- The text of and illustrations in this document are licensed by Red Hat under -->
+<!-- a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). -->
+<!-- -->
+<!-- An explanation of CC-BY-SA is available at -->
+<!-- -->
+<!-- http://creativecommons.org/licenses/by-sa/3.0/. -->
+<!-- -->
+<!-- In accordance with CC-BY-SA, if you distribute this document or an adaptation -->
+<!-- of it, you must provide the URL for the original version. -->
+<!-- -->
+<!-- Red Hat, as the licensor of this document, waives the right to enforce, -->
+<!-- and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent -->
+<!-- permitted by applicable law. -->
+<!-- ============================================================================= -->
+
<chapter id="using-server">
<title>Using the Server</title>
<para>This chapter will familiarise you with how to use the HornetQ server.</para>
Modified: trunk/docs/user-manual/en/wildcard-routing.xml
===================================================================
--- trunk/docs/user-manual/en/wildcard-routing.xml 2009-08-21 09:35:43 UTC (rev 7856)
+++ trunk/docs/user-manual/en/wildcard-routing.xml 2009-08-21 09:38:07 UTC (rev 7857)
@@ -1,4 +1,23 @@
<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ============================================================================= -->
+<!-- Copyright © 2009 Red Hat, Inc. and others. -->
+<!-- -->
+<!-- The text of and illustrations in this document are licensed by Red Hat under -->
+<!-- a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). -->
+<!-- -->
+<!-- An explanation of CC-BY-SA is available at -->
+<!-- -->
+<!-- http://creativecommons.org/licenses/by-sa/3.0/. -->
+<!-- -->
+<!-- In accordance with CC-BY-SA, if you distribute this document or an adaptation -->
+<!-- of it, you must provide the URL for the original version. -->
+<!-- -->
+<!-- Red Hat, as the licensor of this document, waives the right to enforce, -->
+<!-- and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent -->
+<!-- permitted by applicable law. -->
+<!-- ============================================================================= -->
+
<chapter id="wildcard-routing">
<title>Routing Messages With Wild Cards</title>
<para>HornetQ allows the routing of messages via wildcard addresses.</para>
Modified: trunk/docs/user-manual/en/wildcard-syntax.xml
===================================================================
--- trunk/docs/user-manual/en/wildcard-syntax.xml 2009-08-21 09:35:43 UTC (rev 7856)
+++ trunk/docs/user-manual/en/wildcard-syntax.xml 2009-08-21 09:38:07 UTC (rev 7857)
@@ -1,4 +1,23 @@
<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ============================================================================= -->
+<!-- Copyright © 2009 Red Hat, Inc. and others. -->
+<!-- -->
+<!-- The text of and illustrations in this document are licensed by Red Hat under -->
+<!-- a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). -->
+<!-- -->
+<!-- An explanation of CC-BY-SA is available at -->
+<!-- -->
+<!-- http://creativecommons.org/licenses/by-sa/3.0/. -->
+<!-- -->
+<!-- In accordance with CC-BY-SA, if you distribute this document or an adaptation -->
+<!-- of it, you must provide the URL for the original version. -->
+<!-- -->
+<!-- Red Hat, as the licensor of this document, waives the right to enforce, -->
+<!-- and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent -->
+<!-- permitted by applicable law. -->
+<!-- ============================================================================= -->
+
<chapter id="wildcard-syntax">
<title>Understanding the HornetQ Wildcard Syntax</title>
<para>HornetQ uses a specific syntax for representing wildcards in security settings,
More information about the hornetq-commits
mailing list