August 2009 - hornetq-commits - Jboss List Archives

by do-not-reply＠jboss.org

Author: clebert.suconic(a)jboss.com Date: 2009-08-20 12:30:30 -0400 (Thu, 20 Aug 2009) New Revision: 7832 Modified: trunk/build-hornetq.xml Log: fixing javadoc build Modified: trunk/build-hornetq.xml =================================================================== --- trunk/build-hornetq.xml 2009-08-20 16:14:32 UTC (rev 7831) +++ trunk/build-hornetq.xml 2009-08-20 16:30:30 UTC (rev 7832) @@ -903,7 +903,7 @@ windowtitle="HornetQ ${module.version}"> <packageset dir="${src.main.dir}" defaultexcludes="yes"> - <include name="org/jboss/**"/> + <include name="org/hornetq/**"/> </packageset> <classpath refid="javadoc.classpath"/> <doctitle><![CDATA[<h2>HornetQ ${module.version}</h2>]]></doctitle>

15 years, 6 months

1
0
0 / 0

JBoss hornetq SVN: r7830 - in trunk: docs and 117 other directories.

by do-not-reply＠jboss.org

Author: timfox Date: 2009-08-20 11:17:39 -0400 (Thu, 20 Aug 2009) New Revision: 7830 Modified: trunk/NOTICE trunk/build-hornetq.xml trunk/build.xml trunk/docs/README.html trunk/docs/quickstart-guide/en/about.xml trunk/docs/quickstart-guide/en/download.xml trunk/docs/quickstart-guide/en/examples.xml trunk/docs/quickstart-guide/en/installation.xml trunk/docs/quickstart-guide/en/introduction.xml trunk/docs/quickstart-guide/en/master.xml trunk/docs/quickstart-guide/en/running.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/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-jbm.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/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/preface.xml trunk/docs/user-manual/en/project-info.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 trunk/examples/core/embedded-remote/build.xml trunk/examples/core/embedded-remote/readme.html trunk/examples/core/embedded-remote/src/org/hornetq/core/example/EmbeddedRemoteExample.java trunk/examples/core/embedded/build.xml trunk/examples/core/embedded/readme.html trunk/examples/core/embedded/src/org/hornetq/core/example/EmbeddedExample.java trunk/examples/core/microcontainer/build.xml trunk/examples/core/microcontainer/readme.html trunk/examples/core/microcontainer/src/org/hornetq/core/example/EmbeddedMicroContainerExample.java trunk/examples/core/perf/build.xml trunk/examples/javaee/ejb-jms-transaction/build.xml trunk/examples/javaee/ejb-jms-transaction/readme.html trunk/examples/javaee/hajndi/build.xml trunk/examples/javaee/hajndi/readme.html trunk/examples/javaee/jca-config/build.xml trunk/examples/javaee/jca-config/readme.html trunk/examples/javaee/jca-config/server2/ra.xml trunk/examples/javaee/jms-bridge/build.xml trunk/examples/javaee/jms-bridge/readme.html trunk/examples/javaee/jms-bridge/server/jms-bridge-jboss-beans.xml trunk/examples/javaee/mdb-bmt/build.xml trunk/examples/javaee/mdb-bmt/readme.html trunk/examples/javaee/mdb-cmt-setrollbackonly/build.xml trunk/examples/javaee/mdb-cmt-setrollbackonly/readme.html trunk/examples/javaee/mdb-cmt-tx-local/build.xml trunk/examples/javaee/mdb-cmt-tx-local/readme.html trunk/examples/javaee/mdb-cmt-tx-not-supported/build.xml trunk/examples/javaee/mdb-cmt-tx-not-supported/readme.html trunk/examples/javaee/mdb-cmt-tx-required/build.xml trunk/examples/javaee/mdb-cmt-tx-required/readme.html trunk/examples/javaee/mdb-message-selector/build.xml trunk/examples/javaee/mdb-message-selector/readme.html trunk/examples/javaee/mdb-tx-send/build.xml trunk/examples/javaee/mdb-tx-send/readme.html trunk/examples/javaee/servlet-ssl-example/build.xml trunk/examples/javaee/servlet-ssl-example/readme.html trunk/examples/javaee/servlet-transport/build.xml trunk/examples/javaee/servlet-transport/readme.html trunk/examples/javaee/xarecovery/build.xml trunk/examples/javaee/xarecovery/readme.html trunk/examples/jms/application-layer-failover/build.xml trunk/examples/jms/application-layer-failover/readme.html trunk/examples/jms/automatic-failover/build.xml trunk/examples/jms/automatic-failover/readme.html trunk/examples/jms/bridge/build.xml trunk/examples/jms/bridge/readme.html trunk/examples/jms/browser/build.xml trunk/examples/jms/browser/readme.html trunk/examples/jms/client-kickoff/build.xml trunk/examples/jms/client-kickoff/readme.html trunk/examples/jms/client-kickoff/server0/hornetq-configuration.xml trunk/examples/jms/client-kickoff/src/org/hornetq/jms/example/ClientKickoffExample.java trunk/examples/jms/client-side-load-balancing/build.xml trunk/examples/jms/client-side-load-balancing/readme.html trunk/examples/jms/clustered-durable-subscription/build.xml trunk/examples/jms/clustered-durable-subscription/readme.html trunk/examples/jms/clustered-queue/build.xml trunk/examples/jms/clustered-queue/readme.html trunk/examples/jms/clustered-standalone/build.xml trunk/examples/jms/clustered-standalone/readme.html trunk/examples/jms/clustered-topic/build.xml trunk/examples/jms/clustered-topic/readme.html trunk/examples/jms/consumer-rate-limit/build.xml trunk/examples/jms/consumer-rate-limit/readme.html trunk/examples/jms/dead-letter/build.xml trunk/examples/jms/dead-letter/readme.html trunk/examples/jms/dead-letter/src/org/hornetq/jms/example/DeadLetterExample.java trunk/examples/jms/delayed-redelivery/build.xml trunk/examples/jms/delayed-redelivery/readme.html trunk/examples/jms/delayed-redelivery/src/org/hornetq/jms/example/DelayedRedeliveryExample.java trunk/examples/jms/divert/build.xml trunk/examples/jms/divert/readme.html trunk/examples/jms/divert/src/org/hornetq/jms/example/DivertExample.java trunk/examples/jms/durable-subscription/build.xml trunk/examples/jms/durable-subscription/readme.html trunk/examples/jms/embedded/build.xml trunk/examples/jms/embedded/readme.html trunk/examples/jms/embedded/src/org/hornetq/jms/example/EmbeddedExample.java trunk/examples/jms/expiry/build.xml trunk/examples/jms/expiry/readme.html trunk/examples/jms/expiry/src/org/hornetq/jms/example/ExpiryExample.java trunk/examples/jms/http-transport/build.xml trunk/examples/jms/http-transport/readme.html trunk/examples/jms/instantiate-connection-factory/build.xml trunk/examples/jms/instantiate-connection-factory/readme.html trunk/examples/jms/interceptor/build.xml trunk/examples/jms/interceptor/readme.html trunk/examples/jms/interceptor/src/org/hornetq/jms/example/InterceptorExample.java trunk/examples/jms/jaas/build.xml trunk/examples/jms/jaas/readme.html trunk/examples/jms/jmx/build.xml trunk/examples/jms/jmx/readme.html trunk/examples/jms/jmx/server0/hornetq-configuration.xml trunk/examples/jms/jmx/src/org/hornetq/jms/example/JMXExample.java trunk/examples/jms/large-message/build.xml trunk/examples/jms/large-message/readme.html trunk/examples/jms/large-message/src/org/hornetq/jms/example/LargeMessageExample.java trunk/examples/jms/last-value-queue/build.xml trunk/examples/jms/last-value-queue/readme.html trunk/examples/jms/management-notifications/build.xml trunk/examples/jms/management-notifications/readme.html trunk/examples/jms/management/build.xml trunk/examples/jms/management/readme.html trunk/examples/jms/management/src/org/hornetq/jms/example/ManagementExample.java trunk/examples/jms/message-counters/build.xml trunk/examples/jms/message-counters/readme.html trunk/examples/jms/message-group/build.xml trunk/examples/jms/message-group/readme.html trunk/examples/jms/message-priority/build.xml trunk/examples/jms/message-priority/readme.html trunk/examples/jms/no-consumer-buffering/build.xml trunk/examples/jms/no-consumer-buffering/readme.html trunk/examples/jms/no-consumer-buffering/src/org/hornetq/jms/example/NoConsumerBufferingExample.java trunk/examples/jms/paging/build.xml trunk/examples/jms/paging/readme.html trunk/examples/jms/perf/build.xml trunk/examples/jms/pre-acknowledge/build.xml trunk/examples/jms/pre-acknowledge/readme.html trunk/examples/jms/pre-acknowledge/src/org/hornetq/jms/example/PreacknowledgeExample.java trunk/examples/jms/producer-rate-limit/build.xml trunk/examples/jms/producer-rate-limit/readme.html trunk/examples/jms/queue-message-redistribution/build.xml trunk/examples/jms/queue-message-redistribution/readme.html trunk/examples/jms/queue-message-redistribution/src/org/hornetq/jms/example/QueueMessageRedistributionExample.java trunk/examples/jms/queue-requestor/build.xml trunk/examples/jms/queue-requestor/readme.html trunk/examples/jms/queue-selector/build.xml trunk/examples/jms/queue-selector/readme.html trunk/examples/jms/queue/build.xml trunk/examples/jms/queue/readme.html trunk/examples/jms/reconnect-same-node/build.xml trunk/examples/jms/reconnect-same-node/readme.html trunk/examples/jms/request-reply/build.xml trunk/examples/jms/request-reply/readme.html trunk/examples/jms/scheduled-message/build.xml trunk/examples/jms/scheduled-message/readme.html trunk/examples/jms/security/build.xml trunk/examples/jms/security/readme.html trunk/examples/jms/send-acknowledgements/build.xml trunk/examples/jms/send-acknowledgements/readme.html trunk/examples/jms/send-acknowledgements/src/org/hornetq/jms/example/SendAcknowledgementsExample.java trunk/examples/jms/ssl-enabled/build.xml trunk/examples/jms/ssl-enabled/readme.html trunk/examples/jms/static-selector-jms/build.xml trunk/examples/jms/static-selector-jms/readme.html trunk/examples/jms/static-selector/build.xml trunk/examples/jms/static-selector/readme.html trunk/examples/jms/symmetric-cluster/build.xml trunk/examples/jms/symmetric-cluster/readme.html trunk/examples/jms/symmetric-cluster/src/org/hornetq/jms/example/SymmetricClusterExample.java trunk/examples/jms/temp-queue/build.xml trunk/examples/jms/temp-queue/readme.html trunk/examples/jms/topic-hierarchies/build.xml trunk/examples/jms/topic-hierarchies/readme.html trunk/examples/jms/topic-selector-example1/build.xml trunk/examples/jms/topic-selector-example1/readme.html trunk/examples/jms/topic-selector-example2/build.xml trunk/examples/jms/topic-selector-example2/readme.html trunk/examples/jms/topic/build.xml trunk/examples/jms/topic/readme.html trunk/examples/jms/transactional/build.xml trunk/examples/jms/transactional/readme.html trunk/examples/jms/xa-heuristic/build.xml trunk/examples/jms/xa-heuristic/readme.html trunk/examples/jms/xa-receive/build.xml trunk/examples/jms/xa-receive/readme.html trunk/examples/jms/xa-send/build.xml trunk/examples/jms/xa-send/readme.html trunk/examples/jms/xa-with-jta/build.xml trunk/examples/jms/xa-with-jta/readme.html trunk/examples/jms/xa-with-jta/src/org/hornetq/jms/example/XAwithJTAExample.java trunk/examples/soak/normal/build.xml trunk/src/config/jboss-as/build.xml trunk/src/config/ra.xml trunk/src/main/org/hornetq/core/buffers/package.html trunk/src/main/org/hornetq/core/filter/impl/FilterImpl.java trunk/src/main/org/hornetq/core/management/impl/ManagementServiceImpl.java trunk/src/main/org/hornetq/core/management/package.html trunk/src/main/org/hornetq/core/remoting/Interceptor.java trunk/src/main/org/hornetq/core/server/impl/MessagingServerImpl.java trunk/src/main/org/hornetq/core/transaction/Transaction.java trunk/src/main/org/hornetq/integration/bootstrap/HornetQBootstrapServer.java trunk/src/main/org/hornetq/jms/bridge/QualityOfServiceMode.java trunk/src/main/org/hornetq/jms/client/HornetQConnectionMetaData.java trunk/src/main/org/hornetq/jms/client/HornetQTextMessage.java trunk/src/main/org/hornetq/ra/HornetQRAConnectionMetaData.java trunk/src/main/org/hornetq/ra/HornetQRAMetaData.java trunk/src/main/org/hornetq/ra/HornetQResourceAdapter.java trunk/src/main/org/hornetq/ra/package.html trunk/tests/jms-tests/src/org/hornetq/jmstests/message/foreign/ForeignBytesMessageTest.java trunk/tests/jms-tests/src/org/hornetq/jmstests/tools/ant/GenerateSmokeReport.java trunk/tests/src/org/hornetq/tests/unit/core/filter/impl/FilterParserTest.java trunk/tests/src/org/hornetq/tests/unit/core/filter/impl/FilterTest.java Log: replaced a load of JBoss Messaging references Modified: trunk/NOTICE =================================================================== --- trunk/NOTICE 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/NOTICE 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,14 +1,14 @@ -JBoss Messaging +HornetQ Copyright 2009 Red Hat, Inc. Licensed under the Apache License, version 2.0. -Unless required by applicable law, JBoss Messaging is distributed on +Unless required by applicable law, HornetQ is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OF ANY KIND, either express or implied, including the implied warranties of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. -Certain portions of JBoss Messaging are based on code made available +Certain portions of HornetQ are based on code made available under the GNU Lesser General Public License, version 2.1 or later (http://www.fsf.org/licensing/licenses/lgpl.html). "JBoss" and "Red Hat" are trademarks of Red Hat, Inc. and/or its affiliates, registered in the U.S. and other countries. Your -permissions under the licensing terms governing JBoss Messaging do +permissions under the licensing terms governing HornetQ do not include a license, express or implied, to any Red Hat trademark. \ No newline at end of file Modified: trunk/build-hornetq.xml =================================================================== --- trunk/build-hornetq.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/build-hornetq.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -18,7 +18,6 @@ <project default="jar" name="The HornetQ Project"> -    @@ -901,17 +900,17 @@ <target name="javadoc"> <javadoc destdir="${build.api.dir}" author="true" version="true" use="true" - windowtitle="JBoss Messaging ${module.version}"> + windowtitle="HornetQ ${module.version}"> <packageset dir="${src.main.dir}" defaultexcludes="yes"> <include name="org/jboss/**"/> </packageset> <classpath refid="javadoc.classpath"/> - <doctitle><![CDATA[<h2>JBoss Messaging ${module.version}</h2>]]></doctitle> - <bottom><![CDATA[<i>Copyright © 2006 JBoss Inc. All Rights Reserved.</i>]]></bottom> + <doctitle><![CDATA[<h2>HornetQ ${module.version}</h2>]]></doctitle> + <bottom><![CDATA[<i>Copyright © 2009 Red Hat Inc. All Rights Reserved.</i>]]></bottom> <tag name="todo" scope="all" description="To do:"/> <group title="JMS Facade" packages="org.jboss.jms.*"/> - <group title="Messaging Core" packages="org.hornetq.*"/> + <group title="HornetQ Core" packages="org.hornetq.*"/> </javadoc> </target> Modified: trunk/build.xml =================================================================== --- trunk/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -22,7 +22,7 @@  -<project default="unit-tests" name="JBoss Messaging"> +<project default="unit-tests" name="HornetQ">  +  <depends>MessagingServer</depends> <constructor>  @@ -956,7 +956,7 @@ <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 JBoss Messaging server instance then + 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. @@ -995,15 +995,15 @@ 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 JBoss Messaging is integrated with JBoss AS, it can take advantage of JBoss + <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 JBoss Messagings XA Recovery, the Recovery Manager must be configured to - connect to JBoss Messaging to recover its resources. The following property must be + <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> @@ -1015,7 +1015,7 @@ </properties> </programlisting> <para>The <literal>[connection configuration]</literal> contains all the information - required to connect to JBoss Messaging node under the form <literal>[connector + required to connect to HornetQ node under the form <literal>[connector factory class name],[user name], [password], [connector parameters]</literal>. </para> <itemizedlist> <listitem> @@ -1042,12 +1042,12 @@ </listitem> </itemizedlist> <note> - <para>JBoss Messaging must have a valid acceptor which corresponds to the connector + <para>HornetQ must have a valid acceptor which corresponds to the connector specified in <literal>conf/jbossts-properties.xml</literal>.</para> </note> <section> <title>Configuration Settings</title> - <para>If JBoss Messaging is configured with a default in-vm acceptor:</para> + <para>If HornetQ is configured with a default in-vm acceptor:</para> <programlisting> <acceptor name="in-vm"> <factory-class>org.hornetq.core.remoting.impl.invm.InVMAcceptorFactory</factory-class> @@ -1082,7 +1082,7 @@ <property name="com.arjuna.ats.jta.recovery.XAResourceRecovery.JBMESSAGING1" value="org.hornetq.jms.server.recovery.MessagingXAResourceRecovery;org.hornetq.integration.transports.netty.NettyConnectorFactory, admin, adminpass, hornetq.remoting.netty.port=8888"/> </programlisting> - <para>Configuring JBoss Messaging with an invm acceptor and configuring the Recovery + <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> Modified: trunk/docs/user-manual/en/architecture.xml =================================================================== --- trunk/docs/user-manual/en/architecture.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/docs/user-manual/en/architecture.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,24 +1,24 @@ <?xml version="1.0" encoding="UTF-8"?> <chapter id="architecture"> <title>Architecture</title> - <para>In this section we will give an overview of the JBoss Messaging high level + <para>In this section we will give an overview of the HornetQ high level architecture.</para> <section> <title>Core Architecture</title> - <para>JBoss Messaging core is designed simply as set of Plain Old Java Objects + <para>HornetQ core is designed simply as set of Plain Old Java Objects (POJOs).</para> <para>We've also designed it to have as few dependencies on external jars as possible. In - fact, JBoss Messaging core has <emphasis role="italic">zero</emphasis> dependencies on + fact, HornetQ core has <emphasis role="italic">zero</emphasis> dependencies on any jars other than the standard JDK classes!</para> - <para>This allows JBoss Messaging to be easily embedded in your own project, or instantiated + <para>This allows HornetQ to be easily embedded in your own project, or instantiated in any dependency injection framework such as JBoss Microcontainer, Spring or Google Guice.</para> - <para>A JBoss Messaging server has its own high performance persistent journal, which it + <para>A HornetQ server has its own high performance persistent journal, which it uses for message and other persistence.</para> <para>Using a high performance journal allows outrageous persistence message performance, something not achievable when using a relational database for persistence.</para> - <para>JBoss Messaging clients, potentially on different physical machines interact with the - JBoss Messaging server. JBoss Messaging currently provides two APIs for messaging at the + <para>HornetQ clients, potentially on different physical machines interact with the + HornetQ server. HornetQ currently provides two APIs for messaging at the client side:</para> <para> <orderedlist> @@ -34,35 +34,35 @@ </orderedlist> </para> <para>JMS semantics are implemented by a thin JMS facade layer on the client side.</para> - <para>The JBoss Messaging server does not speak JMS and in fact does not know anything about + <para>The HornetQ server does not speak JMS and in fact does not know anything about JMS, it's a protocol agnostic messaging server designed to be used with multiple different protocols.</para> <para>When a user uses the JMS API on the client side, all JMS interactions are translated - into operations on the JBoss Messaging core client API before being transferred over the - wire using the JBoss Messaging wire format.</para> + into operations on the HornetQ core client API before being transferred over the + wire using the HornetQ wire format.</para> <para>The server always just deals with core API interactions.</para> <para>A schematic illustrating this relationship is shown in figure 3.1 below:</para> <para> <graphic fileref="images/architecture1.jpg" align="center"/> </para> - <para>Figure 3.1 shows two user applications interacting with a JBoss Messaging server. User + <para>Figure 3.1 shows two user applications interacting with a HornetQ server. User Application 1 is using the JMS API, while User Application 2 is using the core client API directly.</para> <para>You can see from the diagram that the JMS API is implemented by a thin facade layer on the client side.</para> </section> <section> - <title>JBoss Messaging embedded in your own application</title> - <para>JBoss Messaging core is designed as a set of simple POJOs so if you have an + <title>HornetQ embedded in your own application</title> + <para>HornetQ core is designed as a set of simple POJOs so if you have an application that requires messaging functionality internally but you don't want to expose that as a messaging server you can directly instantiate and embed messaging servers in your own application.</para> - <para>For more information on embedding JBoss Messaging, see <xref + <para>For more information on embedding HornetQ, see <xref linkend="embedding-jbm" />.</para> </section> <section> - <title>JBoss Messaging integrated with a JEE application server</title> - <para>JBoss Messaging provides its own fully functional Java Connector Architecture (JCA) + <title>HornetQ integrated with a JEE application server</title> + <para>HornetQ provides its own fully functional Java Connector Architecture (JCA) adaptor which enables it to be integrated easily into any JEE compliant application server or servlet engine.</para> <para>JEE application servers provide Message Driven Beans (MDBs), which are a special type @@ -83,12 +83,12 @@ an EJB, MDB or servlet without going through a JCA adapter, but this is not recommended since you will not be able to take advantage of the JCA features, such as caching of JMS sessions, which can result in poor performance.</para> - <para>Figure 3.2 below shows a JEE application server integrating with a JBoss Messaging - server via the JBoss Messaging JCA adaptor. Note that all communication between EJB + <para>Figure 3.2 below shows a JEE application server integrating with a HornetQ + server via the HornetQ JCA adaptor. Note that all communication between EJB sessions or entity beans and Message Driven beans go through the adaptor and not - directly to JBoss Messaging.</para> + directly to HornetQ.</para> <para>The large arrow with the prohibited sign shows an EJB session bean talking directly to - the JBoss Messaging server. This is not recommended as you'll most likely end up + the HornetQ server. This is not recommended as you'll most likely end up creating a new connection and session every time you want to interact from the EJB, which is an anti-pattern.</para> <para> @@ -98,8 +98,8 @@ linkend="appserver-integration" />.</para> </section> <section> - <title>JBoss Messaging stand-alone server</title> - <para>JBoss Messaging can also be deployed as a stand-alone server. This means a fully + <title>HornetQ stand-alone server</title> + <para>HornetQ can also be deployed as a stand-alone server. This means a fully independent messaging server not dependent on a JEE application server.</para> <para>The standard stand-alone messaging server configuration comprises a core messaging server, a JMS service and a JNDI service.</para> @@ -107,13 +107,13 @@ instances from any server side <literal>hornetq-jms.xml</literal> configuration files. It also provides a simple management API for creating and destroying Queues, Topics and ConnectionFactory instances which can be accessed via JMX or the connection. It is a - separate service to the JBoss Messaging core server, since the core server is JMS + separate service to the HornetQ core server, since the core server is JMS agnostic. If you don't want to deploy any JMS Queues, Topics and ConnectionFactory instances via server side XML configuration and don't require a JMS management API on the server side then you can disable this service.</para> <para>We also include a JNDI server since JNDI is a common requirement when using JMS to lookup Queues, Topics and ConnectionFactory instances. If you do not require JNDI then - this service can also be disabled. JBoss Messaging allows you to programmatically create + this service can also be disabled. HornetQ allows you to programmatically create JMS and core objects directly on the client side as opposed to looking them up from JNDI, so a JNDI server is not always a requirement.</para> <para>The stand-alone server configuration uses JBoss Microcontainer to instantiate and Modified: trunk/docs/user-manual/en/client-classpath.xml =================================================================== --- trunk/docs/user-manual/en/client-classpath.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/docs/user-manual/en/client-classpath.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,18 +1,18 @@ <?xml version="1.0" encoding="UTF-8"?> <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 JBoss Messaging + <para>In this chapter we explain which jars you need on the Java classpath of a HornetQ client application. This depends on various factors including whether you're using just core, JMS, JNDI or Netty. We explain which jars are needed in each case.</para> <note> <para>All the jars mentioned here can be found in the <literal>lib</literal> directory of - the JBoss Messaging distribution. Be sure you only use the jars from the correct version + the HornetQ distribution. Be sure you only use the jars from the correct version of the release, you <emphasis>must not</emphasis> mix and match versions of jars from - different JBoss Messaging versions.</para> + different HornetQ versions.</para> </note> <section> <title>Pure Core Client</title> - <para>If you're using just a pure JBoss Messaging core client (i.e. no JMS) then you need + <para>If you're using just a pure HornetQ core client (i.e. no JMS) then you need <literal>hornetq-core-client.jar</literal> on your client classpath.</para> <para>If you're using a Netty transport then you will also netty <literal >netty.jar</literal> and <literal>hornetq-transports.jar</literal>.</para> Modified: trunk/docs/user-manual/en/client-reconnection.xml =================================================================== --- trunk/docs/user-manual/en/client-reconnection.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/docs/user-manual/en/client-reconnection.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,7 +1,7 @@ <?xml version="1.0" encoding="UTF-8"?> <chapter id="client-reconnection"> <title>Client Reconnection</title> - <para>JBoss Messaging clients can be configured to automatically reconnect to the server in the + <para>HornetQ clients can be configured to automatically reconnect to the server in the event that a failure is detected in the connection between the client and the server. If the client successfully reconnects, and the server still has a record of the clients session (i.e. the server was not restarted) then the client will transparently re-attach to the Modified: trunk/docs/user-manual/en/clusters.xml =================================================================== --- trunk/docs/user-manual/en/clusters.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/docs/user-manual/en/clusters.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -3,9 +3,9 @@ <title>Clusters</title> <section> <title>Clusters Overview</title> - <para>JBoss Messaging clusters allow groups of JBoss Messaging servers to be grouped + <para>HornetQ clusters allow groups of HornetQ servers to be grouped together in order to share message processing load. Each active node in the cluster is - an active JBoss Messaging server which manages its own messages and handles its own + an active HornetQ server which manages its own messages and handles its own connections. A server must be configured to be clustered, you will need to set the <literal>clustered</literal> element in the <literal>hornetq-configuration.xml</literal> configuration file to <literal>true</literal>, this is <literal>false</literal> by @@ -134,7 +134,7 @@ particular server it updates its entry in the list for that server.</para> <para>If it has not received a broadcast from a particular server for a length of time it will remove that server's entry from its list.</para> - <para>Discovery groups are used in two places in JBoss Messaging:</para> + <para>Discovery groups are used in two places in HornetQ:</para> <itemizedlist> <listitem> <para>By cluster connections so they know what other servers in the cluster they @@ -151,7 +151,7 @@ <para>For cluster connections, discovery groups are defined in the server side configuration file <literal>hornetq-configuration.xml</literal>. All discovery groups must be defined inside a <literal>discovery-groups</literal> element. There can be - many discovery groups defined by JBoss Messaging server. Let's look at an + many discovery groups defined by HornetQ server. Let's look at an example:</para> <programlisting><discovery-groups> <discovery-group name="my-discovery-group"> @@ -192,7 +192,7 @@ </section> <section id="clusters-discovery.groups.clientside"> <title>Discovery Groups on the Client Side</title> - <para>Let's discuss how to configure a JBoss Messaging client to use discovery to + <para>Let's discuss how to configure a HornetQ client to use discovery to discover a list of servers to which it can connect. The way to do this differs depending on whether you're using JMS or the core API.</para> <section> @@ -263,7 +263,7 @@ </section> <section> <title>Server-Side Message Load Balancing</title> - <para>If cluster connections are defined between nodes of a cluster, then JBoss Messaging + <para>If cluster connections are defined between nodes of a cluster, then HornetQ will load balance messages arriving from at a particular node from a client.</para> <para>Let's take a simple example of a cluster of four nodes A, B, C, and D arranged in a <emphasis>symmetric cluster</emphasis> (described in <xref linkend="symmetric-cluster" />). @@ -282,7 +282,7 @@ <para>For example, messages arriving on node A might be distributed in the following order between the nodes: B, D, C, A, B, D, C, A, B, D. The exact order depends on the order the nodes started up, but the algorithm used is round robin.</para> - <para>JBoss Messaging cluster connections can be configured to always blindly load balance + <para>HornetQ cluster connections can be configured to always blindly load balance messages in a round robin fashion irrespective of whether there are any matching consumers on other nodes, but they can be a bit cleverer than that and also be configured to only distribute to other nodes if they have matching consumers. We'll look @@ -294,7 +294,7 @@ balanced between the nodes of the cluster. Let's take a look at a typical cluster connection. Cluster connections are always defined in <literal >hornetq-configuration.xml</literal> inside a <literal>cluster-connection</literal> - element. There can be zero or more cluster connections defined per JBoss Messaging + element. There can be zero or more cluster connections defined per HornetQ server.</para> <programlisting> <cluster-connections> @@ -322,7 +322,7 @@ with different values of <literal>address</literal>, simultaneously balancing messages for those addresses, potentially to different clusters of servers. By having multiple cluster connections on different addresses a - single JBoss Messaging Server can effectively take part in multiple clusters + single HornetQ Server can effectively take part in multiple clusters simultaneously.</para> <para>By careful not to have multiple cluster connections with overlapping values of <literal>address</literal>, e.g. "europe" and "europe.news" since @@ -365,11 +365,11 @@ <para>If this is set to <literal>true</literal> then each incoming message will be round robin'd even though the same queues on the other nodes of the cluster may have no consumers at all, or they may have consumers that have - non matching message filters (selectors). Note that JBoss Messaging will + non matching message filters (selectors). Note that HornetQ will <emphasis>not</emphasis> forward messages to other nodes if there are no <emphasis>queues</emphasis> of the same name on the other nodes, even if this parameter is set to <literal>true</literal>.</para> - <para>If this is set to <literal>false</literal> then JBoss Messaging will only + <para>If this is set to <literal>false</literal> then HornetQ will only forward messages to other nodes of the cluster if the address to which they are being forwarded has queues which have consumers, and if those consumers have message filters (selectors) at least one of those selectors must match @@ -380,15 +380,15 @@ <listitem> <para><literal>max-hops</literal>. When a cluster connection decides the set of nodes to which it might load balance a message, those nodes do not have to - be directly connected to it via a cluster connection. JBoss Messaging can be + be directly connected to it via a cluster connection. HornetQ can be configured to also load balance messages to nodes which might be connected - to it only indirectly with other JBoss Messaging servers as intermediates in + to it only indirectly with other HornetQ servers as intermediates in a chain.</para> - <para>This allows JBoss Messaging to be configured in more complex topologies + <para>This allows HornetQ to be configured in more complex topologies and still provide message load balancing. We'll discuss this more later in this chapter.</para> <para>The default value for this parameter is <literal>1</literal>, which means - messages are only load balanced to other JBoss Messaging serves which are + messages are only load balanced to other HornetQ serves which are directly connected to this server. This parameter is optional.</para> </listitem> <listitem> @@ -401,7 +401,7 @@ </section> <section id="clusters.client.loadbalancing"> <title>Client-Side Load balancing</title> - <para>With JBoss Messaging client-side connection load balancing, subsequent client + <para>With HornetQ client-side connection load balancing, subsequent client 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> @@ -626,7 +626,7 @@ to addresses that start with "jms.", so the above would enable instant (no delay) redistribution for all JMS queues and topic subscriptions.</para> <para>The attribute <literal>match</literal> can be an exact match or it can be a string - that conforms to the JBoss Messaging wildcard syntax (described in <xref linkend="wildcard-syntax" + that conforms to the HornetQ wildcard syntax (described in <xref linkend="wildcard-syntax" />).</para> <para>The element <literal>redistribution-delay</literal> defines the delay in milliseconds after the last consumer is closed on a queue before redistributing messages from that @@ -641,7 +641,7 @@ </section> <section> <title>Cluster topologies</title> - <para>JBoss Messaging clusters can be connected together in many different topologies, let's + <para>HornetQ clusters can be connected together in many different topologies, let's consider the two most common ones here</para> <section id="symmetric-cluster"> <title>Symmetric cluster</title> Modified: trunk/docs/user-manual/en/command-buffering.xml =================================================================== --- trunk/docs/user-manual/en/command-buffering.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/docs/user-manual/en/command-buffering.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,7 +1,7 @@ <?xml version="1.0" encoding="UTF-8"?> <chapter id="command-buffering"> <title>Command Buffering</title> - <para>As JBoss Messaging clients send commands to their servers they store each sent command in + <para>As HornetQ clients send commands to their servers they store each sent command in an in-memory buffer. In the case that connection failure occurs and the client subsequently reconnects to the same server or fails over onto a replica server, as part of the reconnection protocol the server informs the client during reconnection with the id of the Modified: trunk/docs/user-manual/en/configuring-transports.xml =================================================================== --- trunk/docs/user-manual/en/configuring-transports.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/docs/user-manual/en/configuring-transports.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,14 +1,14 @@ <?xml version="1.0" encoding="UTF-8"?> <chapter id="configuring-transports"> <title>Configuring the Transport</title> - <para>JBoss Messaging has a fully pluggable and highly flexible transport layer and defines its + <para>HornetQ has a fully pluggable and highly flexible transport layer and defines its own Service Provider Interface (SPI) to make plugging in a new transport provider relatively straightforward.</para> - <para>In this chapter we'll describe the concepts required for understanding JBoss Messaging + <para>In this chapter we'll describe the concepts required for understanding HornetQ transports and where and how they're configured.</para> <section id="configuring-transports.acceptors"> <title>Understanding Acceptors</title> - <para>One of the most important concepts in JBoss Messaging transports is the + <para>One of the most important concepts in HornetQ transports is the <emphasis>acceptor</emphasis>. Let's dive straight in and take a look at an acceptor defined in xml in the configuration file <literal >hornetq-configuration.xml</literal>.</para> @@ -25,7 +25,7 @@ <para>Acceptors are always defined inside an <literal>acceptors</literal> element. There can be one or more acceptors defined in the <literal>acceptors</literal> element. There's no upper limit to the number of acceptors per server.</para> - <para>Each acceptor defines a way in which connections can be made to the JBoss Messaging + <para>Each acceptor defines a way in which connections can be made to the HornetQ server.</para> <para>In the above example we're defining an acceptor that uses Netty to listen for connections at port <literal>5446</literal>. </para> @@ -148,7 +148,7 @@ </section> <section> <title>Configuring the Netty transport</title> - <para>Out of the box, JBoss Messaging currently uses <ulink + <para>Out of the box, HornetQ currently uses <ulink url="http://www.jboss.org/netty/">Netty</ulink>, a high performance low level network library.</para> <para>Our Netty transport can be configured in several different ways; to use old (blocking) @@ -295,15 +295,15 @@ </section> <section> <title>Configuring Netty Servlet</title> - <para>We also provide a Netty servlet transport for use with JBoss Messaging. The - servlet transport allows JBoss Messaging traffic to be tunneled over HTTP to a + <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 JBoss Messaging server.</para> <para>The servlet transport differs from the Netty HTTP transport in that, with the HTTP - transport JBoss Messaging effectively acts a web server listening for HTTP traffic + transport HornetQ effectively acts a web server listening for HTTP traffic on, e.g. port 80 or 8080, whereas with the servlet transport JBM traffic is proxied through a servlet engine which may already be serving web site or other - applications. This allows JBoss Messaging to be used where corporate policies may + applications. This allows HornetQ to be used where corporate policies may only allow a single web server listening on an HTTP port, and this needs to serve all applications including messaging.</para> <para>Please see the examples for a full working example of the servlet transport being @@ -411,7 +411,7 @@ </programlisting>In both cases you will need to provide a keystore and password. Take a look at the - servlet ssl example shipped with JBoss Messaging for more detail.</para> + servlet ssl example shipped with HornetQ for more detail.</para> </section> </section> Modified: trunk/docs/user-manual/en/connection-ttl.xml =================================================================== --- trunk/docs/user-manual/en/connection-ttl.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/docs/user-manual/en/connection-ttl.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -3,11 +3,11 @@ <title>Dead Connections and Session Multiplexing</title> <para>In this section we will discuss connection time-to-live (TTL) and explain how JBoss Messaging deals with crashed clients and clients which have exited without cleanly closing - their resources. We'll also discuss how JBoss Messaging multiplexes several sessions on a + their resources. We'll also discuss how HornetQ multiplexes several sessions on a single connection.</para> <section id="dead.connections"> <title>Cleaning up Dead Connection Resources on the Server</title> - <para>Before a JBoss Messaging client application exits it is considered good practice that + <para>Before a HornetQ client application exits it is considered good practice that it should close its resources in a controlled manner, using a <literal>finally</literal> block.</para> <para>Here's an example of a well behaved core client application closing its session and @@ -64,11 +64,11 @@ over time this result in the server running out of memory or other resources.</para> <para>We have to balance the requirement for cleaning up dead client resources with the fact that sometimes the network between the client and the server can fail and then come - back, allowing the client to reconnect. JBoss Messaging supports client reconnection, so + back, allowing the client to reconnect. HornetQ supports client reconnection, so we don't want to clean up "dead" server side resources too soon or this will prevent any client from reconnecting, as it won't be able to find its old sessions on the server.</para> - <para>JBoss Messaging makes all of this configurable. For each <literal + <para>HornetQ makes all of this configurable. For each <literal >ClientSessionFactory</literal> we define a <emphasis>connection TTL</emphasis>. Basically, the TTL determines how long the server will keep a connection alive in the absence of any data arriving from the client. The client will automatically send "ping" @@ -95,7 +95,7 @@ <para>As previously discussed, it's important that all core client sessions and JMS connections are always closed explicitly in a <literal>finally</literal> block when you are finished using them. </para> - <para>If you fail to do so, JBoss Messaging will detect this at garbage collection time, + <para>If you fail to do so, HornetQ will detect this at garbage collection time, and log a warning similar to the following in the logs (If you are using JMS the warning will involve a JMS connection not a client session):</para> <programlisting> @@ -110,7 +110,7 @@ at org.acme.yourproject.YourClass (YourClass.java:666) </programlisting> - <para>JBoss Messaging will then close the connection / client session for you.</para> + <para>HornetQ will then close the connection / client session for you.</para> <para>Note that the log will also tell you the exact line of your user code where you created the JMS connection / client session that you later did not close. This will enable you to pinpoint the error in your code and correct it appropriately.</para> Modified: trunk/docs/user-manual/en/core-bridges.xml =================================================================== --- trunk/docs/user-manual/en/core-bridges.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/docs/user-manual/en/core-bridges.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -2,15 +2,15 @@ <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 - target address, typically on a different JBoss Messaging server.</para> + target address, typically on a different HornetQ server.</para> <para>The source and target servers do not have to be in the same cluster which makes bridging suitable for reliably sending messages from one cluster to another, for instance across a WAN, and where the connection may be unreliable.</para> <para>The bridge has built in resilience to failure so if the target server connection is lost, e.g. due to network failure, the bridge will retry connecting to the target until it comes back online. When it comes back online it will resume operation as normal.</para> - <para>In summary, bridges are a way to reliably connect two separate JBoss Messaging servers - together. With a core bridge both source and target servers must be JBoss Messaging + <para>In summary, bridges are a way to reliably connect two separate HornetQ servers + together. With a core bridge both source and target servers must be HornetQ servers.</para> <para>Bridges can be configured provide <emphasis>once and only once</emphasis> delivery guarantees even in the event of the failure of the source or the target server. They do this @@ -18,7 +18,7 @@ <note> <para>Although they have similar function, don't confuse core bridges with JMS bridges!</para> - <para>Core bridges are for linking a JBoss Messaging node with another JBoss Messaging node + <para>Core bridges are for linking a HornetQ node with another HornetQ node and do not use the JMS API. A JMS Bridge is used for linking any two JMS 1.1 compliant JMS providers. So, a JMS Bridge could be used for bridging to or from different JMS compliant messaging system. It's always preferable to use a core bridge if you can. Core Modified: trunk/docs/user-manual/en/diverts.xml =================================================================== --- trunk/docs/user-manual/en/diverts.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/docs/user-manual/en/diverts.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,7 +1,7 @@ <?xml version="1.0" encoding="UTF-8"?> <chapter id="diverts"> <title>Diverting and Splitting Message Flows</title> - <para>JBoss Messaging allows you to configure objects called <emphasis>diverts</emphasis> with + <para>HornetQ allows you to configure objects called <emphasis>diverts</emphasis> with some simple server configuration.</para> <para>Diverts allow you to transparently divert messages routed to one address to some other address, without making any changes to any client application logic.</para> Modified: trunk/docs/user-manual/en/duplicate-detection.xml =================================================================== --- trunk/docs/user-manual/en/duplicate-detection.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/docs/user-manual/en/duplicate-detection.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,7 +1,7 @@ <?xml version="1.0" encoding="UTF-8"?> <chapter id="duplicate-detection"> <title>Duplicate Message Detection</title> - <para>JBoss Messaging includes powerful automatic duplicate message detection, filtering out + <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 JBoss Messaging uses it and how and where to configure it.</para> @@ -24,7 +24,7 @@ <para>Sending the message(s) in a transaction does not help out either. If the server or connection fails while the transaction commit is being processed it is also indeterminate whether the transaction was successfully committed or not!</para> - <para>To solve these issues JBoss Messaging provides automatic duplicate messages detection for + <para>To solve these issues HornetQ provides automatic duplicate messages detection for messages sent to addresses.</para> <section> <title>Using Duplicate Detection for Message Sending</title> @@ -126,7 +126,7 @@ </section> <section> <title>Duplicate Detection and Paging</title> - <para>JBoss Messaging also uses duplicate detection when paging messages to storage. This is + <para>HornetQ also uses duplicate detection when paging messages to storage. This is so when a message is depaged from storage and server failure occurs, we do not end up depaging the message more than once which could result in duplicate delivery.</para> <para>For more information on paging and how to configure it, please see <xref Modified: trunk/docs/user-manual/en/embedding-jbm.xml =================================================================== --- trunk/docs/user-manual/en/embedding-jbm.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/docs/user-manual/en/embedding-jbm.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,18 +1,18 @@ <?xml version="1.0" encoding="UTF-8"?> <chapter id="embedding-jbm"> - <title>Embedding JBoss Messaging</title> - <para>JBoss Messaging is designed as set of simple Plain Old Java Objects (POJOs). This means - JBoss Messaging can be instantiated and run in any dependency injection framework such as + <title>Embedding HornetQ</title> + <para>HornetQ is designed as set of simple Plain Old Java Objects (POJOs). This means + HornetQ can be instantiated and run in any dependency injection framework such as JBoss Microcontainer, Spring or Google Guice. It also means that if you have an application that could use messaging functionality internally, then it can <emphasis>directly - instantiate</emphasis> JBoss Messaging clients and servers in its own application code + instantiate</emphasis> HornetQ clients and servers in its own application code to perform that functionality. We call this <emphasis>embedding</emphasis> JBoss Messaging.</para> <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, - instantiate the server, start it, and you have a JBoss Messaging running in your virtual + 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> @@ -47,7 +47,7 @@ transports.add(new TransportConfiguration(InVMAcceptorFactory.class.getName())); config.setAcceptorConfigurations(transports);</programlisting> - <para>You need to instantiate and start JBoss Messaging server. The class <literal + <para>You need to instantiate and start HornetQ server. The class <literal >org.hornetq.core.serverMessaging</literal> has a few static methods for creating servers with common configurations.</para> <programlisting>import org.hornetq.core.server.Messaging; @@ -68,9 +68,9 @@ <title>Dependency Frameworks</title> <para>You may also choose to use a dependency injection framework such as <trademark>JBoss Micro Container</trademark> or <trademark>Spring Framework</trademark>.</para> - <para>JBoss Messaging standalone uses JBoss Micro Container as the injection framework. + <para>HornetQ standalone uses JBoss Micro Container as the injection framework. <literal>HornetQBootstrapServer</literal> and <literal>hornetq-jboss-beans.xml</literal> - which are part of the JBoss Messaging distribution provide a very complete + 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 >MessagingServer</literal> and <literal>Configuration</literal> object, you can also @@ -102,8 +102,8 @@ bootStrap.run();</programlisting> </section> <section> - <title>Connecting to the Embedded JBoss Messaging</title> - <para>To connect clients to JBoss Messaging you just create the factories as normal:</para> + <title>Connecting to the Embedded HornetQ</title> + <para>To connect clients to HornetQ you just create the factories as normal:</para> <section> <title>Core API</title> <para>If using the core API, just create the <literal>ClientSessionFactory</literal> and @@ -136,7 +136,7 @@ </section> <section> <title>JMS API</title> - <para>Connection on an Embedded JBoss Messaging through JMS is also simple. Just + <para>Connection on an Embedded HornetQ through JMS is also simple. Just instantiate <literal>JBossConnectionFactory</literal> directly. The following example illustrates that.</para> <programlisting>JBossConnectionFactory cf = @@ -171,6 +171,6 @@ <section> <title>JMS Embedding Example</title> <para>Please see <xref linkend="examples.embedded" /> for an example which shows how - to setup and run JBoss Messaging embedded with JMS.</para> + to setup and run HornetQ embedded with JMS.</para> </section> </chapter> Modified: trunk/docs/user-manual/en/examples.xml =================================================================== --- trunk/docs/user-manual/en/examples.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/docs/user-manual/en/examples.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,7 +1,7 @@ <?xml version="1.0" encoding="UTF-8"?> <chapter id="examples"> <title>Examples</title> - <para>The JBoss Messaging distribution comes with a wide variety of run out-of-the-box examples + <para>The HornetQ distribution comes with a wide variety of run out-of-the-box examples demonstrating many of the features.</para> <para>The examples are available in the distribution, in the <literal>examples</literal> directory. Examples are split into JMS and core examples. JMS examples show how a particular @@ -18,15 +18,15 @@ <para>Here's a listing of the examples with a brief description.</para> <section id="application-level-failover"> <title>Application-Layer Failover</title> - <para>JBoss Messaging implements fully transparent automatic failover of connections + <para>HornetQ implements fully transparent automatic failover of connections from a live to backup node, this requires no special coding for failover, and is described in a different example. Automatic failover requires server replication.</para> - <para>However, JBoss Messaging also supports Application-Layer failover, useful in the + <para>However, HornetQ also supports Application-Layer failover, useful in the case that replication is not enabled on the server side.</para> <para>With Application-Layer failover, it's up to the application to register a JMS - <literal>ExceptionListener</literal> with JBoss Messaging which will be called - by JBoss Messaging in the event that connection failure is detected.</para> + <literal>ExceptionListener</literal> with HornetQ which will be called + by HornetQ in the event that connection failure is detected.</para> <para>The code in the <literal>ExceptionListener</literal> then recreates the JMS connection, session, etc on another node and the application can continue.</para> <para>Application-layer failover is an alternative approach to High Availability (HA). @@ -42,7 +42,7 @@ as a live-backup pair for high availability (HA), and a client connection transparently failing over from live to backup when the live server is crashed.</para> - <para>JBoss Messaging implements seamless, transparent failover of client connections + <para>HornetQ implements seamless, transparent failover of client connections between live and backup servers. This is implemented by the replication of state between live and backup nodes. When replication is configured and a live node crashes, the client connections can carry on as if nothing happened and carry on @@ -57,13 +57,13 @@ to read/write to the connection, or the failure of a pong to arrive back from the server in good time after a ping is sent, instead of failing the connection immediately and notifying any user <literal>ExceptionListener</literal> objects, - JBoss Messaging can be configured to automatically retry the connection, and + HornetQ can be configured to automatically retry the connection, and reconnect to the server when it becomes available again across the network.</para> </section> <section id="examples.browsers"> <title>Browser</title> <para>The <literal>browser</literal> example shows you how to use a JMS <literal - >QueueBrowser</literal> with JBoss Messaging.</para> + >QueueBrowser</literal> with HornetQ.</para> <para>Queues are a standard part of JMS, please consult the JMS 1.1 specification for full details.</para> <para> A <literal>QueueBrowser</literal> is used to look at messages on the queue @@ -75,7 +75,7 @@ <para>The <literal>bridge</literal> example demonstrates a core bridge deployed on one server, which consumes messages from a local queue and forwards them to an address on a second server.</para> - <para>Core bridges are used to create message flows between any two JBoss Messaging + <para>Core bridges are used to create message flows between any two HornetQ servers which are remotely separated. Core bridges are resilient and will cope with temporary connection failure allowing them to be an ideal choice for forwarding over unreliable connections, e.g. a WAN.</para> @@ -90,7 +90,7 @@ <para>The <literal>client-side-load-balancing</literal> example demonstrates how subsequent connections created from a JMS <literal>ConnectionFactory</literal> can be created to different nodes of the cluster. In other words it demonstrates how - JBoss Messaging does client side load balancing of connections across the + HornetQ does client side load balancing of connections across the cluster.</para> </section> <section> @@ -132,7 +132,7 @@ </section> <section id="examples.delayed-redelivery"> <title>Delayed Redelivery</title> - <para>The <literal>delayed-redelivery</literal> example demonstrates how JBoss Messaging + <para>The <literal>delayed-redelivery</literal> example demonstrates how HornetQ can be configured to provide a delayed redelivery in the case a message needs to be redelivered.</para> <para>Delaying redelivery can often be useful in the case that clients regularly fail or @@ -143,14 +143,14 @@ </section> <section id="divert-example"> <title>Divert</title> - <para>JBoss Messaging diverts allow messages to be transparently "diverted" from one + <para>HornetQ diverts allow messages to be transparently "diverted" from one address to another with just some simple configuration defined on the server side.</para> </section> <section> <title>Durable Subscription</title> <para>The <literal>durable-subscription</literal> example shows you how to use a durable - subscription with JBoss Messaging. Durable subscriptions are a standard part of JMS, + subscription with HornetQ. Durable subscriptions are a standard part of JMS, please consult the JMS 1.1 specification for full details.</para> <para>Unlike non-durable subscriptions, the key function of durable subscriptions is that the messages contained in them persist longer than the lifetime of the @@ -161,7 +161,7 @@ </section> <section> <title>Embedded</title> - <para>The <literal>embedded</literal> example shows how to embed the JBoss Messaging + <para>The <literal>embedded</literal> example shows how to embed the HornetQ Server within your own code.</para> </section> <section> @@ -176,36 +176,36 @@ before being used by the client code. This objects are called "administered objects" in JMS terminology.</para> <para>However, in some cases a JNDI server may not be available or desired. To come to - the rescue JBoss Messaging also supports the direct instantiation of these + the rescue HornetQ also supports the direct instantiation of these administered objects on the client side so you don't have to use JNDI for JMS.</para> </section> <section id="examples.interceptor"> <title>Interceptor</title> - <para>JBoss Messaging allows an application to use an interceptor to hook into the + <para>HornetQ allows an application to use an interceptor to hook into the messaging system. Interceptors allow you to handle various message events in JBoss Messaging.</para> </section> <section id="examples.jaas"> <title>JAAS</title> - <para>The <literal>jaas</literal> example shows you how to configure JBoss Messaging to - use JAAS for security. JBoss Messaging can leverage JAAS to delegate user + <para>The <literal>jaas</literal> example shows you how to configure HornetQ to + use JAAS for security. HornetQ can leverage JAAS to delegate user authentication and authorization to existing security infrastructure.</para> </section> <section id="examples.jmx"> <title>JMX Management</title> - <para>The <literal>jmx</literal> example shows how to manage JBoss Messaging using + <para>The <literal>jmx</literal> example shows how to manage HornetQ using JMX.</para> </section> <section id="examples.large-message"> <title>Large Message</title> <para>The <literal>large-message</literal> example shows you how to send and receive - very large messages with JBoss Messaging. JBoss Messaging supports the sending and + very large messages with HornetQ. HornetQ supports the sending and receiving of huge messages, much larger than can fit in available RAM on the client or server. Effectively the only limit to message size is the amount of disk space you have on the server.</para> <para>Large messages are persisted on the server so they can survive a server restart. - In other words JBoss Messaging doesn't just do a simple socket stream from the + In other words HornetQ doesn't just do a simple socket stream from the sender to the consumer.</para> </section> <section id="examples.last-value-queue"> @@ -225,28 +225,28 @@ <para>We then create a consumer on the queue on each node, and we create a producer on only one of the nodes. We then send some messages via the producer, and we verify that both consumers receive the sent messages in a round-robin fashion.</para> - <para>In other words, JBoss Messaging load balances the sent messages across all + <para>In other words, HornetQ load balances the sent messages across all consumers on the cluster</para> </section> <section id="examples.management"> <title>Management</title> - <para>The <literal>management</literal> example shows how to manage JBoss Messaging + <para>The <literal>management</literal> example shows how to manage HornetQ using JMS Messages to invoke management operations on the server.</para> </section> <section id="examples.management-notifications"> <title>Management Notification</title> <para>The <literal>management-notification</literal> example shows how to receive - management notifications from JBoss Messaging using JMS messages. JBoss Messaging + management notifications from HornetQ using JMS messages. HornetQ servers emit management notifications when events of interest occur (consumers are created or closed, destinations are created or deleted, security authentication fails, etc.).</para> </section> <section id="examples.consumer-rate-limit"> <title>Message Consumer Rate Limiting</title> - <para>With JBoss Messaging you can specify a maximum consume rate at which a JMS + <para>With HornetQ you can specify a maximum consume rate at which a JMS MessageConsumer will consume messages. This can be specified when creating or deploying the connection factory.</para> - <para>If this value is specified then JBoss Messaging will ensure that messages are + <para>If this value is specified then HornetQ will ensure that messages are never consumed at a rate higher than the specified rate. This is a form of consumer throttling.</para> </section> @@ -262,7 +262,7 @@ period of time before being removed. JMS specification states that clients should not receive messages that have been expired (but it does not guarantee this will not happen).</para> - <para>JBoss Messaging can assign an expiry destination to a given queue so that when + <para>HornetQ can assign an expiry destination to a given queue so that when messages are expired, they are removed from the queue and sent to the expiry destination. These "expired" messages can later be consumed from the expiry destination for further inspection.</para> @@ -270,7 +270,7 @@ <section id="examples.message-group"> <title>Message Group</title> <para>The <literal>message-group</literal> example shows you how to configure and use - message groups with JBoss Messaging. Message groups allow you to pin messages so + message groups with HornetQ. Message groups allow you to pin messages so they are only consumed by a single consumer. Message groups are sets of messages that has the following characteristics:</para> <para> @@ -313,21 +313,21 @@ </section> <section id="examples.no-consumer-buffering"> <title>No Consumer Buffering</title> - <para>By default, JBoss Messaging consumers buffer messages from the server in a client + <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 JBoss Messaging 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, JBoss Messaging pre-fetches messages into a + performance. Therefore, by default, HornetQ pre-fetches messages into a buffer on each consumer.</para> - <para>In some case buffering is not desirable, and JBoss Messaging allows it to be + <para>In some case buffering is not desirable, and HornetQ allows it to be switched off. This example demonstrates that.</para> </section> <section id="examples.paging"> <title>Paging</title> - <para>The <literal>paging</literal> example shows how JBoss Messaging can support huge + <para>The <literal>paging</literal> example shows how HornetQ can support huge queues even when the server is running in limited RAM. It does this by transparently <emphasis>paging</emphasis> messages to disk, and <emphasis>depaging</emphasis> them when they are required.</para> @@ -341,7 +341,7 @@ <para>All of these standard modes involve sending acknowledgements from the client to the server. However in some cases, you really don't mind losing messages in event of failure, so it would make sense to acknowledge the message on the server before - delivering it to the client. This example demonstrates how JBoss Messaging allows + delivering it to the client. This example demonstrates how HornetQ allows this with an extra acknowledgement mode.</para> </section> <section> @@ -364,13 +364,13 @@ <section id="examples.scheduled-message"> <title>Scheduled Message</title> <para>The <literal>scheduled-message</literal> example shows you how to send a scheduled - message to a JMS Queue with JBoss Messaging. Scheduled messages won't get delivered + message to a JMS Queue with HornetQ. Scheduled messages won't get delivered until a specified time in the future.</para> </section> <section> <title>Security</title> <para>The <literal>security</literal> example shows you how configure and use role based - queue security with JBoss Messaging.</para> + queue security with HornetQ.</para> </section> <section id="asynchronous-send-acknowledgements-example"> <title>Send Acknowledgements</title> @@ -387,7 +387,7 @@ <section> <title>Static Message Selector Using JMS</title> <para>The <literal>static-selector-jms</literal> example shows you how to configure a - JBoss Messaging queue with static message selectors (filters) using JMS.</para> + HornetQ queue with static message selectors (filters) using JMS.</para> </section> <section> <title>SSL Transport</title> @@ -397,8 +397,8 @@ <section> <title>Symmetric Cluster</title> <para>The <literal>symmetric-cluster</literal> example demonstrates a symmetric cluster - set-up with JBoss Messaging.</para> - <para>JBoss Messaging has extremely flexible clustering which allows you to set-up + set-up with HornetQ.</para> + <para>HornetQ has extremely flexible clustering which allows you to set-up servers in many different topologies. The most common topology that you'll perhaps be familiar with if you are used to application server clustering is a symmetric cluster.</para> @@ -416,7 +416,7 @@ </section> <section id="topic-hierarchy-example"> <title>Topic Hierarchy</title> - <para>JBoss Messaging supports topic hierarchies. With a topic hierarchy you can + <para>HornetQ supports topic hierarchies. With a topic hierarchy you can register a subscriber with a wild-card and that subscriber will receive any messages sent to an address that matches the wild card.</para> </section> @@ -434,29 +434,29 @@ <section> <title>Transactional Session</title> <para>The <literal>transactional</literal> example shows you how to use a transactional - Session with JBoss Messaging.</para> + Session with HornetQ.</para> </section> <section> <title>XA Heuristic</title> <para>The <literal>xa-heuristic</literal> example shows you how to make an XA heuristic - decision through JBoss Messaging Management Interface. A heuristic decision is a + decision through HornetQ Management Interface. A heuristic decision is a unilateral decision to commit or rollback an XA transaction branch after it has been prepared.</para> </section> <section> <title>XA Receive</title> <para>The <literal>xa-receive</literal> example shows you how message receiving behaves - in an XA transaction in JBoss Messaging.</para> + in an XA transaction in HornetQ.</para> </section> <section> <title>XA Send</title> <para>The <literal>xa-send</literal> example shows you how message sending behaves in an - XA transaction in JBoss Messaging.</para> + XA transaction in HornetQ.</para> </section> <section> <title>XA with Transaction Manager</title> <para>The <literal>xa-with-jta</literal> example shows you how to use JTA interfaces to - control transactions with JBoss Messaging.</para> + control transactions with HornetQ.</para> </section> </section> <section> @@ -465,7 +465,7 @@ directory and type <literal>ant</literal></para> <section id="examples.embedded"> <title>Embedded</title> - <para>This example shows how to embed the JBoss Messaging server within your own + <para>This example shows how to embed the HornetQ server within your own code.</para> </section> </section> @@ -491,7 +491,7 @@ </section> <section id="jms-bridge-example"> <title>JMS Bridge</title> - <para>An example demonstrating the use of the JBoss Messaging JMS bridge.</para> + <para>An example demonstrating the use of the HornetQ JMS bridge.</para> </section> <section> <title>MDB (Message Driven Bean)</title> @@ -499,16 +499,16 @@ </section> <section> <title>Servlet Transport</title> - <para>An example of how to use the JBoss Messaging servlet transport.</para> + <para>An example of how to use the HornetQ servlet transport.</para> </section> <section> <title>Servlet SSL Transport</title> - <para>An example of how to use the JBoss Messaging servlet transport over SSL.</para> + <para>An example of how to use the HornetQ servlet transport over SSL.</para> </section> <section id="xa-recovery-example"> <title>XA Recovery</title> <para>An example of how XA recovery works within the JBoss Application server using - JBoss Messaging.</para> + HornetQ.</para> </section> </section> </chapter> Modified: trunk/docs/user-manual/en/filter-expressions.xml =================================================================== --- trunk/docs/user-manual/en/filter-expressions.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/docs/user-manual/en/filter-expressions.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,7 +1,7 @@ <?xml version="1.0" encoding="UTF-8"?> <chapter id="filter-expressions"> <title>Filter Expressions</title> - <para>JBoss Messaging provides a powerful filter language based on a subset of the SQL 92 + <para>HornetQ provides a powerful filter language based on a subset of the SQL 92 expression syntax.</para> <para>It is the same as the syntax used for JMS selectors, but the predefined identifiers are different. For documentation on JMS selector syntax please the JMS javadoc for <ulink @@ -28,7 +28,7 @@ several places as described in <xref linkend="management"/>.</para> </listitem> </itemizedlist> - <para>There are some differences between JMS selector expressions and JBoss Messaging core + <para>There are some differences between JMS selector expressions and HornetQ core filter expressions. Whereas JMS selector expressions operate on a JMS message, JBoss Messaging 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 Modified: trunk/docs/user-manual/en/flow-control.xml =================================================================== --- trunk/docs/user-manual/en/flow-control.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/docs/user-manual/en/flow-control.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -13,14 +13,14 @@ keep building up and are not processed for a long time. </para> <section id="flow-control.consumer.window"> <title>Window-Based Flow Control</title> - <para>By default, JBoss Messaging consumers buffer messages from the server in a client + <para>By default, HornetQ consumers buffer messages from the server in a client side buffer before the client consumes them. This improves performance: otherwise every - time the client consumes a message, JBoss Messaging would have to go the server to + time the client consumes a message, HornetQ would have to go the server to request the next message. In turn, this message would then get sent to the client side, if one was available.</para> <para>A network round trip would be involved for <emphasis>every</emphasis> message and considerably reduce performance.</para> - <para>To prevent this, JBoss Messaging pre-fetches messages into a buffer on each consumer. + <para>To prevent this, HornetQ pre-fetches messages into a buffer on each consumer. The total maximum size of messages (in bytes) that will be buffered on each consumer is determined by the <literal>consumer-window-size</literal> parameter.</para> <para>By default, the <literal>consumer-window-size</literal> is set to 1 MiB (1024 * 1024 @@ -79,7 +79,7 @@ find the optimal value, but a value of 1MiB is fine in most cases.</para> <section id="flow-control.core.api"> <title>Using Core API</title> - <para>If JBoss Messaging Core API is used, the consumer window size is specified by + <para>If HornetQ Core API is used, the consumer window size is specified by <literal>ClientSessionFactory.setConsumerWindowSize()</literal> method and some of the <literal>ClientSession.createConsumer()</literal> methods.</para> </section> @@ -102,7 +102,7 @@ specified by <literal>JBossConnectionFactory.setConsumerWindowSize()</literal> method.</para> <para>Please see <xref linkend="examples.no-consumer-buffering" /> for an example which shows how to configure - JBoss Messaging to prevent consumer buffering when dealing with slow + HornetQ to prevent consumer buffering when dealing with slow consumers.</para> </section> </section> @@ -119,7 +119,7 @@ of limiting consumer rate.</para> <section id="flow-control.rate.core.api"> <title>Using Core API</title> - <para>If the JBoss Messaging core API is being used the rate can be set via the <literal + <para>If the HornetQ core API is being used the rate can be set via the <literal >ClientSessionFactory.setConsumerMaxRate(int consumerMaxRate)</literal> method or alternatively via some of the <literal>ClientSession.createConsumer()</literal> methods. </para> @@ -149,26 +149,26 @@ soon fill up with messages.</para> </note> <para>Please see <xref linkend="examples.consumer-rate-limit" /> for an example which shows - how to configure JBoss Messaging to prevent consumer buffering when dealing with slow + how to configure HornetQ to prevent consumer buffering when dealing with slow consumers.</para> </section> </section> </section> <section> <title>Producer flow control</title> - <para>JBoss Messaging also can limit the amount of data sent from a client to a server to + <para>HornetQ also can limit the amount of data sent from a client to a server to prevent the server being overwhelmed.</para> <section> <title>Window based flow control</title> - <para>JBoss Messaging clients maintain a buffer of commands that have been sent to the + <para>HornetQ clients maintain a buffer of commands that have been sent to the server, thus provides a form of flow control. Please see <xref linkend="command-buffering"/> for more information on this.</para> </section> <section> <title>Rate limited flow control</title> - <para>JBoss Messaging also allows the rate a producer can emit message to be limited, in - units of messages per second. By specifying such a rate, JBoss Messaging will ensure + <para>HornetQ also allows the rate a producer can emit message to be limited, in + units of messages per second. By specifying such a rate, HornetQ will ensure that producer never produces messages at a rate higher than that specified.</para> <para>The rate must be a positive integer to enable and is the maximum desired message consumption rate specified in units of messages per second. Setting this to <literal @@ -178,7 +178,7 @@ for a working example of limiting producer rate.</para> <section id="flow-control.producer.rate.core.api"> <title>Using Core API</title> - <para>If the JBoss Messaging core API is being used the rate can be set via the <literal + <para>If the HornetQ core API is being used the rate can be set via the <literal >ClientSessionFactory.setProducerMaxRate(int consumerMaxRate)</literal> method or alternatively via some of the <literal>ClientSession.createProducer()</literal> methods. </para> Modified: trunk/docs/user-manual/en/ha.xml =================================================================== --- trunk/docs/user-manual/en/ha.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/docs/user-manual/en/ha.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -6,15 +6,15 @@ availability is <emphasis>failover</emphasis> which we define as the <emphasis>ability for client connections to migrate from one server to another in event of server failure so client applications can continue to operate</emphasis>.</para> - <para>JBoss Messaging provides high availability by replicating servers in pairs. It also + <para>HornetQ provides high availability by replicating servers in pairs. It also provides both 100% transparent client failover and application-level client failover.</para> <section> <title>Server replication</title> - <para>JBoss Messaging allows pairs of servers to be linked together as <emphasis>live - + <para>HornetQ allows pairs of servers to be linked together as <emphasis>live - backup</emphasis> pairs. In this release there is a single backup server for each live server. Backup servers are not operational until failover occurs. In later releases we will most likely support replication onto multiple backup servers.</para> - <para>When a <emphasis>live - backup</emphasis> pair is configured, JBoss Messaging ensures + <para>When a <emphasis>live - backup</emphasis> pair is configured, HornetQ ensures that the live server state is replicated to the backup server. Replicated state includes session state, and also global state such as the set of queues and addresses on the server. </para> @@ -75,7 +75,7 @@ may diverge. After such a failure, at the next available opportunity the <literal >B</literal> server should be taken down, and its <literal>data</literal> directory copied back to the <literal>L</literal> server. Live and backup servers - can then be restarted. In this release of JBoss Messaging we do not provide any + can then be restarted. In this release of HornetQ we do not provide any automatic facility for re-assigning a backup node with a live node while it is running.</para> <para>For a backup server to function correctly it's also important that it has the same @@ -100,23 +100,23 @@ </section> <section id="ha.client.automatic"> <title>Automatic client failover</title> - <para>JBoss Messaging clients can be configured with knowledge of live and backup servers, + <para>HornetQ clients can be configured with knowledge of live and backup servers, so that in event of connection failure of the client - live server connection, the client will detect this and reconnect its sessions to the backup server. Because of server replication, then backup server will already have those sessions in the same state they were left on the live server and the client will be able to reconnect them and resume them 100% transparently as if nothing happened.</para> - <para>For automatic failover JBoss Messaging requires <emphasis>zero</emphasis> coding of + <para>For automatic failover HornetQ requires <emphasis>zero</emphasis> coding of special failover code on the client or server. This differs from other messaging systems - which intrusively require you to code special failover handling code. JBoss Messaging + which intrusively require you to code special failover handling code. HornetQ automatic failover preserves all your normal JMS or core API semantics and allows your client code to continue 100% uninterrupted on event of connection failure and failover from a live to a backup server.</para> - <para>JBoss Messaging clients detect connection failure when it has not received packets + <para>HornetQ clients detect connection failure when it has not received packets from the server within the time given by <literal>client-failure-check-period</literal> as explained in section <xref linkend="connection-ttl"/>. If the client does not receive data in good time, it will assume the connection has failed and attempt failover.</para> - <para>JBoss Messaging clients can be configured with the list of live-backup server pairs in + <para>HornetQ clients can be configured with the list of live-backup server pairs in a number of different ways. They can be configured explicitly or probably the most common way of doing this is to use <emphasis>server discovery</emphasis> for the client to automatically discover the list. For full details on how to configure clients please @@ -147,7 +147,7 @@ live server.</para> <para>To implement application-level failover, if you're using JMS then you need to code an <literal>ExceptionListener</literal> class on the JMS connection. The <literal - >ExceptionListener</literal> will be called by JBoss Messaging in the event that + >ExceptionListener</literal> will be called by HornetQ in the event that connection failure is detected. In your <literal>ExceptionListener</literal> you would close your old JMS connections, potentially look up new connection factory instances from JNDI and creating new connections. In this case you may well be using Modified: trunk/docs/user-manual/en/intercepting-operations.xml =================================================================== --- trunk/docs/user-manual/en/intercepting-operations.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/docs/user-manual/en/intercepting-operations.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,7 +1,7 @@ <?xml version="1.0" encoding="UTF-8"?> <chapter id="intercepting-operations"> <title>Intercepting Operations</title> - <para>JBoss Messaging supports <emphasis>interceptors</emphasis> to intercept packets entering + <para>HornetQ supports <emphasis>interceptors</emphasis> to intercept packets entering and leaving the server. Any supplied interceptors would be called for any packet entering or leaving the server, this allows custom code to be executed, e.g. for auditing packets, filtering or other reasons. Interceptors can change the packets they intercept.</para> Modified: trunk/docs/user-manual/en/interoperability.xml =================================================================== --- trunk/docs/user-manual/en/interoperability.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/docs/user-manual/en/interoperability.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -10,7 +10,7 @@ Consequently, using StompConnect it is possible to turn JBM into a Stomp Broker and use any of the available stomp clients. These include clients written in C, C++, c# and .net etc.</para> - <para>To run StompConnect first start the JBoss Messaging server and make sure that it is + <para>To run StompConnect first start the HornetQ server and make sure that it is using JNDI.</para> <para>Stomp requires the file <literal>jndi.properties</literal> to be available on the classpath. This should look something like:</para> @@ -20,8 +20,8 @@ <para>Make sure this file is in the classpath along with the StompConnect jar and the JBoss Messaging jars and simply run <literal>java org.codehaus.stomp.jms.Main</literal>.</para> - <para>JBoss Messaging will shortly be implementing the Stomp protocol directly, so you won't - have to use StompConnect to be able to use JBoss Messaging with Stomp clients.</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> <section> <title>AMQP</title> Modified: trunk/docs/user-manual/en/jms-core-mapping.xml =================================================================== --- trunk/docs/user-manual/en/jms-core-mapping.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/docs/user-manual/en/jms-core-mapping.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,9 +1,9 @@ <?xml version="1.0" encoding="UTF-8"?> <chapter id="jms-core-mapping"> <title>Mapping JMS Concepts to the Core API</title> - <para>This chapter describes how JMS destinations are mapped to JBoss Messaging core + <para>This chapter describes how JMS destinations are mapped to HornetQ core queues.</para> - <para>JBoss Messaging core is JMS-agnostic. It does not have any concept of a JMS topic. A JMS + <para>HornetQ core is JMS-agnostic. It does not have any concept of a JMS topic. A JMS topic is implemented in core as an address (the topic name) with zero or more queues bound to it. Each queue bound to that address represents a topic subscription. Likewise, a JMS queue is implemented as an address (the JMS queue name) with one single queue bound to it Modified: trunk/docs/user-manual/en/large-messages.xml =================================================================== --- trunk/docs/user-manual/en/large-messages.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/docs/user-manual/en/large-messages.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,13 +1,13 @@ <?xml version="1.0" encoding="UTF-8"?> <chapter id="large-messages"> <title>Large Messages</title> - <para>JBoss Messaging supports sending and receiving of huge messages, even when the client and + <para>HornetQ supports sending and receiving of huge messages, even when the client and server are running with limited memory. The only limit to the size of a message that can be sent or consumed is the amount of disk space you have available. We have tested sending and consuming messages up to 8 GiB in size with a client and server running in just 50MiB of RAM!</para> <para>To send a large message, the user can set an <literal>InputStream</literal> on a message - body, and when that message is sent, JBoss Messaging will read the <literal + body, and when that message is sent, HornetQ will read the <literal >InputStream</literal>. A <literal>FileInputStream</literal> could be used for example to send a huge message from a huge file on disk.</para> <para>As the <literal>InputStream</literal> is read the data is sent to the server as a stream @@ -46,7 +46,7 @@ <para>The default value is 100KiB.</para> <section id="large-messages.core.config"> <title>Using Core API</title> - <para>If the JBoss Messaging Core API is used, the minimal large message size is + <para>If the HornetQ Core API is used, the minimal large message size is specified by <literal>ClientSessionFactory.setMinLargeMessageSize</literal>.</para> <programlisting>ClientSessionFactory factory = new ClientSessionFactoryImpl(new @@ -77,7 +77,7 @@ </section> <section> <title>Streaming large messages</title> - <para>JBoss Messaging supports setting the body of messages using input and output streams + <para>HornetQ supports setting the body of messages using input and output streams (<literal>java.lang.io</literal>)</para> <para>These streams are then used directly for sending (input streams) and receiving (output streams) messages.</para> @@ -160,7 +160,7 @@ </section> <section id="large-messages.streaming.over.jms"> <title>Streaming over JMS</title> - <para>When using JMS, JBoss Messaging maps the streaming methods on the core API (see + <para>When using JMS, HornetQ maps the streaming methods on the core API (see <xref linkend="large-messages.ClientMessageAPI"/>) by setting object properties . You can use the method <literal>Message.setObjectProperty</literal> to set the input and output streams.</para> @@ -205,7 +205,7 @@ <section> <title>Streaming Alternative</title> <para>If you choose not to use the <literal>InputStream</literal> or <literal - >OutputStream</literal> capability of JBoss Messaging You could still access the + >OutputStream</literal> capability of HornetQ You could still access the data directly in an alternative fashion.</para> <para>On the Core API just get the bytes of the body as you normally would.</para> <programlisting>ClientMessage msg = consumer.receive(); Modified: trunk/docs/user-manual/en/libaio.xml =================================================================== --- trunk/docs/user-manual/en/libaio.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/docs/user-manual/en/libaio.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,13 +1,13 @@ <?xml version="1.0" encoding="UTF-8"?> <chapter id="libaio"> <title>Libaio Native Libraries</title> - <para>JBoss Messaging distributes a native library, used as a bridge between JBoss Messaging and + <para>HornetQ distributes a native library, used as a bridge between HornetQ and linux libaio.</para> <para><literal>libaio</literal> is a library, developed as part of the linux kernel project. With <literal>libaio</literal> we submit writes to the operating system where they are processed asynchronously. Some time later the OS will call our code back when they have been processed.</para> - <para>These are the native libraries distributed by JBoss Messaging:</para> + <para>These are the native libraries distributed by HornetQ:</para> <itemizedlist> <listitem> <para>libHornetQLibAIO32.so - x86 32 bits</para> @@ -19,7 +19,7 @@ <para>libHornetQLibAIO_ia64.so - Itanium 64 bits</para> </listitem> </itemizedlist> - <para>When using libaio, JBoss Messaging will aways try loading these files as long as they are + <para>When using libaio, HornetQ will aways 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> @@ -102,7 +102,7 @@ >./native-src/src/.libs/libHornetQLibAIO.so</literal>. Simply move that file over <literal>bin</literal> on the distribution or the place you have chosen on the <link linkend="using-server.library.path">library path</link>.</para> - <para>If you want to perform changes on the JBoss Messaging libaio code, you could just + <para>If you want to perform changes on the HornetQ libaio code, you could just call make directly at the <literal>native-src</literal> directory.</para> </section> </section> Modified: trunk/docs/user-manual/en/logging.xml =================================================================== --- trunk/docs/user-manual/en/logging.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/docs/user-manual/en/logging.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -4,7 +4,7 @@ <para>JBM uses standard <ulink url="http://java.sun.com/j2se/1.4.2/docs/guide/util/logging/">JDK logging</ulink>, (a.k.a Java-Util-Logging: JUL), for all its logging. This means we have no dependencies on any third party logging framework. Users can provide their own logging - handler to use or alternatively use the log4j handler supplied by JBoss Messaging.</para> + handler to use or alternatively use the log4j handler supplied by HornetQ.</para> <para>The handlers are configured via the JUL <literal>logging.properties</literal> file. This default location for this file is under the <literal>lib</literal> directory found in the Java home directory but it can be overridden by setting the <literal @@ -14,18 +14,18 @@ directory of the JBM installation. </para> <para>By default the standalone server is configured to use the standard console handler and a file handler that logs to <literal>bin/logs/messaging.log</literal>.</para> - <para>Because some of the third party components used to bootstrap JBoss Messaging, i.e. the + <para>Because some of the third party components used to bootstrap HornetQ, i.e. the Microcontainer, use the JBoss Logging framework we have supplied a plugin class that redirects this to the JUL logger. This is set via a system property, <literal >-Dorg.jboss.logging.Logger.pluginClass=org.hornetq.integration.logging.HornetQLoggerPlugin</literal>. This is only needed when starting the standalone server and is set in the run script. This - is not a problem if you are embedding JBoss Messaging in your own code as the Microcontainer + is not a problem if you are embedding HornetQ in your own code as the Microcontainer won't be being used.</para> <para>If you want configure your client's logging, make sure you provide a <literal>logging.properties</literal> file and set the <literal>java.util.logging.config.file</literal> property on client startup</para> <section> <title>Log4j Configuration</title> - <para>JBoss Messaging supplies a JUL Log4j handler that can be used instead of the defaults. + <para>HornetQ supplies a JUL Log4j handler that can be used instead of the defaults. To use this simply edit the logging.properties file as such:</para> <programlisting>handlers=org.hornetq.integration.logging.Log4jLoggerHandler</programlisting> <para>You will also need to download the Log4j jars and place them in the <literal @@ -34,7 +34,7 @@ </section> <section> <title>Logging With The JBoss Application Server</title> - <para>When JBoss Messaging is deployed within the Application Server then it will still use + <para>When HornetQ is deployed within the Application Server then it will still use JUL however the logging is redirected to the default JBoss logger. For more information on this refer to the JBoss documentation.</para> </section> Modified: trunk/docs/user-manual/en/management.xml =================================================================== --- trunk/docs/user-manual/en/management.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/docs/user-manual/en/management.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,26 +1,26 @@ <?xml version="1.0" encoding="UTF-8"?> <chapter id="management"> <title>Management</title> - <para>JBoss Messaging has an extensive management API that allows a user to modify a server + <para>HornetQ has an extensive management API that allows a user to modify a server configuration, create new resources (e.g. JMS queues and topics), inspect these resources (e.g. how many messages are currently held in a queue) and interact with it (e.g. to remove messages from a queue). All the operations allows a client to <emphasis>manage</emphasis> - JBoss Messaging. It also allows clients to subscribe to management notifications.</para> - <para>There are 3 ways to manage JBoss Messaging:</para> + HornetQ. It also allows clients to subscribe to management notifications.</para> + <para>There are 3 ways to manage HornetQ:</para> <itemizedlist> <listitem> <para>Using JMX -- JMX is the standard way to manage Java applications</para> </listitem> <listitem> - <para>Using the core API -- management operations are sent to JBoss Messaging server using + <para>Using the core API -- management operations are sent to HornetQ server using <emphasis>core messages</emphasis></para> </listitem> <listitem> - <para>Using the JMS API -- management operations are sent to JBoss Messaging server using + <para>Using the JMS API -- management operations are sent to HornetQ server using <emphasis>JMS messages</emphasis></para> </listitem> </itemizedlist> - <para>Although there are 3 different ways to manage JBoss Messaging each API supports the same + <para>Although there are 3 different ways to manage HornetQ each API supports the same functionality. If it is possible to manage a resource using JMX it is also possible to achieve the same result using Core messages or JMS messages.</para> <para>This choice depends on your requirements, your application settings and your environment to @@ -31,7 +31,7 @@ management API is the same.</para> <para>For each <emphasis>managed resource</emphasis>, there exists a Java interface describing what can be invoked for this type of resource.</para> - <para>JBoss Messaging exposes its managed resources in 2 packages:</para> + <para>HornetQ exposes its managed resources in 2 packages:</para> <itemizedlist> <listitem> <para><emphasis>Core</emphasis> resources are located in the <literal @@ -54,7 +54,7 @@ <section> <title>Core Management API</title> - <para>JBoss Messaging defines a core management API to manage core resources. For full + <para>HornetQ defines a core management API to manage core resources. For full details of the API please consult the javadoc. In summary:</para> <section> <title>Core Server Management</title> @@ -101,7 +101,7 @@ </listitem> <listitem> <para>Retrieving the server configuration and attributes</para> - <para>The <literal>MessagingServerControl</literal> exposes JBoss Messaging + <para>The <literal>MessagingServerControl</literal> exposes HornetQ server configuration through all its attributes (e.g. <literal >getVersion()</literal> method to retrieve the server's version, etc.)</para> @@ -197,7 +197,7 @@ </section> <section> <title>Other Core Resources Management</title> - <para>JBoss Messaging allows to start and stop its remote resources (acceptors, diverts, + <para>HornetQ allows to start and stop its remote resources (acceptors, diverts, bridges, etc.) so that a server can be taken off line for a given period of time without stopping it completely (e.g. if other management operations must be performed such as resolving heuristic transactions). These resources are:</para> @@ -276,7 +276,7 @@ </section> <section> <title>JMS Management API</title> - <para>JBoss Messaging defines a JMS Management API to manage JMS <emphasis>administrated + <para>HornetQ defines a JMS Management API to manage JMS <emphasis>administrated objects</emphasis> (i.e. JMS queues, topics and connection factories).</para> <section> <title>JMS Server Management</title> @@ -446,10 +446,10 @@ </section> <section id="management.jmx"> <title>Using Management Via JMX</title> - <para>JBoss Messaging can be managed using <ulink + <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 JBoss Messaging using MBeans interfaces. JBoss + <para>The management API is exposed by HornetQ using MBeans interfaces. JBoss Messaging registers its resources with the domain <literal >org.jboss.messaging</literal>.</para> <para>For example, the <literal>ObjectName</literal> to manage a JMS Queue <literal @@ -465,18 +465,18 @@ >org.hornetq.core.management.ObjectNames</literal>. You can also use <literal >jconsole</literal> to find the <literal>ObjectName</literal> of the MBeans you want to manage. </para> - <para>Managing JBoss Messaging using JMX is identical to management of any Java Applications + <para>Managing HornetQ using JMX is identical to management of any Java Applications using JMX. It can be done by reflection or by creating proxies of the MBeans.</para> <section id="management.jmx.configuration"> <title>Configuring JMX</title> - <para>By default, JMX is enabled to manage JBoss Messaging. It can be disabled by setting + <para>By default, JMX is enabled to manage HornetQ. It can be disabled by setting <literal>jmx-management-enabled</literal> to <literal>false</literal> in <literal >hornetq-configuration.xml</literal>:</para> <programlisting> - + <jmx-management-enabled>false</jmx-management-enabled> </programlisting> - <para>If JMX is enabled, JBoss Messaging can be managed locally using <literal + <para>If JMX is enabled, HornetQ can be managed locally using <literal >jconsole</literal>. Remote connections to JMX are not enabled by default for security reasons. Please refer to <ulink url="http://java.sun.com/j2se/1.5.0/docs/guide/management/agent.html#remote">Java @@ -487,7 +487,7 @@ <section> <title>MBeanServer configuration</title> - <para>When JBoss Messaging is run in standalone, it uses the Java Virtual Machine's <literal>Platform + <para>When HornetQ is run in standalone, it uses the Java Virtual Machine's <literal>Platform MBeanServer</literal> to register its MBeans. This is configured in JBoss Microcontainer Beans file (see <xref linkend="server.microcontainer.configuration" />):</para> @@ -513,12 +513,12 @@ <title>Example</title> <para>See <xref linkend="examples.jmx" /> for an example which shows how to use a remote connection to JMX and MBean proxies to - manage JBoss Messaging.</para> + manage HornetQ.</para> </section> </section> <section> <title>Using Management Via Core API</title> - <para>The core management API in JBoss Messaging is called by sending Core messages to a + <para>The core management API in HornetQ is called by sending Core messages to a special address, the <emphasis>management address</emphasis>.</para> <para><emphasis>Management messages</emphasis> are regular Core messages with well-known properties that the server needs to understand to interact with the management API:</para> @@ -533,7 +533,7 @@ <para>The parameters of the management operation</para> </listitem> </itemizedlist> - <para>When such a management message is sent to the management address, JBoss Messaging server + <para>When such a management message is sent to the management address, HornetQ server will handle it, extract the information, invoke the operation on the managed resources and send a <emphasis>management reply</emphasis> to the management message's reply-to address (specified by <literal>ClientMessageImpl.REPLYTO_HEADER_NAME</literal>). </para> @@ -598,7 +598,7 @@ is also configured in hornetq-configuration.xml:</para> <programlisting>  -  +  <security-setting match="jbm.management"> <permission type="manage" roles="admin" /> </security-setting> @@ -607,7 +607,7 @@ </section> <section id="management.jms"> <title>Using Management Via JMS</title> - <para>Using JMS messages to manage JBoss Messaging is very similar to using core API.</para> + <para>Using JMS messages to manage HornetQ is very similar to using core API.</para> <para>An important difference is that JMS requires a JMS queue to send the messages to (instead of an address for the core API).</para> <para>The <emphasis>management queue</emphasis> is a special queue and needs to be @@ -661,25 +661,25 @@ <section> <title>Example</title> <para>See <xref linkend="examples.management" /> for an example which shows how to use - JMS messages to manage JBoss Messaging server.</para> + JMS messages to manage HornetQ server.</para> </section> </section> <section id="management.replication"> <title>Management Cluster Credentials</title> - <para>JBoss Messaging allows <emphasis>replication</emphasis> of a live server to a backup + <para>HornetQ allows <emphasis>replication</emphasis> of a live server to a backup server. This impacts management as resources created on the live server (e.g. a core address) must also be created on the backup server. Otherwise, when failover occurs, the backup server will not be able to handle messages sent to this address since its resources will have been created on the live server only and not on the backup.</para> - <para>JBoss Messaging <emphasis>replicates management operations</emphasis> regardless of the + <para>HornetQ <emphasis>replicates management operations</emphasis> regardless of the management API used (JMX, Core messages, JMS messages). Any management operation invoked on a live server will also be invoked on its backup server to ensure a proper replication of resources and state. For example, you only need to manage the live server: if a queue is - created on the live server, JBoss Messaging will ensure that the same resource will also be + created on the live server, HornetQ will ensure that the same resource will also be created on the backup server.</para> <para>If core or JMS messages are used to invoke management operations, replication is handled - automatically by JBoss Messaging.</para> - <para>To allow this management replication with JMX, JBoss Messaging defines + automatically by HornetQ.</para> + <para>To allow this management replication with JMX, HornetQ defines <emphasis>management cluster credentials</emphasis>: this special user/password <emphasis>must be shared by all nodes</emphasis>. To configure it, change the value in <literal >hornetq-configuration.xml</literal>:</para> @@ -688,12 +688,12 @@ <management-cluster-password>CHANGE ME!!</management-cluster-password> </programlisting> <para>It is strongly suggested to - change these values from their default. If they are not changed from the default, JBoss Messaging will + change these values from their default. If they are not changed from the default, HornetQ will detect this and pester you with a warning on every start-up.</para> - <para>JBoss Messaging internally uses Core messages to replicate management operations between + <para>HornetQ internally uses Core messages to replicate management operations between the live and backup server when JMX is used. By default, there is a timeout of 5s (5000ms) to send a management request from the live server to the backup server and wait for a - reply. If a reply is not received before the timeout is hit, JBoss Messaging considers the + reply. If a reply is not received before the timeout is hit, HornetQ considers the replication has failed. This timeout can be configured in <literal >hornetq-configuration.xml</literal>:</para> <programlisting> @@ -702,7 +702,7 @@ </section> <section id="management.notifications"> <title>Management Notifications</title> - <para>JBoss Messaging emits <emphasis>notifications</emphasis> to inform listeners of + <para>HornetQ emits <emphasis>notifications</emphasis> to inform listeners of potentially interesting events (creation of new resources, security violation, etc.).</para> <para>These notifications can be received by 3 different ways:</para> @@ -734,7 +734,7 @@ </section> <section> <title>Core Messages Notifications</title> - <para>JBoss Messaging defines a special <emphasis>management notification + <para>HornetQ defines a special <emphasis>management notification address</emphasis>. Core queues can be bound to this address so that clients will receive management notifications as Core messages</para> <para>A Core client which wants to receive management notifications must create a core @@ -758,7 +758,7 @@ </section> <section> <title>JMS Messages Notifications</title> - <para>JBoss Messaging's notifications can also be received using JMS messages.</para> + <para>HornetQ's notifications can also be received using JMS messages.</para> <para>It is similar to receiving notifications using Core API but an important difference is that JMS requires a JMS Destination to receive the messages (preferably a Topic):</para> @@ -806,7 +806,7 @@ <section id="management.message-counters"> <title>Message Counters</title> <para>Message counters can be used to obtain information on queues <emphasis>over - time</emphasis> as JBoss Messaging keeps a history on queue metrics.</para> + time</emphasis> as HornetQ keeps a history on queue metrics.</para> <para>They can be used to show <emphasis>trends</emphasis> on queues. For example, using the management API, it would be possible to query the number of messages in a queue at regular interval. However, this would not be enough to know if the queue is used: the number of @@ -870,7 +870,7 @@ <para>Message counters can be retrieved using the Management API. For example, to retrieve message counters on a JMS Queue using JMX:</para> <programlisting> -// retrieve a connection to JBoss Messaging's MBeanServer +// retrieve a connection to HornetQ's MBeanServer MBeanServerConnection mbsc = ... JMSQueueControlMBean queueControl = (JMSQueueControl)MBeanServerInvocationHandler.newProxyInstance(mbsc, on, Modified: trunk/docs/user-manual/en/master.xml =================================================================== --- trunk/docs/user-manual/en/master.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/docs/user-manual/en/master.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -50,7 +50,7 @@ ]> <book lang="en"> <bookinfo> - <title>JBoss Messaging 2.0 User Manual</title> + <title>HornetQ 2.0 User Manual</title> <subtitle>Setting the Standard for High Performance Messaging</subtitle> </bookinfo> Modified: trunk/docs/user-manual/en/message-expiry.xml =================================================================== --- trunk/docs/user-manual/en/message-expiry.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/docs/user-manual/en/message-expiry.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -4,13 +4,13 @@ <para>Messages can be set with an optional <emphasis>time to live</emphasis> when sending them. Such messages will be retained in the messaging system until their <emphasis>time to live</emphasis> is reached.</para> - <para>JBoss Messaging's addresses can be assigned a expiry address so that, when messages are + <para>HornetQ's addresses can be assigned a expiry address so that, when messages are expired, they are removed from the queue and sent to the expiry address. Many different queues can be bound to an expiry address. These <emphasis>expired</emphasis> messages can later be consumed for further inspection.</para> <section> <title>Message Expiry</title> - <para>Using JBoss Messaging Core API, you can set an expiration time directly on the + <para>Using HornetQ Core API, you can set an expiration time directly on the message:</para> <programlisting> // message will expire in 5000ms from now Modified: trunk/docs/user-manual/en/message-grouping.xml =================================================================== --- trunk/docs/user-manual/en/message-grouping.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/docs/user-manual/en/message-grouping.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -6,7 +6,7 @@ <listitem> <para>Messages in a message group share the same group id, i.e. they have same group identifier property (<literal>JMSXGroupID</literal> for JMS, <literal - >_JBM_GROUP_ID</literal> for JBoss Messaging Core API).</para> + >_JBM_GROUP_ID</literal> for HornetQ Core API).</para> </listitem> <listitem> <para>Messages in a message group are always consumed by the same consumer, even if there Modified: trunk/docs/user-manual/en/messaging-concepts.xml =================================================================== --- trunk/docs/user-manual/en/messaging-concepts.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/docs/user-manual/en/messaging-concepts.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,7 +1,7 @@ <?xml version="1.0" encoding="UTF-8"?> <chapter id="messaging-concepts"> <title>Messaging Concepts</title> - <para>JBoss Messaging is an asynchronous messaging system, an example of <ulink + <para>HornetQ is an asynchronous messaging system, an example of <ulink url="http://en.wikipedia.org/wiki/Message_oriented_middleware">Message Oriented Middleware</ulink> , we'll just call them messaging systems in the remainder of this book.</para> @@ -114,7 +114,7 @@ <section> <title>Transactions</title> <para>Messaging systems typically support the sending and acknowledgement of multiple - messages in a single local transaction. JBoss Messaging also supports the sending and + messages in a single local transaction. HornetQ also supports the sending and acknowledgement of message as part of a large global transaction - using the Java mapping of XA, JTA.</para> </section> @@ -148,7 +148,7 @@ <para>JMS does not define a standard wire format - it only defines a programmatic API so JMS clients and servers from different vendors cannot interoperate since they will most likely use the vendor's own internal wire protocol.</para> - <para>JBoss Messaging provides a fully compliant JMS 1.1 API.</para> + <para>HornetQ provides a fully compliant JMS 1.1 API.</para> </section> <section> <title>System specific APIs</title> @@ -157,7 +157,7 @@ functionality to be exposed to the client application. API's like JMS are not normally rich enough to expose all the extra features that most messaging systems provide.</para> - <para>JBoss Messaging provides its own core client API for clients to use if they wish + <para>HornetQ provides its own core client API for clients to use if they wish to have access to functionality over and above that accessible via the JMS API.</para> </section> @@ -169,10 +169,10 @@ systems. It defines a wire format, so theoretically any STOMP client can work with any messaging system that supports STOMP. STOMP clients are available in many different programming languages.</para> - <para>JBoss Messaging can be used by any STOMP client when using the <ulink + <para>HornetQ can be used by any STOMP client when using the <ulink url="http://stomp.codehaus.org/StompConnect">StompConnect</ulink> broker which translates the STOMP protocol to the JMS API.</para> - <para>JBoss Messaging will be shortly implementing the STOMP protocol on the broker, thus + <para>HornetQ will be shortly implementing the STOMP protocol on the broker, thus avoiding having to use StompConnect.</para> </section> <section> @@ -181,7 +181,7 @@ standard for interoperable messaging. It also defines a wire format, so any AMQP client can work with any messaging system that supports AMQP. AMQP clients are available in many different programming languages.</para> - <para>JBoss Messaging will shortly be implementing AMQP.</para> + <para>HornetQ will shortly be implementing AMQP.</para> </section> <section> <title>REST</title> @@ -193,7 +193,7 @@ protocol.</para> <para>The advantage of a REST approach with HTTP is in its simplicity and the fact the internet is already tuned to deal with HTTP optimally.</para> - <para>JBoss Messaging will shortly be implementing REST.</para> + <para>HornetQ will shortly be implementing REST.</para> </section> </section> <section> @@ -204,8 +204,8 @@ <para>Some messaging systems require you to deal with server side failure by writing some client side code which gets called on event of server failure, and in which you are supposed to recreate your connections to another server.</para> - <para>JBoss Messaging provides 100% transparent failover where you don't have have to write - any special client side code to deal with failure. On failover JBoss Messaging will + <para>HornetQ provides 100% transparent failover where you don't have have to write + any special client side code to deal with failure. On failover HornetQ will automatically fail over your client connections to another server, and your client sessions can continue as if nothing happened.</para> <para>For more information on HA, please see <xref linkend="ha" />.</para> @@ -219,10 +219,10 @@ <para>Degrees of support for clusters varies between messaging systems, with some systems having fairly basic clusters with the cluster members being hardly aware of each other.</para> - <para>JBoss Messaging provides very configurable state of the art clustering where messages + <para>HornetQ provides very configurable state of the art clustering where messages can be intelligently load balanced between the servers in the cluster, according to the number of consumers on each node, and whether they are ready for messages.</para> - <para>JBoss Messaging also has the ability to automatically redistribute messages between + <para>HornetQ also has the ability to automatically redistribute messages between nodes of a cluster to prevent starvation on any particular node.</para> <para>For full details on clustering, please see <xref linkend="clusters"/>.</para> </section> @@ -233,9 +233,9 @@ <para>A bridge normally consumes from a queue on one server and forwards messages to another queue on a different server. Bridges cope with unreliable connections, automatically reconnecting when the connections becomes available again.</para> - <para>JBoss Messaging bridges can be configured with filter expressions to only forward + <para>HornetQ bridges can be configured with filter expressions to only forward certain messages, and transformation can also be hooked in.</para> - <para>JBoss Messaging also allows routing between queues to be configured in server side + <para>HornetQ also allows routing between queues to be configured in server side configuration. This allows complex routing networks to be set up forwarding or copying messages from one destination to another, forming a global network of interconnected brokers.</para> Modified: trunk/docs/user-manual/en/paging.xml =================================================================== --- trunk/docs/user-manual/en/paging.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/docs/user-manual/en/paging.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,12 +1,12 @@ <?xml version="1.0" encoding="UTF-8"?> <chapter id="paging"> <title>Paging</title> - <para>JBoss Messaging transparently supports huge queues containing millions of messages while + <para>HornetQ transparently supports huge queues containing millions of messages while the server is running with limited memory.</para> <para>In such a situation it's not possible to store all of the queues in memory at any one - time, so JBoss Messaging transparently <emphasis>pages</emphasis> messages into and out of + time, so HornetQ transparently <emphasis>pages</emphasis> messages into and out of memory as they are needed, thus allowing massive queues with a low memory footprint.</para> - <para>JBoss Messaging will start paging messages to disk, when either the size of the queue + <para>HornetQ will start paging messages to disk, when either the size of the queue reaches a total configured maximum size.</para> <section> <title>Page Files</title> @@ -47,7 +47,7 @@ <tbody> <row> <entry><literal>paging-directory</literal></entry> - <entry>Where page files are stored. JBoss Messaging will create one + <entry>Where page files are stored. HornetQ will create one folder for each address being paged under this configured location.</entry> <entry>data/paging</entry> @@ -143,6 +143,6 @@ <section> <title>Example</title> <para>See <xref linkend="examples.paging"/> for an example which shows how to use paging - with JBoss Messaging.</para> + with HornetQ.</para> </section> </chapter> Modified: trunk/docs/user-manual/en/perf-tuning.xml =================================================================== --- trunk/docs/user-manual/en/perf-tuning.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/docs/user-manual/en/perf-tuning.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,7 +1,7 @@ <?xml version="1.0" encoding="UTF-8"?> <chapter id="perf-tuning"> <title>Performance Tuning</title> - <para>In this chapter we'll discuss how to tune JBoss Messaging for optimum performance.</para> + <para>In this chapter we'll discuss how to tune HornetQ for optimum performance.</para> <section> <title>Tuning the journal</title> <itemizedlist> @@ -78,7 +78,7 @@ </section> <section> <title>Other Tunings</title> - <para>There are various other places in JBoss Messaging where we can perform some + <para>There are various other places in HornetQ where we can perform some tuning:</para> <itemizedlist> <listitem> @@ -167,7 +167,7 @@ >-XX:+UseParallelGC</literal> on Sun JDKs.</para> </listitem> <listitem> - <para>Memory settings. Give as much memory as you can to the server. JBoss Messaging + <para>Memory settings. Give as much memory as you can to the server. HornetQ can run in low memory by using paging (described in <xref linkend="paging"/>) but if it can run with all queues in RAM this will improve performance. The amount of memory you require will depend on the size and number of your queues @@ -199,7 +199,7 @@ <note> <para>Some popular libraries such as the Spring JMS Template are known to use these anti-patterns. If you're using Spring JMS Template and you're getting - poor performance you know why. Don't blame JBoss Messaging!</para> + poor performance you know why. Don't blame HornetQ!</para> </note> </listitem> <listitem> @@ -215,7 +215,7 @@ entire queue has to be scanned for matching messages.</para> <para>This anti-pattern can normally be avoided by instead using a topic with many durable subscriptions, each subscription defines a message selector. With topic - subscriptions the selector expression is evaluated by JBoss Messaging before the + subscriptions the selector expression is evaluated by HornetQ before the message goes into the subscription, so no scanning is involved.</para> </listitem> <listitem> Modified: trunk/docs/user-manual/en/persistence.xml =================================================================== --- trunk/docs/user-manual/en/persistence.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/docs/user-manual/en/persistence.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,14 +1,14 @@ <?xml version="1.0" encoding="UTF-8"?> <chapter id="persistence"> <title>Persistence</title> - <para>In this chapter we will describe how persistence works with JBoss Messaging and how to + <para>In this chapter we will describe how persistence works with HornetQ and how to configure it.</para> - <para>JBoss Messaging ships with a high performance journal. This journal has been implemented - by the JBoss Messaging team with a view to providing high performance in a messaging system. - Since JBoss Messaging handles its own persistence, rather than relying on a database or + <para>HornetQ ships with a high performance journal. This journal has been implemented + by the HornetQ team with a view to providing high performance in a messaging system. + Since HornetQ handles its own persistence, rather than relying on a database or other 3rd party persistence engine, we have been able to tune the journal to gain optimal performance for the persistence of messages and transactions.</para> - <para>A JBoss Messaging journal is an <emphasis>append only</emphasis> journal. It consists of a + <para>A HornetQ journal is an <emphasis>append only</emphasis> journal. It consists of a set of files on disk. Each file is pre-created to a fixed size and initially filled with padding. As operations are performed on the server, e.g. add message, update message, delete message, records are appended to the journal. When one journal file is full we move to the @@ -21,11 +21,11 @@ by minimising the number of disk cylinders the file is using, we can minimise the amount of disk head movement, since an entire disk cylinder is accessible simply by the disk rotating - the head does not have to move.</para> - <para>As delete records are added to the journal, JBoss Messaging has a sophisticated file + <para>As delete records are added to the journal, HornetQ has a sophisticated file garbage collection algorithm which can determine if a particular journal file is needed any more - i.e. has all it's data been deleted in the same or other files. If so, the file can be reclaimed and re-used. </para> - <para>JBoss Messaging also has a compaction algorithm which removes dead space from the journal + <para>HornetQ also has a compaction algorithm which removes dead space from the journal and compresses up the data so it takes up less files on disk.</para> <para>The journal also fully supports transactional operation if required, supporting both local and XA transactions.</para> @@ -47,7 +47,7 @@ transaction boundary to be synced to disk. Most disks can only support a limited number of syncs per second, so a syncing approach does not scale well when the number of concurrent transactions needed to be committed grows too large. With AIO, - JBoss Messaging will be called back when the data has made it to disk, allowing us + HornetQ will be called back when the data has made it to disk, allowing us to avoid explicit syncs altogether and simply send back confirmation of completion when AIO informs us that the data has been persisted.</para> <para>The AIO journal is only available when running Linux kernel 2.6 or later and after @@ -57,7 +57,7 @@ <para>libaio is part of the kernel project.</para> </listitem> </itemizedlist> - <para>The standard JBoss Messaging core server uses two instances of the journal:</para> + <para>The standard HornetQ core server uses two instances of the journal:</para> <itemizedlist> <listitem> <para>Bindings journal.</para> @@ -71,17 +71,17 @@ <para>Message journal.</para> <para>This journal instance stores all message related data, including the message themselves and also duplicate id caches.</para> - <para>By default JBoss Messaging will try and use an AIO journal. If AIO is not + <para>By default HornetQ will try and use an AIO journal. If AIO is not available, e.g. the platform is not Linux with the correct kernel version or AIO has not been installed then it will automatically fall back to using Java NIO which is available on any Java platform.</para> </listitem> </itemizedlist> - <para>For large messages, JBoss Messaging persists them outside the message journal. This is + <para>For large messages, HornetQ persists them outside the message journal. This is discussed in <xref linkend="large-messages"/>.</para> - <para>JBoss Messaging also pages messages to disk in low memory situations. This is discussed in + <para>HornetQ also pages messages to disk in low memory situations. This is discussed in <xref linkend="paging"/>.</para> - <para>If no persistence is required at all, JBoss Messaging can also be configured not to + <para>If no persistence is required at all, HornetQ can also be configured not to persist any data at all to storage as discussed in <xref linkend="persistence.enabled" />.</para> <section id="configuring.bindings.journal"> @@ -134,18 +134,18 @@ <para>Choosing <literal>NIO</literal> chooses the Java NIO journal. Choosing <literal>AIO</literal> chooses the Linux asynchronous IO journal. If you choose <literal>AIO</literal> but are not running Linux or you do not have - libaio installed then JBoss Messaging will detect this and automatically fall + libaio installed then HornetQ will detect this and automatically fall back to using <literal>NIO</literal>.</para> </listitem> <listitem id="configuring.message.journal.journal-sync-transactional"> <para><literal>journal-sync-transactional</literal></para> - <para>If this is set to true then JBoss Messaging will wait for all transaction data + <para>If this is set to true then HornetQ will wait for all transaction data to be persisted to disk on a commit before sending a commit response OK back to the client. The default value is <literal>true</literal>.</para> </listitem> <listitem id="configuring.message.journal.journal-sync-non-transactional"> <para><literal>journal-sync-non-transactional</literal></para> - <para>If this is set to true then JBoss Messaging will wait for any non + <para>If this is set to true then HornetQ will wait for any non transactional data to be persisted to disk on a send before sending the response back to the client. The default value for this is <literal >false</literal>.</para> @@ -157,8 +157,8 @@ </listitem> <listitem id="configuring.message.journal.journal-min-files"> <para><literal>journal-min-files</literal></para> - <para>The minimum number of files the journal will maintain. When JBoss Messaging - starts and there is no initial message data, JBoss Messaging will pre-create + <para>The minimum number of files the journal will maintain. When HornetQ + starts and there is no initial message data, HornetQ will pre-create <literal>journal-min-files</literal> number of files.</para> <para>Creating journal files and filling them with padding is a fairly expensive operation and we want to minimise doing this at run-time as files get filled. By @@ -170,7 +170,7 @@ <listitem id="configuring.message.journal.journal-max-aio"> <para><literal>journal-max-aio</literal></para> <para>When using an AIO journal, write requests are queued up before being submitted - to AIO for execution. Then when AIO has completed them it calls JBoss Messaging + to AIO for execution. Then when AIO has completed them it calls HornetQ back. This parameter controls the maximum number of write requests that can be in the AIO queue at any one time. If the queue becomes full then writes will block until space is freed up. This parameter has no meaning when using the NIO @@ -195,7 +195,7 @@ sync request is performed. Sync requests are performed on transactions if <literal>journal-sync-transactional</literal> is true, or on sending regular messages if <literal>journalsync-non-transactional</literal> is true.</para> - <para>JBoss Messaging was made to scale up to hundreds of producers. We try to use + <para>HornetQ was made to scale up to hundreds of producers. We try to use most of the hardware resources by scheduling multiple writes and syncs in a single OS call.</para> <para>However in some use cases it may be better to not wait any data and just flush @@ -224,7 +224,7 @@ </section> <section id="installing-aio"> <title>Installing AIO</title> - <para>The Java NIO journal gives great performance, but If you are running JBoss Messaging + <para>The Java NIO journal gives great performance, but If you are running HornetQ using Linux Kernel 2.6 or later, we highly recommend you use the <literal>AIO</literal> journal for the best persistence performance especially under high concurrency.</para> <para>It's not possible to use the AIO journal under other operating systems or earlier @@ -238,9 +238,9 @@ <programlisting>sudo apt-get install libaio</programlisting></para> </section> <section id="persistence.enabled"> - <title>Configuring JBoss Messaging for Zero Persistence</title> + <title>Configuring HornetQ for Zero Persistence</title> <para> In some situations, zero persistence is sometimes required for a messaging system. - Configuring JBoss Messaging to perform zero persistence is straightforward. Simply set + Configuring HornetQ to perform zero persistence is straightforward. Simply set the parameter <literal>persistence-enabled</literal> in <literal >hornetq-configuration.xml</literal> to <literal>false</literal>. </para> <para>Please note that if you set this parameter to false, then <emphasis>zero</emphasis> Modified: trunk/docs/user-manual/en/preface.xml =================================================================== --- trunk/docs/user-manual/en/preface.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/docs/user-manual/en/preface.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,10 +1,10 @@ <?xml version="1.0" encoding="UTF-8"?> <chapter id="preface"> <title>Preface</title> - <para>The goal of JBoss Messaging is simple and uncompromising; to bring unrivalled levels of + <para>The goal of HornetQ is simple and uncompromising; to bring unrivalled 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 JBoss Messaging? Here are just a few of the reasons:</para> + <para>Why use HornetQ? Here are just a few of the reasons:</para> <itemizedlist> <listitem> <para>100% open source software.</para> Modified: trunk/docs/user-manual/en/project-info.xml =================================================================== --- trunk/docs/user-manual/en/project-info.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/docs/user-manual/en/project-info.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,7 +1,7 @@ <?xml version="1.0" encoding="UTF-8"?> <chapter id="project-info"> <title>Project Information</title> - <para>The JBoss Messaging project page is <ulink url="http://www.jboss.org/jbossmessaging/" + <para>The HornetQ project page is <ulink url="http://www.jboss.org/jbossmessaging/" >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 @@ -10,9 +10,9 @@ 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/jbossmessaging">IRC channel</ulink></para> - <para>JBoss Messaging Subversion TRUNK is <ulink url="http://anonsvn.jboss.org/repos/messaging/trunk">here</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>Red Hat kindly employs developers to work full time on JBoss Messaging, the motley crew are: + <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> Modified: trunk/docs/user-manual/en/security.xml =================================================================== --- trunk/docs/user-manual/en/security.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/docs/user-manual/en/security.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,7 +1,7 @@ <?xml version="1.0" encoding="UTF-8"?> <chapter id="security"> <title>Security</title> - <para>This chapter describes how security works with JBoss Messaging and how you can configure + <para>This chapter describes how security works with HornetQ and how you can configure it. To disable security completely simply set the <literal>security-enabled</literal> property to false in the <literal>hornetq-configuration.xml</literal> file.</para> <para>For performance reasons security is cached and invalidated every so long. To change this @@ -9,13 +9,13 @@ milliseconds. The default is <literal>10000</literal> ms.</para> <section id="security.settings.roles"> <title>Role based security for addresses</title> - <para>JBoss Messaging contains a flexible role-based security model for applying security to + <para>HornetQ contains a flexible role-based security model for applying security to queues, based on their addresses.</para> - <para>As explained in <xref linkend="using-core" />, JBoss Messaging core consists + <para>As explained in <xref linkend="using-core" />, HornetQ core consists mainly of sets of queues bound to addresses. A message is sent to an address and the server looks up the set of queues that are bound to that address, the server then routes the message to those set of queues.</para> - <para>JBoss Messaging allows sets of permissions to be defined against the queues based on + <para>HornetQ allows sets of permissions to be defined against the queues based on their address. An exact match on the address can be used or a wildcard match can be used using the wildcard characters '<literal>#</literal>' and '<literal>*</literal>'.</para> <para>Seven different permissions can be given to the set of queues which match the address. @@ -82,7 +82,7 @@ can send messages to these addresses or consume messages from queues bound to an address that starts with the string "globalqueues.europe."</para> <para>The mapping between a user and what roles they have is handled by the security - manager. JBoss Messaging ships with a user manager that reads user credentials from a + manager. HornetQ ships with a user manager that reads user credentials from a file on disk, and can also plug into JAAS or JBoss Application Server security.</para> <para>For more information on configuring the security manager, please see <xref linkend="change-security-manager" />.</para> @@ -117,14 +117,14 @@ <section> <title>Secure Sockets Layer (SSL) Transport</title> <para>When messaging clients are connected to servers, or servers are connected to other - servers (e.g. via bridges) over an untrusted network then JBoss Messaging allows that + servers (e.g. via bridges) over an untrusted network then HornetQ allows that traffic to be encrypted using the Secure Sockets Layer (SSL) transport.</para> <para>For more information on configuring the SSL transport, please see <xref linkend="configuring-transports" />.</para> </section> <section> <title>Basic user credentials</title> - <para> JBoss Messaging ships with a security manager implementation that reads user + <para> HornetQ ships with a security manager implementation that reads user credentials, i.e. user names, passwords and role information from an xml file on the classpath called <literal>hornetq-users.xml</literal>. This is the default security manager.</para> @@ -182,7 +182,7 @@ <para>The class <literal >org.hornetq.core.security.impl.HornetQSecurityManagerImpl</literal> is the default security manager that reads used by the standalone server.</para> - <para>JBoss Messaging ships with two other security manager implementations you can use + <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 Sever security, alternatively you could write your own implementation by implementing the <literal>org.hornetq.core.security.SecurityManager</literal> @@ -231,12 +231,12 @@ <section> <title>Example</title> <para>See <xref linkend="examples.jaas" /> for an example which - shows how JBoss Messaging can be configured to use JAAS.</para> + shows how HornetQ can be configured to use JAAS.</para> </section> </section> <section> <title>JBoss AS Security Manager</title> - <para>The JBoss AS security manager is used when running JBoss Messaging inside the JBoss + <para>The JBoss AS security manager is used when running HornetQ inside the JBoss Application server. This allows tight integration with the JBoss Application Server's security model.</para> <para>The class name of this security manager is <literal Modified: trunk/docs/user-manual/en/send-guarantees.xml =================================================================== --- trunk/docs/user-manual/en/send-guarantees.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/docs/user-manual/en/send-guarantees.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -4,7 +4,7 @@ Acknowledgements</title> <section> <title>Guarantees of Transaction Completion</title> - <para>When committing or rolling back a transaction with JBoss Messaging, the request to + <para>When committing or rolling back a transaction with HornetQ, the request to commit or rollback is sent to the server, and the call will block on the client side until a response has been received from the server that the commit or rollback was executed.</para> @@ -74,7 +74,7 @@ <section id="send-guarantees.nontrans.acks"> <title>Guarantees of Non Transactional Acknowledgements</title> <para>If you are acknowledging the delivery of a message at the client side using a non - transacted session, JBoss Messaging can be configured to block the call to acknowledge + transacted session, HornetQ can be configured to block the call to acknowledge until the acknowledge has definitely reached the server, and a response has been sent back to the client. This is configured with the parameter <literal >BlockOnAcknowledge</literal>. If this is set to <literal>true</literal> then all @@ -88,7 +88,7 @@ <title>Asynchronous Send Acknowledgements</title> <para>If you are using a non transacted session but want a guarantee that every message sent to the server has reached it, then, as discussed in <xref - linkend="non-transactional-sends"/>, you can configure JBoss Messaging to block the + linkend="non-transactional-sends"/>, you can configure HornetQ to block the call to send until the server has received the message, persisted it and sent back a response. This works well but has a severe performance penalty - each call to send needs to block for at least the time of a network round trip (RTT) - the performance of @@ -104,7 +104,7 @@ * 1024 * 1024 / 8) / 1500 = 89478 messages per second if messages are sent without 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, JBoss Messaging provides an advanced new feature called + <para>To remedy this, HornetQ provides an advanced new feature called <emphasis>asynchronous send acknowledgements</emphasis>. With this feature, JBoss Messaging can be configured to send messages without blocking in one direction and asynchronously getting acknowledgement from the server that the messages were received @@ -121,7 +121,7 @@ <para>Then, you just send messages as normal using your <literal >ClientSession</literal>, and as messages reach the server, the server will send back an acknowledgment of the send asynchronously, and some time later you are - informed at the client side by JBoss Messaging calling your handler's <literal + informed at the client side by HornetQ calling your handler's <literal >sendAcknowledged(ClientMessage message)</literal> method, passing in a reference to the message that was sent.</para> <para>Please see <xref linkend="asynchronous-send-acknowledgements-example" /> Modified: trunk/docs/user-manual/en/thread-pooling.xml =================================================================== --- trunk/docs/user-manual/en/thread-pooling.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/docs/user-manual/en/thread-pooling.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,13 +1,13 @@ <?xml version="1.0" encoding="UTF-8"?> <chapter id="thread-pooling"> <title>Thread management</title> - <para>This chapter describes how JBoss Messaging uses and pools threads and how you can manage + <para>This chapter describes how HornetQ uses and pools threads and how you can manage them.</para> <para>First we'll discuss how threads are managed and used on the server side, then we'll look at the client side.</para> <section> <title>Server-Side Thread Management</title> - <para>Each JBoss Messaging Server maintains a single thread pool for general use, and a + <para>Each HornetQ Server maintains a single thread pool for general use, and a scheduled thread pool for scheduled use. A Java scheduled thread pool cannot be configured to use a standard thread pool, otherwise we could use a single thread pool for both scheduled and non scheduled activity.</para> @@ -61,7 +61,7 @@ <title>Asynchronous IO</title> <para>Asynchronous IO has a thread pool for receiving and dispatching events out of the native layer. You will find it on a thread dump with the prefix JBM-AIO-poller-pool. - JBoss Messaging uses one thread per opened file on the journal (there is usually + HornetQ uses one thread per opened file on the journal (there is usually one).</para> <para>There is also a single thread used to invoke writes on libaio. We do that to avoid context switching on libaio what would cause performance issues. You will find this @@ -70,12 +70,12 @@ </section> <section id="thread-pooling.client.side"> <title>Client-Side Thread Management</title> - <para>On the client side, JBoss Messaging maintains a single static scheduled thread pool + <para>On the client side, HornetQ maintains a single static scheduled thread pool and a single static general thread pool for use by all clients using the same classloader in that JVM instance.</para> <para>The static scheduled thread pool has a maximum size of <literal>2</literal> threads, and the general purpose thread pool has an unbounded maximum size.</para> - <para>If required JBoss Messaging can also be configured so that each <literal + <para>If required HornetQ can also be configured so that each <literal >ClientSessionFactory</literal> instance does not use these static pools but instead maintains its own scheduled and general purpose pool. Any sessions created from that <literal>ClientSessionFactory</literal> will use those pools instead.</para> Modified: trunk/docs/user-manual/en/transaction-config.xml =================================================================== --- trunk/docs/user-manual/en/transaction-config.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/docs/user-manual/en/transaction-config.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,12 +1,12 @@ <?xml version="1.0" encoding="UTF-8"?> <chapter id="transaction-config"> <title>Resource Manager Configuration</title> - <para>JBoss Messaging has its own Resource Manager for handling the lifespan of XA transactions. + <para>HornetQ has its own Resource Manager for handling the lifespan of XA transactions. When a transaction is started the resource manager is notified and keeps a record of the transaction and its current state. It is possible in some cases for a transaction to be started but the forgotten about. Maybe the client died and never came back. If this happens then the transaction will just sit there indefinitely.</para> - <para>To cope with this JBoss Messaging can, if configured, scan for old transactions and + <para>To cope with this HornetQ can, if configured, scan for old transactions and rollback any it finds. The default for this is 60000 milliseconds (1 minute), i.e. any transactions older than 60 seconds are removed, however this can be changed by editing the <literal>transaction-timeout</literal> property in <literal Modified: trunk/docs/user-manual/en/undelivered-messages.xml =================================================================== --- trunk/docs/user-manual/en/undelivered-messages.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/docs/user-manual/en/undelivered-messages.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -35,7 +35,7 @@ <redelivery-delay>5000</redelivery-delay> </address-setting> </programlisting> - <para>If a <literal>redelivery-delay</literal> is specified, JBoss Messaging will wait this + <para>If a <literal>redelivery-delay</literal> is specified, HornetQ will wait this delay before redelivering the messages</para> <para>By default, there is no redelivery delay (<literal>redelivery-delay</literal>is set to 0).</para> @@ -56,7 +56,7 @@ queue and send instead to a dead letter address. </para> <para>Any dead letter messages can then be diverted to queue(s) where they can later be perused by the system administrator for action to be taken.</para> - <para>JBoss Messaging's addresses can be assigned a dead letter address. Once the messages + <para>HornetQ's addresses can be assigned a dead letter address. Once the messages have be unsuccessfully delivered for a given number of attempts, they are removed from the queue and sent to the dead letter address. These <emphasis>dead letter</emphasis> messages can later be consumed for further inspection.</para> @@ -102,7 +102,7 @@ </section> <section id="configuring.delivery.count.persistence"> <title>Delivery Count Persistence</title> - <para>In normal use, JBoss Messaging does not update delivery count + <para>In normal use, HornetQ does not update delivery count <emphasis>persistently</emphasis> until a message is rolled back (i.e. the delivery count is not updated <emphasis>before</emphasis> the message is delivered to the consumer). In most messaging use cases, the messages are consumed, acknowledged and forgotten as soon @@ -114,7 +114,7 @@ not have been reflected in the delivery count. During the recovery phase, the server will not have knowledge of that and will deliver the message with <literal>redelivered</literal> set to <literal>false</literal> while it should be <literal>true</literal>. </para> - <para>As this behavior breaks strict JMS semantics, JBoss Messaging allows to persist delivery + <para>As this behavior breaks strict JMS semantics, HornetQ allows to persist delivery count before message delivery but disabled it by default for performance implications.</para> <para>To enable it, set <literal>persist-delivery-count-before-delivery</literal> to <literal Modified: trunk/docs/user-manual/en/using-core.xml =================================================================== --- trunk/docs/user-manual/en/using-core.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/docs/user-manual/en/using-core.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,7 +1,7 @@ <?xml version="1.0" encoding="UTF-8"?> <chapter id="using-core"> <title>Using Core</title> - <para>JBoss Messaging core is a completely JMS-agnostic messaging system with its own core + <para>HornetQ core is a completely JMS-agnostic messaging system with its own core API.</para> <para>If you don't want to use JMS you can use the core API directly. The core API provides all the functionality of JMS but without much of the complexity. It also provides features that @@ -28,9 +28,9 @@ will survive a server crash or restart. Non durable messages will never survive a server crash or restart.</para> <para>Messages can be specified with a priority value between 0 and 9. 0 represents the - highest priority and 9 represents the lowest. JBoss Messaging will attempt to + highest priority and 9 represents the lowest. HornetQ will attempt to deliver higher priority messages before lower priority ones.</para> - <para>Messages can be specified with an optional expiry time. JBoss Messaging will not + <para>Messages can be specified with an optional expiry time. HornetQ will not deliver messages after its expiry time has been exceeded.</para> <para>Messages also have an optional timestamp which represents the time the message was sent.</para> Modified: trunk/docs/user-manual/en/using-jms.xml =================================================================== --- trunk/docs/user-manual/en/using-jms.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/docs/user-manual/en/using-jms.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,19 +1,19 @@ <?xml version="1.0" encoding="UTF-8"?> <chapter id="using-jms"> <title>Using JMS</title> - <para>Although JBoss Messaging provides a JMS agnostic messaging API, many users will be more + <para>Although HornetQ provides a JMS agnostic messaging API, many users will be more comfortable using JMS.</para> <para>JMS is a very popular API standard for messaging, and most messaging systems provide a JMS API. If you are completely new to JMS we suggest you following the<ulink url="http://java.sun.com/products/jms/tutorial/1_3_1-fcs/doc/jms_tutorialTOC.html"> Sun JMS tutorial</ulink> - a full JMS tutorial is out of scope for this guide.</para> - <para>JBoss Messaging also ships with a wide range of examples, many of which demonstrate JMS + <para>HornetQ also ships with a wide range of examples, many of which demonstrate JMS API usage. A good place to start would be to play around with the simple JMS Queue and Topic example, but we also provide examples for many other parts of the JMS API. A full description of the examples is available in <xref linkend="examples"/>.</para> <para>In this section we'll go through the main steps in configuring the server for JMS and creating a simple JMS program. We'll also show how to configure and use JNDI, and also how - to use JMS with JBoss Messaging without using any JNDI.</para> + to use JMS with HornetQ without using any JNDI.</para> <section> <title>A simple ordering system</title> <para>For this chapter we're going to use a very simple ordering system as our example. It's @@ -143,7 +143,7 @@ Objects</emphasis> (that's JMS Queues, Topics and Connection Factories) from JNDI, in some cases a JNDI server is not available and you still want to use JMS, or you just think "Why do I need JNDI? Why can't I just instantiate these objects directly?"</para> - <para>With JBoss Messaging you can do exactly that. JBoss Messaging supports the direct + <para>With HornetQ you can do exactly that. HornetQ supports the direct instantiation of JMS Queue, Topic and Connection Factory instances, so you don't have to use JNDI at all.</para> <para>For a full working example of direct instantiation please see the JMS examples in Modified: trunk/docs/user-manual/en/using-server.xml =================================================================== --- trunk/docs/user-manual/en/using-server.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/docs/user-manual/en/using-server.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,11 +1,11 @@ <?xml version="1.0" encoding="UTF-8"?> <chapter id="using-server"> <title>Using the Server</title> - <para>This chapter will familiarise you with how to use the JBoss Messaging server.</para> + <para>This chapter will familiarise you with how to use the HornetQ server.</para> <para>We'll show where it is, how to start and stop it, and we'll describe the directory layout and what all the files are and what they do.</para> - <para>For the remainder of this chapter when we talk about the JBoss Messaging server we mean - the JBoss Messaging standalone server, in its default configuration with a JMS Service and + <para>For the remainder of this chapter when we talk about the HornetQ server we mean + the HornetQ standalone server, in its default configuration with a JMS Service and JNDI service enabled.</para> <para>When running embedded in JBoss Application Server the layout may be slightly different but by-and-large will be the same.</para> @@ -19,12 +19,12 @@ <para>To run on Windows type <literal>run.bat</literal></para> <para>These scripts are very simple and basically just set-up the classpath and some JVM parameters and start the JBoss Microcontainer. The Microcontainer is a light weight - container used to deploy the JBoss Messaging POJO's</para> + container used to deploy the HornetQ POJO's</para> <para>To stop the server you'll also find a unix/linux script <literal>stop.sh</literal> and a windows batch file <literal>run.bat</literal></para> <para>To run on Unix/Linux type <literal>./stop.sh</literal></para> <para>To run on Windows type <literal>stop.bat</literal></para> - <para>Please note that JBoss Messaging requires a Java 5 or later JDK to run. We recommend + <para>Please note that HornetQ requires a Java 5 or later JDK to run. We recommend running on Java 6.</para> <para>Both the run and the stop scripts use the config under <literal >config/stand-alone/non-clustered</literal> by default. The configuration can be @@ -38,7 +38,7 @@ settings for tuning running on Java 6 and choosing the garbage collection policy. We recommend using a parallel garbage collection algorithm to smooth out latency and minimises large GC pauses.</para> - <para>By default JBoss Messaging runs in a maximum of 1GB of RAM. To increase the memory + <para>By default HornetQ runs in a maximum of 1GB of RAM. To increase the memory settings change the <literal>-Xms</literal> and <literal>-Xmx</literal> memory settings as you would for any Java program.</para> <para>If you wish to add any more JVM arguments or tune the existing ones, the run scripts @@ -46,12 +46,12 @@ </section> <section> <title>Server classpath</title> - <para>JBoss Messaging looks for its configuration files on the Java classpath.</para> + <para>HornetQ looks for its configuration files on the Java classpath.</para> <para>The scripts <literal>run.sh</literal> and <literal>run.bat</literal> specify the classpath when calling Java to run the server.</para> <para>In the distribution, the run scripts will add the non clustered configuration directory to the classpath. This is a directory which contains a set of configuration - files for running the JBoss Messaging server in a basic non-clustered configuration. In + files for running the HornetQ server in a basic non-clustered configuration. In the distribution this directory is <literal>config/stand-alone/non-clustered/</literal> from the root of the distribution.</para> <para>The distribution contains several standard configuration sets for running:</para> @@ -71,7 +71,7 @@ </itemizedlist> <para>You can of course create your own configuration and specify any configuration directory when running the run script.</para> - <para>Just make sure the directory is on the classpath and JBoss Messaging will search there + <para>Just make sure the directory is on the classpath and HornetQ will search there when starting up.</para> </section> <section id="using-server.library.path"> @@ -84,9 +84,9 @@ </section> <section> <title>System properties</title> - <para>JBoss Messaging also takes a couple of Java system properties on the command line for + <para>HornetQ also takes a couple of Java system properties on the command line for configuring logging properties</para> - <para>JBoss Messaging uses JDK logging to minimise dependencies on other logging systems. + <para>HornetQ uses JDK logging to minimise dependencies on other logging systems. JDK logging can then be configured to delegate to some other framework, e.g. log4j if that's what you prefer.</para> <para>For more information on configuring logging, please see <xref linkend="logging" @@ -101,14 +101,14 @@ <listitem> <para><literal>hornetq-jboss-beans.xml</literal>. This is the JBoss Microcontainer beans file which defines what beans the Microcontainer should create and what - dependencies to enforce between them. Remember that JBoss Messaging is just a + dependencies to enforce between them. Remember that HornetQ is just a set of POJOs. In the stand-alone server, it's the JBoss Microcontainer which instantiates these POJOs and enforces dependencies between them and other beans. Please see <xref linkend="usingserver.mainconfig"/> for more information on this file.</para> </listitem> <listitem> - <para><literal>hornetq-configuration.xml</literal>. This is the main JBoss Messaging + <para><literal>hornetq-configuration.xml</literal>. This is the main HornetQ configuration file. All the parameters in this file are described in <xref linkend="configuration-index"/>.</para> </listitem> @@ -124,7 +124,7 @@ found.</para> </listitem> <listitem> - <para><literal>hornetq-users.xml</literal> JBoss Messaging ships with a security manager + <para><literal>hornetq-users.xml</literal> HornetQ ships with a security manager implementation which obtains user credentials from the <literal >hornetq-users.xml</literal> file. This file contains user, password and role information. For more information on security ,please see <xref @@ -243,7 +243,7 @@ </deployment></programlisting> </para> - <para>We can see that, as well as the core JBoss Messaging server, the stand-alone server + <para>We can see that, as well as the core HornetQ server, the stand-alone server instantiates various different POJOs, lets look at them in turn:</para> <itemizedlist> <listitem> @@ -293,10 +293,10 @@ </section> <section id="usingserver.mainconfig"> <title>The main configuration file.</title> - <para>The configuration for the JBoss Messaging core server is contained in <literal + <para>The configuration for the HornetQ core server is contained in <literal >hornetq-configuration.xml</literal>. This is what the FileConfiguration bean uses to configure the messaging server.</para> - <para>There are many attributes which you can configure JBoss Messaging. In most cases the + <para>There are many attributes which you can configure HornetQ. In most cases the defaults will do fine, in fact every attribute can be defaulted which means a file with a single empty <literal>configuration</literal> element is a valid configuration file. The different configuration will be explained throughout the manual or you can refer to Modified: trunk/docs/user-manual/en/wildcard-routing.xml =================================================================== --- trunk/docs/user-manual/en/wildcard-routing.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/docs/user-manual/en/wildcard-routing.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,7 +1,7 @@ <?xml version="1.0" encoding="UTF-8"?> <chapter id="wildcard-routing"> <title>Routing Messages With Wild Cards</title> - <para>JBoss Messaging allows the routing of messages via wildcard addresses.</para> + <para>HornetQ allows the routing of messages via wildcard addresses.</para> <para>If a consumer is created with an address of say <literal>queue.news.#</literal> then it will receive any messages sent to addresses that match this, for instance <literal >queue.news.europe</literal> or <literal>queue.news.usa</literal> or <literal Modified: trunk/docs/user-manual/en/wildcard-syntax.xml =================================================================== --- trunk/docs/user-manual/en/wildcard-syntax.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/docs/user-manual/en/wildcard-syntax.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,10 +1,10 @@ <?xml version="1.0" encoding="UTF-8"?> <chapter id="wildcard-syntax"> - <title>Understanding the JBoss Messaging Wildcard Syntax</title> - <para>JBoss Messaging uses a specific syntax for representing wildcards in security settings, + <title>Understanding the HornetQ Wildcard Syntax</title> + <para>HornetQ uses a specific syntax for representing wildcards in security settings, address settings and when creating consumers.</para> <para>The syntax is similar to that used by <ulink url="www.amqp.org">AMQP</ulink>.</para> - <para>A JBoss Messaging wildcard expression contains words delimited by the character '<literal + <para>A HornetQ wildcard expression contains words delimited by the character '<literal >.</literal>' (full stop).</para> <para>The special characters '<literal>#</literal>' and '<literal>*</literal>' also have special meaning and can take the place of a word.</para> Modified: trunk/examples/core/embedded/build.xml =================================================================== --- trunk/examples/core/embedded/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/core/embedded/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -15,7 +15,7 @@ ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging Embedded Example"> +<project default="run" name="HornetQ Embedded Example"> <import file="../../common/build.xml"/> Modified: trunk/examples/core/embedded/readme.html =================================================================== --- trunk/examples/core/embedded/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/core/embedded/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,16 +1,16 @@ <html> <head> - <title>JBoss Messaging Embedded Example</title> + <title>HornetQ Embedded Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> <h1>Embedded Example</h1> <br> - <p>This examples shows how to setup and run JBoss Messaging embedded.</p> - <p>JBoss Messaging was designed to use POJOs (Plain Old Java Objects), what makes embedding JBoss Messaging as simple as instantiating a few objects.</p> + <p>This examples shows how to setup and run HornetQ embedded.</p> + <p>HornetQ was designed to use POJOs (Plain Old Java Objects), what makes embedding HornetQ as simple as instantiating a few objects.</p> <p>On this example, we are only using one jar (hornetq-core.jar).</p> - <p>JBoss Messaging Embedded could be used from very simple use cases with only InVM support to very complex cases with clustering, persistence and fail over.</p> + <p>HornetQ Embedded could be used from very simple use cases with only InVM support to very complex cases with clustering, persistence and fail over.</p> <br> <h2>Example step-by-step</h2> <p><i>To run the example, simply type <code>ant</code> from this directory</i></p> Modified: trunk/examples/core/embedded/src/org/hornetq/core/example/EmbeddedExample.java =================================================================== --- trunk/examples/core/embedded/src/org/hornetq/core/example/EmbeddedExample.java 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/core/embedded/src/org/hornetq/core/example/EmbeddedExample.java 2009-08-20 15:17:39 UTC (rev 7830) @@ -30,7 +30,7 @@ /** * - * This exammple shows how to run a JBoss Messaging core client and server embedded in your + * This exammple shows how to run a HornetQ core client and server embedded in your * own application * * @author <a href="mailto:tim.fox@jboss.com">Tim Fox</a> Modified: trunk/examples/core/embedded-remote/build.xml =================================================================== --- trunk/examples/core/embedded-remote/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/core/embedded-remote/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -15,7 +15,7 @@ ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging Embedded Example"> +<project default="run" name="HornetQ Embedded Example"> <import file="../../common/build.xml"/> Modified: trunk/examples/core/embedded-remote/readme.html =================================================================== --- trunk/examples/core/embedded-remote/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/core/embedded-remote/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,13 +1,13 @@ <html> <head> - <title>JBoss Messaging Embedded Example</title> + <title>HornetQ Embedded Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"/> </head> <body> <h1>Embedded Example</h1> <br/> - <p>This examples shows how to setup and run JBoss Messaging embedded with remote clients connecting.</p> - <p>JBoss Messaging was designed to use POJOs (Plain Old Java Objects), what makes embedding JBoss Messaging as simple as instantiating a few objects.</p> + <p>This examples shows how to setup and run HornetQ embedded with remote clients connecting.</p> + <p>HornetQ was designed to use POJOs (Plain Old Java Objects), what makes embedding HornetQ as simple as instantiating a few objects.</p> <p>We have limited the server classpath on this example:</p> <ol> @@ -24,7 +24,7 @@ <li>netty.jar</li> </ol> - <p>JBoss Messaging Embedded could be used from very simple use cases with only InVM support to very complex cases with clustering, persistence and fail over.</p> + <p>HornetQ Embedded could be used from very simple use cases with only InVM support to very complex cases with clustering, persistence and fail over.</p> <h2>Example step-by-step</h2> Modified: trunk/examples/core/embedded-remote/src/org/hornetq/core/example/EmbeddedRemoteExample.java =================================================================== --- trunk/examples/core/embedded-remote/src/org/hornetq/core/example/EmbeddedRemoteExample.java 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/core/embedded-remote/src/org/hornetq/core/example/EmbeddedRemoteExample.java 2009-08-20 15:17:39 UTC (rev 7830) @@ -27,7 +27,7 @@ /** * - * This exammple shows how to run a JBoss Messaging core client and server embedded in your + * This exammple shows how to run a HornetQ core client and server embedded in your * own application * * @author <a href="mailto:tim.fox@jboss.com">Tim Fox</a> Modified: trunk/examples/core/microcontainer/build.xml =================================================================== --- trunk/examples/core/microcontainer/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/core/microcontainer/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -15,7 +15,7 @@ ~ implied. See the License for the specific language governing ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging Example with Micro Container"> +<project default="run" name="HornetQ Example with Micro Container"> <import file="../../common/build.xml"/> Modified: trunk/examples/core/microcontainer/readme.html =================================================================== --- trunk/examples/core/microcontainer/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/core/microcontainer/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,12 +1,12 @@ <html> <head> - <title>JBoss Messaging Embedded Example</title> + <title>HornetQ Embedded Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"/> </head> <body> <h1>Example Micro Container</h1> <br/> - <p>This examples shows how to setup and run JBoss Messaging through the Micro Container.</p> + <p>This examples shows how to setup and run HornetQ through the Micro Container.</p> <p>Refer to the user's manual for the list of required Jars, since JBoss Micro Container requires a few jars.</p> <h2>Example step-by-step</h2> <p><i>To run the example, simply type <code>ant</code> from this directory</i></p> Modified: trunk/examples/core/microcontainer/src/org/hornetq/core/example/EmbeddedMicroContainerExample.java =================================================================== --- trunk/examples/core/microcontainer/src/org/hornetq/core/example/EmbeddedMicroContainerExample.java 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/core/microcontainer/src/org/hornetq/core/example/EmbeddedMicroContainerExample.java 2009-08-20 15:17:39 UTC (rev 7830) @@ -27,7 +27,7 @@ /** * - * This exammple shows how to run a JBoss Messaging core client and server embedded in your + * This exammple shows how to run a HornetQ core client and server embedded in your * own application * * @author <a href="mailto:tim.fox@jboss.com">Tim Fox</a> Modified: trunk/examples/core/perf/build.xml =================================================================== --- trunk/examples/core/perf/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/core/perf/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -14,7 +14,7 @@ ~ implied. See the License for the specific language governing ~ permissions and limitations under the License. --> -<project name="JBoss Messaging Perf Example"> +<project name="HornetQ Perf Example"> <import file="../../common/build.xml"/> Modified: trunk/examples/javaee/ejb-jms-transaction/build.xml =================================================================== --- trunk/examples/javaee/ejb-jms-transaction/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/javaee/ejb-jms-transaction/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -12,7 +12,7 @@ ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging Java EE EJB using JMS Example"> +<project default="run" name="HornetQ Java EE EJB using JMS Example"> <import file="../common/build.xml"/> Modified: trunk/examples/javaee/ejb-jms-transaction/readme.html =================================================================== --- trunk/examples/javaee/ejb-jms-transaction/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/javaee/ejb-jms-transaction/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,12 +1,12 @@ <html> <head> - <title>JBoss Messaging EJB/JMS Transaction Example</title> + <title>HornetQ EJB/JMS Transaction Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> <h1>EJB/JMS Transaction Example</h1> - <p>This example will show how to run JBoss Messaging in JBoss AS (Application Server).</p> + <p>This example will show how to run HornetQ in JBoss AS (Application Server).</p> <p>The example application will invoke an EJB which will (1) send a JMS message, (2) update a database from the same transaction.<br /> @@ -15,7 +15,7 @@ <h2>Example configuration</h2> - <p>To run the example, you need to download JBoss AS 5.x and create a configuration for JBoss Messaging.</p> + <p>To run the example, you need to download JBoss AS 5.x and create a configuration for HornetQ.</p> <p>The example also requires a database. The instructions are for MySQL. If you use another database, please refer to the database documentation to configure it.</p> <p>The example makes a copy of the default-with-hornetq profile so please configure this for the database</p> @@ -23,7 +23,7 @@ <h3>JBoss AS configuration</h3> - <p>Please refer to JBoss Messaging Quickstart guide to <a href="../../../docs/quickstart-guide/en/html_single/index.html#installation.jboss">install it in JBoss AS 5<a></p> + <p>Please refer to HornetQ Quickstart guide to <a href="../../../docs/quickstart-guide/en/html_single/index.html#installation.jboss">install it in JBoss AS 5<a></p> <h3>Database configuration</h3> Modified: trunk/examples/javaee/hajndi/build.xml =================================================================== --- trunk/examples/javaee/hajndi/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/javaee/hajndi/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -11,7 +11,7 @@ ~ implied. See the License for the specific language governing ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging Java HAJNDI Example"> +<project default="run" name="HornetQ Java HAJNDI Example"> <import file="../common/build.xml"/> Modified: trunk/examples/javaee/hajndi/readme.html =================================================================== --- trunk/examples/javaee/hajndi/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/javaee/hajndi/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,6 +1,6 @@ <html> <head> - <title>JBoss Messaging Java EE HAJNDI Example</title> + <title>HornetQ Java EE HAJNDI Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> @@ -16,9 +16,9 @@ <p>With HA-JNDI the client can be simplify configured with UDP address parameters and can transparently perform JNDI lookups without having to worry about a particular server being unavailable.</p> <p>HA-JNDI is a service of JBoss Application Server and is not available by default when running against - a stand-alone JBoss Messaging instance.</> + a stand-alone HornetQ instance.</> <p>An alternative approach is to avoid JNDI together and directly instantiate JMS Connection Factory, - Queue and Topic instances on the client side. JBoss Messaging Connection Factory instances can + Queue and Topic instances on the client side. HornetQ Connection Factory instances can also be configured to use UDP discovery so the specific details of the available servers are not required on the client side.</p> <p>For more information on instantiating Connection Factory objects directly please see the user @@ -28,9 +28,9 @@ <h2>Example configuration</h2> - <p>To run the example, you need to download JBoss AS 5.x and create a clustered configuration for JBoss Messaging.</p> + <p>To run the example, you need to download JBoss AS 5.x and create a clustered configuration for HornetQ.</p> - <p>Please refer to JBoss Messaging Quickstart guide to <a href="../../../docs/quickstart-guide/en/html_single/index.html#installation.jboss">install it in JBoss AS 5<a></p> + <p>Please refer to HornetQ Quickstart guide to <a href="../../../docs/quickstart-guide/en/html_single/index.html#installation.jboss">install it in JBoss AS 5<a></p> <p>To run this example, we will need two clustered profiles, one for each server instance:</li> <li>Copy the directory <code>$JBOSS_HOME/server/all-with-hornetq</code> to <code>$JBOSS_HOME/server/all-with-hornetq_2</code></li> Modified: trunk/examples/javaee/jca-config/build.xml =================================================================== --- trunk/examples/javaee/jca-config/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/javaee/jca-config/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -12,7 +12,7 @@ ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging Java EE JCA Config Example"> +<project default="run" name="HornetQ Java EE JCA Config Example"> <import file="../common/build.xml"/> Modified: trunk/examples/javaee/jca-config/readme.html =================================================================== --- trunk/examples/javaee/jca-config/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/javaee/jca-config/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,14 +1,14 @@ <html> <head> - <title>JBoss Messaging Java EE JCA Configuration Example</title> + <title>HornetQ Java EE JCA Configuration Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> <h1>Java EE Resource Adapter Configuration Example</h1> - <p>This example demonstrates how to configure several properties on the JBoss Messaging Resource Adapter. We setup two JBoss Servers. The enterprise application is being deployed in one application server while the MDBs and JMS Connections are pointing to a remote server</p> + <p>This example demonstrates how to configure several properties on the HornetQ Resource Adapter. We setup two JBoss Servers. The enterprise application is being deployed in one application server while the MDBs and JMS Connections are pointing to a remote server</p> <p>This example is composed by two MDBs (MDBQueueA and MDBQueueB) and a StatlessSessionBean (StatelessSender). The main class (MDBRemoteClientExample) will call a method on StatelessSender and send a Message to Queue B.<p> <p>StatelessSender will send a message to Queue A and it is getting the connection out of the JavaConnectionArchitecture (JCA) ConnectionFactory, and sending a message to QueueA which will be received on MDBQueueA.</p> - <p>MDBQueueB is connected to a different JBoss Messaging resource-adapter, and it will receive the message sent by the main Class.</p> + <p>MDBQueueB is connected to a different HornetQ resource-adapter, and it will receive the message sent by the main Class.</p> <p>All the MDBs and JMS Connections are referring to the remote server</p> <p>A Resource Adapter is a way to connect any system provider to an application server, and is integral part of the Java Connectors Architecture specification.</p> <p>JBossMessaging provides its own adapter and this example will provide you a quick tutorial on how to configure some of the default properties, and how to change the default values on MDB Inbound Properties, or on ConnectionFactory Outbound Properties.</p> @@ -129,11 +129,11 @@ </code> </pre> - <p>Refer to the <i>Resource Adapter</i> Chapter on the <i>JBoss Messaging Documentation</i> for more information about configuring the ra.xml properties. + <p>Refer to the <i>Resource Adapter</i> Chapter on the <i>HornetQ Documentation</i> for more information about configuring the ra.xml properties. <p>You may choose to deploy multiple JBossMessaging Resource adapters on the same application server, for example if you are connecting to different HornetQ servers and if you wish to have a higher control of properties on each server you are connecting to. You will be able to determine which rar you are using individually at each <i>MDB</i> and <i>ConnectionFactory</i> as specified before here. Just copy the directory jms-ra.rar in your application as any other name with the extension .rar and use that file name at your deployments.</p> - <p>Please refer to JBoss Messaging Quickstart guide to <a href="../../../docs/quickstart-guide/en/html_single/index.html#installation.jboss">install it in JBoss AS 5<a></p> + <p>Please refer to HornetQ Quickstart guide to <a href="../../../docs/quickstart-guide/en/html_single/index.html#installation.jboss">install it in JBoss AS 5<a></p> <h2>Example step-by-step</h2> Modified: trunk/examples/javaee/jca-config/server2/ra.xml =================================================================== --- trunk/examples/javaee/jca-config/server2/ra.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/javaee/jca-config/server2/ra.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -10,8 +10,8 @@ http://java.sun.com/xml/ns/j2ee/connector_1_5.xsd" version="1.5"> - <description>JBoss Messaging 2.0 Resource Adapter Alternate Configuration</description> - <display-name>JBoss Messaging 2.0 Resource Adapter Alternate Configuration</display-name> + <description>HornetQ 2.0 Resource Adapter Alternate Configuration</description> + <display-name>HornetQ 2.0 Resource Adapter Alternate Configuration</display-name> <vendor-name>Red Hat Middleware LLC</vendor-name> <eis-type>JMS 1.1 Server</eis-type> Modified: trunk/examples/javaee/jms-bridge/build.xml =================================================================== --- trunk/examples/javaee/jms-bridge/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/javaee/jms-bridge/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -12,7 +12,7 @@ ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging JMS Bridge Example"> +<project default="run" name="HornetQ JMS Bridge Example"> <import file="../common/build.xml"/> Modified: trunk/examples/javaee/jms-bridge/readme.html =================================================================== --- trunk/examples/javaee/jms-bridge/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/javaee/jms-bridge/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,6 +1,6 @@ <html> <head> - <title>JBoss Messaging JMS Bridge Example</title> + <title>HornetQ JMS Bridge Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> @@ -9,7 +9,7 @@ <p>This example shows how to configure and run a JMS Bridge in JBoss AS 5.<br /> A bridge receives messages from a <em>source</em> JMS destination and resend them to a <em>target</em> destination.</p> <p>The source and target destinations can be on different servers, even from different JMS providers. For example, you can use this - JMS Bridge to bridge a legacy JMS provider to JBoss Messaging during migration.</p> + JMS Bridge to bridge a legacy JMS provider to HornetQ during migration.</p> <p>This example will show how to configure and run the simplest bridge:</p> <ul> @@ -22,11 +22,11 @@ <h2>Example configuration</h2> - <p>To run the example, you need to download JBoss AS 5.x and create a configuration for JBoss Messaging.</p> + <p>To run the example, you need to download JBoss AS 5.x and create a configuration for HornetQ.</p> <h3>JBoss AS configuration</h3> - <p>Please refer to JBoss Messaging Quickstart guide to <a href="../../../docs/quickstart-guide/en/html_single/index.html#installation.jboss">install it in JBoss AS 5<a></p> + <p>Please refer to HornetQ Quickstart guide to <a href="../../../docs/quickstart-guide/en/html_single/index.html#installation.jboss">install it in JBoss AS 5<a></p> <h3>JMS Bridge configuration</h3> Modified: trunk/examples/javaee/jms-bridge/server/jms-bridge-jboss-beans.xml =================================================================== --- trunk/examples/javaee/jms-bridge/server/jms-bridge-jboss-beans.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/javaee/jms-bridge/server/jms-bridge-jboss-beans.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -3,7 +3,7 @@ <deployment xmlns="urn:jboss:bean-deployer:2.0"> <bean name="JMSBridge" class="org.hornetq.jms.bridge.impl.JMSBridgeImpl"> -  +  <depends>MessagingServer</depends> <constructor>  Modified: trunk/examples/javaee/mdb-bmt/build.xml =================================================================== --- trunk/examples/javaee/mdb-bmt/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/javaee/mdb-bmt/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -11,7 +11,7 @@ ~ implied. See the License for the specific language governing ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging Java EE MDB Example"> +<project default="run" name="HornetQ Java EE MDB Example"> <import file="../common/build.xml"/> Modified: trunk/examples/javaee/mdb-bmt/readme.html =================================================================== --- trunk/examples/javaee/mdb-bmt/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/javaee/mdb-bmt/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,6 +1,6 @@ <html> <head> - <title>JBoss Messaging Java EE MDB Bean Managed Transaction Example</title> + <title>HornetQ Java EE MDB Bean Managed Transaction Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> @@ -13,7 +13,7 @@ <h2>JBoss AS configuration</h2> - <p>Please refer to JBoss Messaging Quickstart guide to <a href="../../../docs/quickstart-guide/en/html_single/index.html#installation.jboss">install it in JBoss AS 5<a></p> + <p>Please refer to HornetQ Quickstart guide to <a href="../../../docs/quickstart-guide/en/html_single/index.html#installation.jboss">install it in JBoss AS 5<a></p> <h2>Example step-by-step</h2> <p><i>To deploy and start the server, simply type <code>ant deploy</code> from the example directory</i></p> Modified: trunk/examples/javaee/mdb-cmt-setrollbackonly/build.xml =================================================================== --- trunk/examples/javaee/mdb-cmt-setrollbackonly/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/javaee/mdb-cmt-setrollbackonly/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -11,7 +11,7 @@ ~ implied. See the License for the specific language governing ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging Java EE MDB Example"> +<project default="run" name="HornetQ Java EE MDB Example"> <import file="../common/build.xml"/> Modified: trunk/examples/javaee/mdb-cmt-setrollbackonly/readme.html =================================================================== --- trunk/examples/javaee/mdb-cmt-setrollbackonly/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/javaee/mdb-cmt-setrollbackonly/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,6 +1,6 @@ <html> <head> - <title>JBoss Messaging Java EE MDB SetRollbackOnly Example</title> + <title>HornetQ Java EE MDB SetRollbackOnly Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> @@ -13,7 +13,7 @@ <h2>JBoss AS configuration</h2> - <p>Please refer to JBoss Messaging Quickstart guide to <a href="../../../docs/quickstart-guide/en/html_single/index.html#installation.jboss">install it in JBoss AS 5<a></p> + <p>Please refer to HornetQ Quickstart guide to <a href="../../../docs/quickstart-guide/en/html_single/index.html#installation.jboss">install it in JBoss AS 5<a></p> <h2>Example step-by-step</h2> <p><i>To deploy and start the server, simply type <code>ant deploy</code> from the example directory</i></p> Modified: trunk/examples/javaee/mdb-cmt-tx-local/build.xml =================================================================== --- trunk/examples/javaee/mdb-cmt-tx-local/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/javaee/mdb-cmt-tx-local/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -12,7 +12,7 @@ ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging Java EE MDB Example"> +<project default="run" name="HornetQ Java EE MDB Example"> <import file="../common/build.xml"/> Modified: trunk/examples/javaee/mdb-cmt-tx-local/readme.html =================================================================== --- trunk/examples/javaee/mdb-cmt-tx-local/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/javaee/mdb-cmt-tx-local/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,6 +1,6 @@ <html> <head> - <title>JBoss Messaging Java EE MDB using a local transaction Example</title> + <title>HornetQ Java EE MDB using a local transaction Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> @@ -13,7 +13,7 @@ <h2>JBoss AS configuration</h2> - <p>Please refer to JBoss Messaging Quickstart guide to <a href="../../../docs/quickstart-guide/en/html_single/index.html#installation.jboss">install it in JBoss AS 5<a></p> + <p>Please refer to HornetQ Quickstart guide to <a href="../../../docs/quickstart-guide/en/html_single/index.html#installation.jboss">install it in JBoss AS 5<a></p> <h2>Example step-by-step</h2> <p><i>To deploy and start the server, simply type <code>ant deploy</code> from the example directory</i></p> Modified: trunk/examples/javaee/mdb-cmt-tx-not-supported/build.xml =================================================================== --- trunk/examples/javaee/mdb-cmt-tx-not-supported/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/javaee/mdb-cmt-tx-not-supported/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -12,7 +12,7 @@ ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging Java EE MDB Example"> +<project default="run" name="HornetQ Java EE MDB Example"> <import file="../common/build.xml"/> Modified: trunk/examples/javaee/mdb-cmt-tx-not-supported/readme.html =================================================================== --- trunk/examples/javaee/mdb-cmt-tx-not-supported/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/javaee/mdb-cmt-tx-not-supported/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,6 +1,6 @@ <html> <head> - <title>JBoss Messaging Java EE MDB Container Managed Transaction with NOT_SUPPORTED transaction Example</title> + <title>HornetQ Java EE MDB Container Managed Transaction with NOT_SUPPORTED transaction Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> @@ -13,7 +13,7 @@ <h2>JBoss AS configuration</h2> - <p>Please refer to JBoss Messaging Quickstart guide to <a href="../../../docs/quickstart-guide/en/html_single/index.html#installation.jboss">install it in JBoss AS 5<a></p> + <p>Please refer to HornetQ Quickstart guide to <a href="../../../docs/quickstart-guide/en/html_single/index.html#installation.jboss">install it in JBoss AS 5<a></p> <h2>Example step-by-step</h2> <p><i>To deploy and start the server, simply type <code>ant deploy</code> from the example directory</i></p> Modified: trunk/examples/javaee/mdb-cmt-tx-required/build.xml =================================================================== --- trunk/examples/javaee/mdb-cmt-tx-required/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/javaee/mdb-cmt-tx-required/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -11,7 +11,7 @@ ~ implied. See the License for the specific language governing ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging Java EE MDB Example"> +<project default="run" name="HornetQ Java EE MDB Example"> <import file="../common/build.xml"/> Modified: trunk/examples/javaee/mdb-cmt-tx-required/readme.html =================================================================== --- trunk/examples/javaee/mdb-cmt-tx-required/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/javaee/mdb-cmt-tx-required/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,6 +1,6 @@ <html> <head> - <title>JBoss Messaging Java EE MDB Container Managed Transactions Example</title> + <title>HornetQ Java EE MDB Container Managed Transactions Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> @@ -13,7 +13,7 @@ <h2>JBoss AS configuration</h2> - <p>Please refer to JBoss Messaging Quickstart guide to <a href="../../../docs/quickstart-guide/en/html_single/index.html#installation.jboss">install it in JBoss AS 5<a></p> + <p>Please refer to HornetQ Quickstart guide to <a href="../../../docs/quickstart-guide/en/html_single/index.html#installation.jboss">install it in JBoss AS 5<a></p> <h2>Example step-by-step</h2> <p><i>To deploy and start the server, simply type <code>ant deploy</code> from the example directory</i></p> Modified: trunk/examples/javaee/mdb-message-selector/build.xml =================================================================== --- trunk/examples/javaee/mdb-message-selector/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/javaee/mdb-message-selector/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -12,7 +12,7 @@ ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging Java EE MDB Example"> +<project default="run" name="HornetQ Java EE MDB Example"> <import file="../common/build.xml"/> Modified: trunk/examples/javaee/mdb-message-selector/readme.html =================================================================== --- trunk/examples/javaee/mdb-message-selector/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/javaee/mdb-message-selector/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,6 +1,6 @@ <html> <head> - <title>JBoss Messaging Java EE MDB Message Selector Example</title> + <title>HornetQ Java EE MDB Message Selector Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> @@ -13,7 +13,7 @@ <h2>JBoss AS configuration</h2> - <p>Please refer to JBoss Messaging Quickstart guide to <a href="../../../docs/quickstart-guide/en/html_single/index.html#installation.jboss">install it in JBoss AS 5<a></p> + <p>Please refer to HornetQ Quickstart guide to <a href="../../../docs/quickstart-guide/en/html_single/index.html#installation.jboss">install it in JBoss AS 5<a></p> <h2>Example step-by-step</h2> <p><i>To deploy and start the server, simply type <code>ant deploy</code> from the example directory</i></p> Modified: trunk/examples/javaee/mdb-tx-send/build.xml =================================================================== --- trunk/examples/javaee/mdb-tx-send/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/javaee/mdb-tx-send/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -12,7 +12,7 @@ ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging Java EE MDB Example"> +<project default="run" name="HornetQ Java EE MDB Example"> <import file="../common/build.xml"/> Modified: trunk/examples/javaee/mdb-tx-send/readme.html =================================================================== --- trunk/examples/javaee/mdb-tx-send/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/javaee/mdb-tx-send/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,6 +1,6 @@ <html> <head> - <title>JBoss Messaging Java EE MDB Send Example</title> + <title>HornetQ Java EE MDB Send Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> @@ -13,7 +13,7 @@ <h2>JBoss AS configuration</h2> - <p>Please refer to JBoss Messaging Quickstart guide to <a href="../../../docs/quickstart-guide/en/html_single/index.html#installation.jboss">install it in JBoss AS 5<a></p> + <p>Please refer to HornetQ Quickstart guide to <a href="../../../docs/quickstart-guide/en/html_single/index.html#installation.jboss">install it in JBoss AS 5<a></p> <h2>Example step-by-step</h2> <p><i>To deploy and start the server, simply type <code>ant deploy</code> from the example directory</i></p> Modified: trunk/examples/javaee/servlet-ssl-example/build.xml =================================================================== --- trunk/examples/javaee/servlet-ssl-example/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/javaee/servlet-ssl-example/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -12,7 +12,7 @@ ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging Servlet Transport Example"> +<project default="run" name="HornetQ Servlet Transport Example"> <import file="../common/build.xml"/> Modified: trunk/examples/javaee/servlet-ssl-example/readme.html =================================================================== --- trunk/examples/javaee/servlet-ssl-example/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/javaee/servlet-ssl-example/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,16 +1,16 @@ <html> <head> - <title>JBoss Messaging Java EE Servlet SSL Example</title> + <title>HornetQ Java EE Servlet SSL Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> <h1>Java EE Servlet SSL Example</h1> <br> - <p>This example shows you how to configure and use servlet transport over SSL with JBoss Messaging.</p> + <p>This example shows you how to configure and use servlet transport over SSL with HornetQ.</p> <h2>JBoss AS configuration</h2> - <p>Please refer to JBoss Messaging Quickstart guide to <a href="../../../docs/quickstart-guide/en/html_single/index.html#installation.jboss">install it in JBoss AS 5<a></p> + <p>Please refer to HornetQ Quickstart guide to <a href="../../../docs/quickstart-guide/en/html_single/index.html#installation.jboss">install it in JBoss AS 5<a></p> <h2>Example configuration</h2> Modified: trunk/examples/javaee/servlet-transport/build.xml =================================================================== --- trunk/examples/javaee/servlet-transport/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/javaee/servlet-transport/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -12,7 +12,7 @@ ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging Servlet Transport Example"> +<project default="run" name="HornetQ Servlet Transport Example"> <import file="../common/build.xml"/> Modified: trunk/examples/javaee/servlet-transport/readme.html =================================================================== --- trunk/examples/javaee/servlet-transport/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/javaee/servlet-transport/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,16 +1,16 @@ <html> <head> - <title>JBoss Messaging Java EE Servlet Example</title> + <title>HornetQ Java EE Servlet Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> <h1>Java EE Servlet Example</h1> <br> - <p>This example shows you how to configure and use servlet transport with JBoss Messaging.</p> + <p>This example shows you how to configure and use servlet transport with HornetQ.</p> <h2>JBoss AS configuration</h2> - <p>Please refer to JBoss Messaging Quickstart guide to <a href="../../../docs/quickstart-guide/en/html_single/index.html#installation.jboss">install it in JBoss AS 5<a></p> + <p>Please refer to HornetQ Quickstart guide to <a href="../../../docs/quickstart-guide/en/html_single/index.html#installation.jboss">install it in JBoss AS 5<a></p> <h2>Example configuration</h2> Modified: trunk/examples/javaee/xarecovery/build.xml =================================================================== --- trunk/examples/javaee/xarecovery/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/javaee/xarecovery/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -11,7 +11,7 @@ ~ implied. See the License for the specific language governing ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging XA Recovery Example"> +<project default="run" name="HornetQ XA Recovery Example"> <import file="../common/build.xml"/> Modified: trunk/examples/javaee/xarecovery/readme.html =================================================================== --- trunk/examples/javaee/xarecovery/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/javaee/xarecovery/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,12 +1,12 @@ <html> <head> - <title>JBoss Messaging XA Recovery Example</title> + <title>HornetQ XA Recovery Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> <h1>XA Recovery Example</h1> - <p>This example will show how to configure JBoss Messaging XA recovery in JBoss AS (Application Server).</p> + <p>This example will show how to configure HornetQ XA recovery in JBoss AS (Application Server).</p> <p>The example application will invoke an EJB which will send a JMS message in a transaction. The server will crash while the transaction has not been committed (it is in the prepared state).<br /> @@ -15,16 +15,16 @@ <h2>Example configuration</h2> - <p>To run the example, you need to download JBoss AS 5.x and create a configuration for JBoss Messaging.</p> - <p>You also need to configure JBoss Transactions to enable XA Recovery of JBoss Messaging resources</p> + <p>To run the example, you need to download JBoss AS 5.x and create a configuration for HornetQ.</p> + <p>You also need to configure JBoss Transactions to enable XA Recovery of HornetQ resources</p> <h3>JBoss AS configuration</h3> - <p>Please refer to JBoss Messaging Quickstart guide to <a href="../../../docs/quickstart-guide/en/html_single/index.html#installation.jboss">install it in JBoss AS 5<a></p> + <p>Please refer to HornetQ Quickstart guide to <a href="../../../docs/quickstart-guide/en/html_single/index.html#installation.jboss">install it in JBoss AS 5<a></p> <h3>XA Recovery configuration</h3> - <p>You need to enable XA Recovery of JBoss Messaging resources.</p> + <p>You need to enable XA Recovery of HornetQ resources.</p> <p>In the <code>jta</code> section of the <code>$JBOSS_HOME/server/xarecovery-example-profile//conf/jbossts-properties.xml</code> configuration file, the following property is added:</p> <pre> @@ -32,11 +32,11 @@ value="org.hornetq.jms.server.recovery.MessagingXAResourceRecovery;org.hornetq.core.remoting.impl.invm.InVMConnectorFactory"/></code> </pre> - <p>This informs the Recovery Manager that it can recovers JBoss Messaging XA Resources by connecting to the server using an <code>InVMConnectorFactory</code>. - Since the Recovery Manager is in the same server than JBoss Messaging, the examples uses intra-vm communication to recover the messaging resources. - JBoss Messaging must have configured an invm acceptor to accept this connection (see the "in-vm"<code><acceptor></code> in <code>hornetq-configuration.xml</code>).</p> + <p>This informs the Recovery Manager that it can recovers HornetQ XA Resources by connecting to the server using an <code>InVMConnectorFactory</code>. + Since the Recovery Manager is in the same server than HornetQ, the examples uses intra-vm communication to recover the messaging resources. + HornetQ must have configured an invm acceptor to accept this connection (see the "in-vm"<code><acceptor></code> in <code>hornetq-configuration.xml</code>).</p> - <p>The example copies a <code>jbossts-properties.xml</code> already configured for JBoss Messaging XA Recovery, so you + <p>The example copies a <code>jbossts-properties.xml</code> already configured for HornetQ XA Recovery, so you do not need to manually edit the profile's file.</p> <h2>Example step-by-step</h2> @@ -215,7 +215,7 @@ <p>The failing resources will crash the server leaving the JMS XA Resource <em>prepared</em> but not <em>committed</em></p> <p>You now need to restart the JBoss AS instance.<br /> - When it is restarted, it will automatically trigger a recovery phase. During that phase, JBoss Messaging resources will be + When it is restarted, it will automatically trigger a recovery phase. During that phase, HornetQ resources will be scanned and the <em>prepared</em> transaction will be recovered and committed. It is then possible to consume this message</p> <h2>More information</h2> Modified: trunk/examples/jms/application-layer-failover/build.xml =================================================================== --- trunk/examples/jms/application-layer-failover/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/application-layer-failover/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -15,7 +15,7 @@ ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging JMS Application Layer Failover Example"> +<project default="run" name="HornetQ JMS Application Layer Failover Example"> <import file="../../common/build.xml"/> Modified: trunk/examples/jms/application-layer-failover/readme.html =================================================================== --- trunk/examples/jms/application-layer-failover/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/application-layer-failover/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,24 +1,24 @@ <html> <head> - <title>JBoss Messaging Application-Layer Failover Example</title> + <title>HornetQ Application-Layer Failover Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> - <h1>JBoss Messaging Application-Layer Failover Example</h1> + <h1>HornetQ Application-Layer Failover Example</h1> <br> - <p>JBoss Messaging implements fully transparent <b>automatic</b> failover of connections from a live to backup node, this requires + <p>HornetQ implements fully transparent <b>automatic</b> failover of connections from a live to backup node, this requires no special coding for failover, and is described in a different example. Automatic failover requires server replication.</p> - <p>However, JBoss Messaging also supports <b>Application-Layer</b> failover, useful in the case that replication is not enabled + <p>However, HornetQ also supports <b>Application-Layer</b> failover, useful in the case that replication is not enabled on the server side.</p> - <p>With Application-Layer failover, it's up to the application to register a JMS ExceptionListener with JBoss Messaging which will be - called by JBoss Messaging in the event that connection failure is detected.</p> + <p>With Application-Layer failover, it's up to the application to register a JMS ExceptionListener with HornetQ which will be + called by HornetQ in the event that connection failure is detected.</p> <p>The code in the ExceptionListener then recreates the JMS Connection, Session, etc on another node and the application can continue.</p> <p>Application-Layer failover is an alternative approach to High Availabilty (HA).</p> <p>Application-Layer failover differs from automatic failover in that some client side coding is required in order to implement this. Also, with Application-Layer failover, since the old Session object dies and a new is created, any uncommitted work in the old Session will be lost, and any unacknowledged messages might be redelivered.</p> - <p>For more information on JBoss Messaging failover and HA, and clustering in general, please see the clustering + <p>For more information on HornetQ failover and HA, and clustering in general, please see the clustering section of the user manual.</p> <h2>Example step-by-step</h2> <p><i>To run the example, simply type <code>ant</code> from this directory</i></p> Modified: trunk/examples/jms/automatic-failover/build.xml =================================================================== --- trunk/examples/jms/automatic-failover/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/automatic-failover/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -15,7 +15,7 @@ ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging JMS Automatic Failover Example"> +<project default="run" name="HornetQ JMS Automatic Failover Example"> <import file="../../common/build.xml"/> Modified: trunk/examples/jms/automatic-failover/readme.html =================================================================== --- trunk/examples/jms/automatic-failover/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/automatic-failover/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,21 +1,21 @@ <html> <head> - <title>JBoss Messaging JMS Automatic (Transparent) Failover Example</title> + <title>HornetQ JMS Automatic (Transparent) Failover Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> - <h1>JBoss Messaging JMS Automatic (Transparent) Failover (HA) Example</h1> + <h1>HornetQ JMS Automatic (Transparent) Failover (HA) Example</h1> <br> <p>This example demonstrates two servers coupled as a live-backup pair for high availability (HA), and a client connection transparently failing over from live to backup when the live server is crashed.</p> - <p>JBoss Messaging implements seamless, transparent failover of client connections between live and backup servers. + <p>HornetQ implements seamless, transparent failover of client connections between live and backup servers. This is implemented by the replication of state between live and backup nodes. When replication is configured and a live node crashes, the client connections can carry on as if <i>nothing happened</i> and carry on sending and consuming messages.</p> - <p><b>With JBoss Messaging there is no need to code any special client side failover logic in order to benefit from + <p><b>With HornetQ there is no need to code any special client side failover logic in order to benefit from failover and HA. There is no need to refactor your messaging applications to work in an HA environment.</b></p> - <p>JBoss Messaging also supports manual failover which is covered in a separate example.</p> - <p>For more information on JBoss Messaging failover and HA, and clustering in general, please see the clustering + <p>HornetQ also supports manual failover which is covered in a separate example.</p> + <p>For more information on HornetQ failover and HA, and clustering in general, please see the clustering section of the user manual.</p> <h2>Example step-by-step</h2> <p><i>To run the example, simply type <code>ant</code> from this directory</i></p> Modified: trunk/examples/jms/bridge/build.xml =================================================================== --- trunk/examples/jms/bridge/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/bridge/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -15,7 +15,7 @@ ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging JMS Clustered Queue Example"> +<project default="run" name="HornetQ JMS Clustered Queue Example"> <import file="../../common/build.xml"/> Modified: trunk/examples/jms/bridge/readme.html =================================================================== --- trunk/examples/jms/bridge/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/bridge/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,16 +1,16 @@ <html> <head> - <title>JBoss Messaging Core Bridge Example</title> + <title>HornetQ Core Bridge Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> - <h1>JBoss Messaging Core Bridge Example</h1> + <h1>HornetQ Core Bridge Example</h1> <br> <p>This example demonstrates a core bridge deployed on one server, which consumes messages from a local queue and forwards them to an address on a second server.</p> - <p>Core bridges are used to create message flows between any two JBoss Messaging servers which are remotely separated. + <p>Core bridges are used to create message flows between any two HornetQ servers which are remotely separated. Core bridges are resilient and will cope with temporary connection failure allowing them to be an ideal choice for forwarding over unreliable connections, e.g. a WAN.</p> <p>They can also be configured with an optional filter expression, and will only forward messages that @@ -18,11 +18,11 @@ <p>Furthermore they can be configured to use an optional Transformer class. A user defined Transformer class can be specified which is called at forwarding time. This gives the user the opportunity to transform the message in some way, e.g. changing it's properties or body</p> - <p>JBoss Messaging also includes a <b>JMS Bridge</b>. This is similar in some ways to a core bridge, but uses the JMS API + <p>HornetQ also includes a <b>JMS Bridge</b>. This is similar in some ways to a core bridge, but uses the JMS API and can be used to bridge between any two JMS 1.1 compliant messaging systems. The core bridge is limited to bridging - between JBoss Messaging instances, but may provide better performance than the JMS bridge. The JMS bridge is covered in + between HornetQ instances, but may provide better performance than the JMS bridge. The JMS bridge is covered in a separate example.</p> - <p>For more information on bridges, please see the JBoss Messaging user manual.</p> + <p>For more information on bridges, please see the HornetQ user manual.</p> <br> <p>In this example we will demonstrate a simple sausage factory for aardvarks.</p> <p>We have a JMS queue on server 0 named <code>sausage-factory</code>, and we have a Modified: trunk/examples/jms/browser/build.xml =================================================================== --- trunk/examples/jms/browser/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/browser/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -14,7 +14,7 @@ ~ implied. See the License for the specific language governing ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging JMS QueueBrowser Example"> +<project default="run" name="HornetQ JMS QueueBrowser Example"> <import file="../../common/build.xml"/> Modified: trunk/examples/jms/browser/readme.html =================================================================== --- trunk/examples/jms/browser/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/browser/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,12 +1,12 @@ <html> <head> - <title>JBoss Messaging JMS QueueBrowser Example</title> + <title>HornetQ JMS QueueBrowser Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> <h1>JMS Queue Example</h1> <br> - <p>This example shows you how to use a JMS <a href="http://java.sun.com/javaee/5/docs/api/javax/jms/QueueBrowser.html">QueueBrowser</a> with JBoss Messaging.<br /> + <p>This example shows you how to use a JMS <a href="http://java.sun.com/javaee/5/docs/api/javax/jms/QueueBrowser.html">QueueBrowser</a> with HornetQ.<br /> Queues are a standard part of JMS, please consult the JMS 1.1 specification for full details.<br /> A QueueBrowser is used to look at messages on the queue without removing them. It can scan the entire content of a queue or only messages matching a message selector.</p> Modified: trunk/examples/jms/client-kickoff/build.xml =================================================================== --- trunk/examples/jms/client-kickoff/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/client-kickoff/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -14,7 +14,7 @@ ~ implied. See the License for the specific language governing ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging Client Kickoff Example"> +<project default="run" name="HornetQ Client Kickoff Example"> <import file="../../common/build.xml"/> <property file="ant.properties"/> Modified: trunk/examples/jms/client-kickoff/readme.html =================================================================== --- trunk/examples/jms/client-kickoff/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/client-kickoff/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,21 +1,21 @@ <html> <head> - <title>JBoss Messaging Client Kickoff Example</title> + <title>HornetQ Client Kickoff Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> <h1>Client Kickoff Example</h1> - <p>This example shows how to kick off a client connected to JBoss Messaging + <p>This example shows how to kick off a client connected to HornetQ using <a href="http://java.sun.com/javase/technologies/core/mntr-mgmt/javamanagement/">JMX</a></p> - <p>The example will connect to JBoss Messaging. Using JMX, we will list the remote addresses connected to the - server and close the corresponding connections. The client will be kicked off from JBoss Messaging and receives + <p>The example will connect to HornetQ. Using JMX, we will list the remote addresses connected to the + server and close the corresponding connections. The client will be kicked off from HornetQ and receives an exception that its JMS connection was interrupted.</p> <h2>Example configuration</h2> - <p>JBoss Messaging exposes its managed resources by default on the platform MBeanServer.</p> + <p>HornetQ exposes its managed resources by default on the platform MBeanServer.</p> <p>To access this MBeanServer remotely, the Java Virtual machine must be started with system properties: <pre> <code>-Dcom.sun.management.jmxremote @@ -25,7 +25,7 @@ </pre> <p>These properties are explained in the Java 5 <a href="http://java.sun.com/j2se/1.5.0/docs/guide/management/agent.html#remote">Management guide</a> (please note that for this example, we will disable user authentication for simplicity sake).</p> - <p>With these properties, JBoss Messaging server will be manageable remotely using standard JMX URL on port <code>3000</code>.</p> + <p>With these properties, HornetQ server will be manageable remotely using standard JMX URL on port <code>3000</code>.</p> </p> <h2>Example step-by-step</h2> @@ -63,7 +63,7 @@ <code>connection.start();</code> </pre> - <li>We create a MBean proxy to the MessagingServerControlMBean used to manage JBoss Messaging server + <li>We create a MBean proxy to the MessagingServerControlMBean used to manage HornetQ server (see <a href="../jmx/readme.html">JMX example</a> for a complete explanation of the different steps)</li> <pre> <code>ObjectName on = ObjectNames.getMessagingServerObjectName(); @@ -130,10 +130,10 @@ <ul> <li><a href="http://java.sun.com/j2se/1.5.0/docs/guide/management/agent.html">Java 5 Management guide</a></li> - <li>JBoss Messaging defines a set of MBeans for this core + <li>HornetQ defines a set of MBeans for this core API (<a href="../../../docs/api/org/jboss/messaging/core/management/package-summary.html">org.hornetq.core.management</a> package) and its JMS API (in the <a href="../../../docs/api/org/jboss/messaging/jms/server/management/package-summary.html">org.hornetq.jms.server.management</a> package) - <li><a href="../../../docs/api/org/jboss/messaging/core/management/ObjectNames.html">ObjectNames</a> is a helper class used to build the ObjectName of JBoss Messaging manageable resources</li> + <li><a href="../../../docs/api/org/jboss/messaging/core/management/ObjectNames.html">ObjectNames</a> is a helper class used to build the ObjectName of HornetQ manageable resources</li> </ul> </body> </html> \ No newline at end of file Modified: trunk/examples/jms/client-kickoff/server0/hornetq-configuration.xml =================================================================== --- trunk/examples/jms/client-kickoff/server0/hornetq-configuration.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/client-kickoff/server0/hornetq-configuration.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,7 +1,7 @@ <configuration xmlns="urn:hornetq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:hornetq /schema/hornetq-configuration.xsd"> -  +  <jmx-management-enabled>true</jmx-management-enabled>  Modified: trunk/examples/jms/client-kickoff/src/org/hornetq/jms/example/ClientKickoffExample.java =================================================================== --- trunk/examples/jms/client-kickoff/src/org/hornetq/jms/example/ClientKickoffExample.java 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/client-kickoff/src/org/hornetq/jms/example/ClientKickoffExample.java 2009-08-20 15:17:39 UTC (rev 7830) @@ -31,7 +31,7 @@ import java.util.concurrent.atomic.AtomicReference; /** - * An example that shows how to kick off a client connected to JBoss Messagingby using JMX. + * An example that shows how to kick off a client connected to HornetQby using JMX. * * @author <a href="mailto:jmesnil@redhat.com">Jeff Mesnil</a> */ Modified: trunk/examples/jms/client-side-load-balancing/build.xml =================================================================== --- trunk/examples/jms/client-side-load-balancing/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/client-side-load-balancing/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -15,7 +15,7 @@ ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging JMS Client Side Load Balancing Example"> +<project default="run" name="HornetQ JMS Client Side Load Balancing Example"> <import file="../../common/build.xml"/> Modified: trunk/examples/jms/client-side-load-balancing/readme.html =================================================================== --- trunk/examples/jms/client-side-load-balancing/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/client-side-load-balancing/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,18 +1,18 @@ <html> <head> - <title>JBoss Messaging JMS Client Side Load-Balancing Example</title> + <title>HornetQ JMS Client Side Load-Balancing Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> - <h1>JBoss Messaging JMS Client Side Load-Balancing Example</h1> + <h1>HornetQ JMS Client Side Load-Balancing Example</h1> <br> <p>This example demonstrates how subsequent connections created from a JMS Connection Factory can be created - to different nodes of the cluster. In other words it demonstrates how JBoss Messaging does <b>client side load balancing</b> of + to different nodes of the cluster. In other words it demonstrates how HornetQ does <b>client side load balancing</b> of connections across the cluster.</p> <p>The particular load-balancing policy can be chosen to be random, round-robin or user-defined. Please see the user guide for more details of how to configure the specific load-balancing policy. In this example we will use the default round-robin load balancing policy.</p> - <p>The list of servers over which JBoss Messaging will round-robin the connections can either be specified explicitly + <p>The list of servers over which HornetQ will round-robin the connections can either be specified explicitly in the connection factory when creating it, or deploying it on the server, or the factory can be configured to use UDP discovery to discover the list of servers over which to round-robin. This example will use UDP discovery to obtain the list.</p> @@ -20,7 +20,7 @@ can be seen in the <code>hornetq-configuration.xml</code> file.</p> <p>A JMS ConnectionFactory is deployed on each server specifying the discovery group that will be used by that connection factory.</p> - <p>For more information on JBoss Messaging load balancing, and clustering in general, please see the clustering + <p>For more information on HornetQ load balancing, and clustering in general, please see the clustering section of the user manual.</p> <h2>Example step-by-step</h2> <p><i>To run the example, simply type <code>ant</code> from this directory</i></p> Modified: trunk/examples/jms/clustered-durable-subscription/build.xml =================================================================== --- trunk/examples/jms/clustered-durable-subscription/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/clustered-durable-subscription/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -15,7 +15,7 @@ ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging JMS Clustered Durable Subscription Example"> +<project default="run" name="HornetQ JMS Clustered Durable Subscription Example"> <import file="../../common/build.xml"/> Modified: trunk/examples/jms/clustered-durable-subscription/readme.html =================================================================== --- trunk/examples/jms/clustered-durable-subscription/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/clustered-durable-subscription/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,10 +1,10 @@ <html> <head> - <title>JBoss Messaging JMS Durable Subscription Example</title> + <title>HornetQ JMS Durable Subscription Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> - <h1>JBoss Messaging JMS Durable Subscription Example</h1> + <h1>HornetQ JMS Durable Subscription Example</h1> <br> <p>This example demonstrates a clustered JMS durable subscription. Normally durable subscriptions exist on a single node and can only have one subscriber at any one time, @@ -35,7 +35,7 @@ </cluster-connection> </code> </pre> - <p>For more information on JBoss Messaging load balancing, and clustering in general, please see the clustering + <p>For more information on HornetQ load balancing, and clustering in general, please see the clustering section of the user manual.</p> <h2>Example step-by-step</h2> <p><i>To run the example, simply type <code>ant</code> from this directory</i></p> Modified: trunk/examples/jms/clustered-queue/build.xml =================================================================== --- trunk/examples/jms/clustered-queue/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/clustered-queue/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -14,7 +14,7 @@ ~ implied. See the License for the specific language governing ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging JMS Clustered Queue Example"> +<project default="run" name="HornetQ JMS Clustered Queue Example"> <import file="../../common/build.xml"/> Modified: trunk/examples/jms/clustered-queue/readme.html =================================================================== --- trunk/examples/jms/clustered-queue/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/clustered-queue/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,16 +1,16 @@ <html> <head> - <title>JBoss Messaging JMS Load Balanced Queue Example</title> + <title>HornetQ JMS Load Balanced Queue Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> - <h1>JBoss Messaging JMS Load Balanced Clustered Queue Example</h1> + <h1>HornetQ JMS Load Balanced Clustered Queue Example</h1> <br> <p>This example demonstrates a JMS queue deployed on two different nodes. The two nodes are configured to form a cluster.</p> <p>We then create a consumer on the queue on each node, and we create a producer on only one of the nodes.</p> <p>We then send some messages via the producer, and we verify that <b>both</b> consumers receive the sent messages in a round-robin fashion.</p> - <p>In other words, JBoss Messaging <b>load balances</b> the sent messages across all consumers on the cluster</p> + <p>In other words, HornetQ <b>load balances</b> the sent messages across all consumers on the cluster</p> <p>This example uses JNDI to lookup the JMS Queue and ConnectionFactory objects. If you prefer not to use JNDI, these could be instantiated directly.</p> <p>Here's the relevant snippet from the server configuration, which tells the server to form a cluster between the two nodes @@ -26,7 +26,7 @@ </cluster-connection> </code> </pre> - <p>For more information on JBoss Messaging load balancing, and clustering in general, please see the clustering + <p>For more information on HornetQ load balancing, and clustering in general, please see the clustering section of the user manual.</p> <h2>Example step-by-step</h2> <p><i>To run the example, simply type <code>ant</code> from this directory</i></p> @@ -130,8 +130,8 @@ <li>We now consume those messages on *both* server 0 and server 1. We note the messages have been distributed between servers in a round robin fashion. - JBoss Messaging has <b>load balanced</b> the messages between the available consumers on the different nodes. - JBoss Messaging can be configured to always load balance messages to all nodes, or to only balance messages + HornetQ has <b>load balanced</b> the messages between the available consumers on the different nodes. + HornetQ can be configured to always load balance messages to all nodes, or to only balance messages to nodes which have consumers with no or matching selectors. See the user manual for more details.</li> JMS Queues implement point-to-point message where each message is only ever consumed by a maximum of one consumer. Modified: trunk/examples/jms/clustered-standalone/build.xml =================================================================== --- trunk/examples/jms/clustered-standalone/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/clustered-standalone/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -15,7 +15,7 @@ ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging Clustered Standalone Example"> +<project default="run" name="HornetQ Clustered Standalone Example"> <import file="../../common/build.xml"/> Modified: trunk/examples/jms/clustered-standalone/readme.html =================================================================== --- trunk/examples/jms/clustered-standalone/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/clustered-standalone/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -11,7 +11,7 @@ <p>Subscriber for the topic are created on each node, and a producer is created on only one of the nodes.</p> <p>Some messages are sent by the producer, and we verify that <strong>all</strong> subscribers receive all the sent messages.</p> - <p>This example uses JBoss Messaging's default stand-alone clustered configuration. + <p>This example uses HornetQ's default stand-alone clustered configuration. The relevant snippet from the server configuration, which tells the servers to form a cluster between the three nodes and to load balance the messages between the nodes is:</p> <pre> Modified: trunk/examples/jms/clustered-topic/build.xml =================================================================== --- trunk/examples/jms/clustered-topic/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/clustered-topic/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -15,7 +15,7 @@ ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging JMS Clustered Topic Example"> +<project default="run" name="HornetQ JMS Clustered Topic Example"> <import file="../../common/build.xml"/> Modified: trunk/examples/jms/clustered-topic/readme.html =================================================================== --- trunk/examples/jms/clustered-topic/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/clustered-topic/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,10 +1,10 @@ <html> <head> - <title>JBoss Messaging JMS Clustered Topic Example</title> + <title>HornetQ JMS Clustered Topic Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> - <h1>JBoss Messaging JMS Clustered Topic Example</h1> + <h1>HornetQ JMS Clustered Topic Example</h1> <br> <p>This example demonstrates a JMS Topic deployed on two different nodes. The two nodes are configured to form a cluster.</p> <p>We then create a subscriber on the topic on each node, and we create a producer on only one of the nodes.</p> @@ -27,7 +27,7 @@ </cluster-connection> </code> </pre> - <p>For more information on JBoss Messaging load balancing, and clustering in general, please see the clustering + <p>For more information on HornetQ load balancing, and clustering in general, please see the clustering section of the user manual.</p> <h2>Example step-by-step</h2> <p><i>To run the example, simply type <code>ant</code> from this directory</i></p> Modified: trunk/examples/jms/consumer-rate-limit/build.xml =================================================================== --- trunk/examples/jms/consumer-rate-limit/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/consumer-rate-limit/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -15,7 +15,7 @@ ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging JMS Consumer Rate Limit Example"> +<project default="run" name="HornetQ JMS Consumer Rate Limit Example"> <import file="../../common/build.xml"/> Modified: trunk/examples/jms/consumer-rate-limit/readme.html =================================================================== --- trunk/examples/jms/consumer-rate-limit/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/consumer-rate-limit/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,14 +1,14 @@ <html> <head> - <title>JBoss Messaging JMS Message Consumer Rate Limiting</title> + <title>HornetQ JMS Message Consumer Rate Limiting</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> - <h1>JBoss Messaging <br>JMS Message Consumer Rate Limiting</h1> + <h1>HornetQ <br>JMS Message Consumer Rate Limiting</h1> <br><br> - <p>With JBoss Messaging you can specify a maximum consume rate at which a JMS MessageConsumer will consume messages. + <p>With HornetQ you can specify a maximum consume rate at which a JMS MessageConsumer will consume messages. This can be specified when creating or deploying the connection factory. See <code>hornetq-jms.xml</code></p> - <p>If this value is specified then JBoss Messaging will ensure that messages are never consumed at a rate higher than + <p>If this value is specified then HornetQ will ensure that messages are never consumed at a rate higher than the specified rate. This is a form of consumer <i>throttling</i>.</p> <h2>Example step-by-step</h2> <p>In this example we specify a <code>consumer-max-rate</code> of <code>10</code> messages per second in the <code>hornetq-jms.xml</code> Modified: trunk/examples/jms/dead-letter/build.xml =================================================================== --- trunk/examples/jms/dead-letter/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/dead-letter/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -15,7 +15,7 @@ ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging Dead Letter Example"> +<project default="run" name="HornetQ Dead Letter Example"> <import file="../../common/build.xml"/> Modified: trunk/examples/jms/dead-letter/readme.html =================================================================== --- trunk/examples/jms/dead-letter/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/dead-letter/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,6 +1,6 @@ <html> <head> - <title>JBoss Messaging Dead Letter Example</title> + <title>HornetQ Dead Letter Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> @@ -13,7 +13,7 @@ <p>To prevent this, messaging systems define dead letter messages: after a specified unsuccessful delivery attempts, the message is removed from the destination and put instead in a <em>dead letter destination</em> where they can be consumed for further investigation. <p> - The example will show how to configure JBoss Messaging to send a message to a dead letter destination after 3 unsuccessful delivery attempts.<br /> + The example will show how to configure HornetQ to send a message to a dead letter destination after 3 unsuccessful delivery attempts.<br /> The example will send 1 message to a queue. We will deliver the message 3 times and rollback the session every time.<br /> On the 4th attempt, there won't be any message to consume: it will have been moved to a <em>dead letter queue</em>.<br /> We will then consume the message from this dead letter queue. @@ -28,7 +28,7 @@ </code> </pre> <p>This configuration will moved dead letter messages from <code>exampleQueue</code> to the <code>deadLetterQueue</code>.</p> - <p>JBoss Messaging allows to specify either a <code>Queue</code> by prefixing the <code>dead-letter-address</code> with <code>jms.queue.</code> + <p>HornetQ allows to specify either a <code>Queue</code> by prefixing the <code>dead-letter-address</code> with <code>jms.queue.</code> or a <code>Topic</code> by prefixing with <code>jms.topic.</code>.<br /> In this example, we will use a <code>Queue</code> to hold the dead letter messages.</p> <p>The maximum attempts of delivery is <code>3</code>. Once this figure is reached, a message is considered a dead letter message and is moved to @@ -135,7 +135,7 @@ System.out.println("4th delivery from " + queue.getQueueName() + ": " + messageReceived);</code> </pre> - <p>We have configured JBoss Messaging to send any dead letter messages to the <code>deadLetterQueue</code>. + <p>We have configured HornetQ to send any dead letter messages to the <code>deadLetterQueue</code>. We will now consume messages from this queue and receives the <em>dead letter messages</em>.</p> <li>We look up the JMS <em>dead letter queue</em> object from JNDI</li> @@ -161,7 +161,7 @@ <p>JMS does not specify the notion of dead letter destinations and messages. From JMS point of view, the message received from the dead letter queue is a <strong>different</strong> message than the message removed from the queue after the unsuccessful delivery attempts: the messages have the same content (properties and body) but their JMS headers differ.<br /> - JBoss Messaging defines additional properties for messages received from a dead letter destination</p> + HornetQ defines additional properties for messages received from a dead letter destination</p> <li>The message's destination is the dead letter queue</li> <pre> Modified: trunk/examples/jms/dead-letter/src/org/hornetq/jms/example/DeadLetterExample.java =================================================================== --- trunk/examples/jms/dead-letter/src/org/hornetq/jms/example/DeadLetterExample.java 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/dead-letter/src/org/hornetq/jms/example/DeadLetterExample.java 2009-08-20 15:17:39 UTC (rev 7830) @@ -116,7 +116,7 @@ // The message received from the dead letter queue has the same content than the undelivered message but its JMS headers // differ (from JMS point of view, it's not the same message). - // JBoss Messaging defines additional properties for messages received from the dead letter queue + // HornetQ defines additional properties for messages received from the dead letter queue System.out.println(); // Step 21. the messageReceived's destination is now the dead letter queue. Modified: trunk/examples/jms/delayed-redelivery/build.xml =================================================================== --- trunk/examples/jms/delayed-redelivery/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/delayed-redelivery/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -15,7 +15,7 @@ ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging Delayed Redelivery Example"> +<project default="run" name="HornetQ Delayed Redelivery Example"> <import file="../../common/build.xml"/> Modified: trunk/examples/jms/delayed-redelivery/readme.html =================================================================== --- trunk/examples/jms/delayed-redelivery/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/delayed-redelivery/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,12 +1,12 @@ <html> <head> - <title>JBoss Messaging Delayed Redelivery Example</title> + <title>HornetQ Delayed Redelivery Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> - <h1>JBoss Messaging Delayed Redelivery Example</h1> + <h1>HornetQ Delayed Redelivery Example</h1> - <p>This example demonstrates how JBoss Messaging can be configured to provide a delayed redelivery in the case + <p>This example demonstrates how HornetQ can be configured to provide a delayed redelivery in the case a message needs to be redelivered.</p> <p>Delaying redelivery can often be useful in the case that clients regularly fail or roll-back. Without a delayed redelivery, the system can get into a "thrashing" state, with delivery being attempted, the client rolling back, and Modified: trunk/examples/jms/delayed-redelivery/src/org/hornetq/jms/example/DelayedRedeliveryExample.java =================================================================== --- trunk/examples/jms/delayed-redelivery/src/org/hornetq/jms/example/DelayedRedeliveryExample.java 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/delayed-redelivery/src/org/hornetq/jms/example/DelayedRedeliveryExample.java 2009-08-20 15:17:39 UTC (rev 7830) @@ -24,7 +24,7 @@ import org.hornetq.common.example.HornetQExample; /** - * This example demonstrates how JBoss Messaging can be configured with a redelivery delay in the event a message + * This example demonstrates how HornetQ can be configured with a redelivery delay in the event a message * is redelivered. * * Please see the readme.html for more information Modified: trunk/examples/jms/divert/build.xml =================================================================== --- trunk/examples/jms/divert/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/divert/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -14,7 +14,7 @@ ~ implied. See the License for the specific language governing ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging JMS Divert Example"> +<project default="run" name="HornetQ JMS Divert Example"> <import file="../../common/build.xml"/> Modified: trunk/examples/jms/divert/readme.html =================================================================== --- trunk/examples/jms/divert/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/divert/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,11 +1,11 @@ <html> <head> - <title>JBoss Messaging Divert Example</title> + <title>HornetQ Divert Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> <body> - <h1>JBoss Messaging Divert Example</h1> + <h1>HornetQ Divert Example</h1> <br> - <p>JBoss Messaging diverts allow messages to be transparently "diverted" from one address to another + <p>HornetQ diverts allow messages to be transparently "diverted" from one address to another with just some simple configuration defined on the server side.</p> <p>Diverts can be defined to be <b>exclusive</b> or <b>non-exclusive</b>.</p> <p>With an <b>exclusive</b> divert the message is intercepted and does not get sent to the queues originally Modified: trunk/examples/jms/divert/src/org/hornetq/jms/example/DivertExample.java =================================================================== --- trunk/examples/jms/divert/src/org/hornetq/jms/example/DivertExample.java 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/divert/src/org/hornetq/jms/example/DivertExample.java 2009-08-20 15:17:39 UTC (rev 7830) @@ -26,7 +26,7 @@ import org.hornetq.common.example.HornetQExample; /** - * This examples demonstrates the use of JBoss Messaging "Diverts" to transparently divert or copy messages + * This examples demonstrates the use of HornetQ "Diverts" to transparently divert or copy messages * from one address to another. * * Please see the readme.html for more information. Modified: trunk/examples/jms/durable-subscription/build.xml =================================================================== --- trunk/examples/jms/durable-subscription/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/durable-subscription/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -15,7 +15,7 @@ ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging JMS Durable Subscription Example"> +<project default="run" name="HornetQ JMS Durable Subscription Example"> <import file="../../common/build.xml"/> Modified: trunk/examples/jms/durable-subscription/readme.html =================================================================== --- trunk/examples/jms/durable-subscription/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/durable-subscription/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,12 +1,12 @@ <html> <head> - <title>JBoss Messaging JMS Durable Subscription Example</title> + <title>HornetQ JMS Durable Subscription Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> <h1>JMS Durable Subscription Example</h1> <br> - <p>This example shows you how to use a durable subscription with JBoss Messaging.</p> + <p>This example shows you how to use a durable subscription with HornetQ.</p> <p>Durable subscriptions are a standard part of JMS, please consult the JMS 1.1 specification for full details.</p> <p>Unlike non durable subscriptions, the key function of durable subscriptions is that the messages contained in them persist longer than the lifetime of the subscriber - i.e. they will accumulate messages sent to the topic even if there is no active subscriber on them. They will also survive server restarts. Note that for the messages to be persisted, the messages sent to them must be marked as persistent messages.</p> <br> Modified: trunk/examples/jms/embedded/build.xml =================================================================== --- trunk/examples/jms/embedded/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/embedded/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -15,7 +15,7 @@ ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging Embedded Example"> +<project default="run" name="HornetQ Embedded Example"> <import file="../../common/build.xml"/> Modified: trunk/examples/jms/embedded/readme.html =================================================================== --- trunk/examples/jms/embedded/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/embedded/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,16 +1,16 @@ <html> <head> - <title>JBoss Messaging Embedded Example</title> + <title>HornetQ Embedded Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> <h1>Embedded Example</h1> <br> - <p>This examples shows how to setup and run JBoss Messaging embedded.</p> - <p>JBoss Messaging was designed to use POJOs (Plain Old Java Objects), what makes embedding JBoss Messaging as simple as instantiating a few objects.</p> + <p>This examples shows how to setup and run HornetQ embedded.</p> + <p>HornetQ was designed to use POJOs (Plain Old Java Objects), what makes embedding HornetQ as simple as instantiating a few objects.</p> <p>On this example, we only one jars (hornetq-core.jar, hornetq-jms.jar and jboss-javaee.jar).</p> - <p>JBoss Messaging Embedded could be used from very simple use cases with only InVM support to very complex cases with clustering, persistence and fail over.</p> + <p>HornetQ Embedded could be used from very simple use cases with only InVM support to very complex cases with clustering, persistence and fail over.</p> <br> <h2>Example step-by-step</h2> <p><i>To run the example, simply type <code>ant</code> from this directory</i></p> Modified: trunk/examples/jms/embedded/src/org/hornetq/jms/example/EmbeddedExample.java =================================================================== --- trunk/examples/jms/embedded/src/org/hornetq/jms/example/EmbeddedExample.java 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/embedded/src/org/hornetq/jms/example/EmbeddedExample.java 2009-08-20 15:17:39 UTC (rev 7830) @@ -33,7 +33,7 @@ import org.hornetq.jms.client.HornetQConnectionFactory; /** - * This example demonstrates how to run a JBoss Messaging embedded with JMS + * This example demonstrates how to run a HornetQ embedded with JMS * * @author <a href="clebert.suconic(a)jboss.com">Clebert Suconic</a> */ Modified: trunk/examples/jms/expiry/build.xml =================================================================== --- trunk/examples/jms/expiry/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/expiry/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -14,7 +14,7 @@ ~ implied. See the License for the specific language governing ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging Expiry Example"> +<project default="run" name="HornetQ Expiry Example"> <import file="../../common/build.xml"/> Modified: trunk/examples/jms/expiry/readme.html =================================================================== --- trunk/examples/jms/expiry/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/expiry/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,6 +1,6 @@ <html> <head> - <title>JBoss Messaging Message Expiration Example</title> + <title>HornetQ Message Expiration Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> @@ -9,7 +9,7 @@ <p>This example shows you how to define and deal with message expiration.</p> <p>Messages can be retained in the messaging system for a limited period of time before being removed. JMS specification states that clients should not receive messages that have been expired (but it does not guarantee this will not happen).</p> - <p>JBoss Messaging can assign a <em>expiry destination</em> to a given queue so that when messages are expired, they are removed from the queue and sent + <p>HornetQ can assign a <em>expiry destination</em> to a given queue so that when messages are expired, they are removed from the queue and sent to the expiry destination. These "expired" messages can later be consumed from the expiry destination for further inspection. <p> The example will send 1 message with a short <em>time-to-live</em> to a queue. We will wait for the message to expire and checks that the message @@ -25,7 +25,7 @@ </code> </pre> <p>This configuration will moved expired messages from the <code>exampleQueue</code> to the <code>expiryQueue</code></p> - <p>JBoss Messaging allows to specify either a <code>Queue</code> by prefixing the <code>expiry-address</code> with <code>jms.queue.</code> + <p>HornetQ allows to specify either a <code>Queue</code> by prefixing the <code>expiry-address</code> with <code>jms.queue.</code> or a <code>Topic</code> by prefixing with <code>jms.topic.</code>.<br /> In this example, we will use a <code>Queue</code> to hold the expired messages.</p> <p>Since we want to consume messages from this expiryQueue, we also need to add a JNDI binding to perform a lookup. @@ -107,7 +107,7 @@ System.out.println("Received message from " + queue.getQueueName() + ": " + messageReceived);</code> </pre> - <p>However, we have configured JBoss Messaging to send any expired messages to the <code>expiryQueue</code>. + <p>However, we have configured HornetQ to send any expired messages to the <code>expiryQueue</code>. We will now consume messages from this expiry queue and receives the <em>expired</em> message.</p> <li>We look up the JMS <em>expiry queue</em> object from JNDI</li> @@ -133,7 +133,7 @@ <p>JMS does not specify the notion of expiry queue. From JMS point of view, the message received from the expiry queue is a <strong>different</strong> message than the message expired from the queue: the two messages have the same content (properties and body) but their JMS headers differ.<br /> - JBoss Messaging defines additional properties to correlate the message received from the expiry queue with the + HornetQ defines additional properties to correlate the message received from the expiry queue with the message expired from the queue</p> <li>The expired message's destination is the expiry queue</li> Modified: trunk/examples/jms/expiry/src/org/hornetq/jms/example/ExpiryExample.java =================================================================== --- trunk/examples/jms/expiry/src/org/hornetq/jms/example/ExpiryExample.java 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/expiry/src/org/hornetq/jms/example/ExpiryExample.java 2009-08-20 15:17:39 UTC (rev 7830) @@ -99,7 +99,7 @@ // The message received from the expiry queue has the same content than the expired message but its JMS headers differ // (from JMS point of view, it's not the same message). - // JBoss Messaging defines additional properties to correlate the message received from the expiry queue with the + // HornetQ defines additional properties to correlate the message received from the expiry queue with the // message expired from the queue System.out.println(); Modified: trunk/examples/jms/http-transport/build.xml =================================================================== --- trunk/examples/jms/http-transport/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/http-transport/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -14,7 +14,7 @@ ~ implied. See the License for the specific language governing ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging JMS HTTP Transport Example"> +<project default="run" name="HornetQ JMS HTTP Transport Example"> <import file="../../common/build.xml"/> Modified: trunk/examples/jms/http-transport/readme.html =================================================================== --- trunk/examples/jms/http-transport/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/http-transport/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,16 +1,16 @@ <html> <head> - <title>JBoss Messaging JMS HTTP Transport Example</title> + <title>HornetQ JMS HTTP Transport Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> <h1>JMS HTTP Example</h1> <br> - <p>This example shows you how to configure JBoss Messaging to use HTTP protocol as its transport layer.</p> + <p>This example shows you how to configure HornetQ to use HTTP protocol as its transport layer.</p> - <p>JBoss Messaging supports a variety of network protocols to be its underlying transport without any specific code change.</p> + <p>HornetQ supports a variety of network protocols to be its underlying transport without any specific code change.</p> - <p>This example is taken from the queue example without any code change. By changing the configuration file, one can get JBoss Messaging working with HTTP transport.</p> + <p>This example is taken from the queue example without any code change. By changing the configuration file, one can get HornetQ working with HTTP transport.</p> <p>All you need to do is open the server0/hornetq-configuration.xml and enable HTTP like the following</p> Modified: trunk/examples/jms/instantiate-connection-factory/build.xml =================================================================== --- trunk/examples/jms/instantiate-connection-factory/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/instantiate-connection-factory/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -15,7 +15,7 @@ ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging Instantiate ConnectionFactory Example"> +<project default="run" name="HornetQ Instantiate ConnectionFactory Example"> <import file="../../common/build.xml"/> Modified: trunk/examples/jms/instantiate-connection-factory/readme.html =================================================================== --- trunk/examples/jms/instantiate-connection-factory/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/instantiate-connection-factory/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,16 +1,16 @@ <html> <head> - <title>JBoss Messaging JMS Instantiate Connection Factory Example</title> + <title>HornetQ JMS Instantiate Connection Factory Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> - <h1>JBoss Messaging JMS Instantiate Connection Factory Example</h1> + <h1>HornetQ JMS Instantiate Connection Factory Example</h1> <br> <p>Usually, JMS Objects such as ConnectionFactory, Queue and Topic instances are looked up from JNDI before being used by the client code. This objects are called "administered objects" in JMS specification terminology.</p> - <p>However, in some cases a JNDI server may not be available or desired. To come to the rescue JBoss Messaging + <p>However, in some cases a JNDI server may not be available or desired. To come to the rescue HornetQ also supports the direct instantiation of these administered objects on the client side.</p> <p>This allows the full set of JMS functionality to be available without requiring a JNDI server!</p> <p>This example is very simple and based on the simple Queue example, however in this example we Modified: trunk/examples/jms/interceptor/build.xml =================================================================== --- trunk/examples/jms/interceptor/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/interceptor/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -15,7 +15,7 @@ ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging Interceptor Example"> +<project default="run" name="HornetQ Interceptor Example"> <import file="../../common/build.xml"/> Modified: trunk/examples/jms/interceptor/readme.html =================================================================== --- trunk/examples/jms/interceptor/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/interceptor/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,14 +1,14 @@ <html> <head> - <title>JBoss Messaging JMS Interceptor Example</title> + <title>HornetQ JMS Interceptor Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> <h1>JMS Interceptor Example</h1> <br> - <p>This example shows you how to implement and configure a simple interceptor with JBoss Messaging.</p> + <p>This example shows you how to implement and configure a simple interceptor with HornetQ.</p> - <p>JBoss Messaging allows an application to use an interceptor to hook into the messaging system. All that needs to do is to implement the + <p>HornetQ allows an application to use an interceptor to hook into the messaging system. All that needs to do is to implement the Interceptor interface, as defined below: </p> <pre> <code> Modified: trunk/examples/jms/interceptor/src/org/hornetq/jms/example/InterceptorExample.java =================================================================== --- trunk/examples/jms/interceptor/src/org/hornetq/jms/example/InterceptorExample.java 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/interceptor/src/org/hornetq/jms/example/InterceptorExample.java 2009-08-20 15:17:39 UTC (rev 7830) @@ -24,7 +24,7 @@ import org.hornetq.common.example.HornetQExample; /** - * A simple JMS example that shows how to implement and use interceptors with JBoss Messaging. + * A simple JMS example that shows how to implement and use interceptors with HornetQ. * * @author <a href="hgao(a)redhat.com">Howard Gao</a> */ Modified: trunk/examples/jms/jaas/build.xml =================================================================== --- trunk/examples/jms/jaas/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/jaas/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -14,7 +14,7 @@ ~ implied. See the License for the specific language governing ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging JAAS Queue Example"> +<project default="run" name="HornetQ JAAS Queue Example"> <import file="../../common/build.xml"/> <path id="extra.classpath"> Modified: trunk/examples/jms/jaas/readme.html =================================================================== --- trunk/examples/jms/jaas/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/jaas/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,23 +1,23 @@ <html> <head> - <title>JBoss Messaging JAAS Example</title> + <title>HornetQ JAAS Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> <h1>JAAS Example</h1> - <p>This example shows you how to configure JBoss Messaging to use JAAS for security.</p> - <p>JBoss Messaging can leverage JAAS to delegate user authentication and authorization to existing security infrastructure.</p> + <p>This example shows you how to configure HornetQ to use JAAS for security.</p> + <p>HornetQ can leverage JAAS to delegate user authentication and authorization to existing security infrastructure.</p> <p> - The example will show how to configure JBoss Messaging with JAAS in <a href="server0/hornetq-jboss-beans.xml">hornetq-jboss-beans.xml</a>. + The example will show how to configure HornetQ with JAAS in <a href="server0/hornetq-jboss-beans.xml">hornetq-jboss-beans.xml</a>. It will use a simple <code>LoginModule</code> without any user interaction. The example will create a connection and authenticate the user with this JAAS LoginModule, send a message to a queue and receive it (see the <a href="../queue/readme.html">Queue example</a> for a complete description of the application code) </p> <h2>Example setup</h2> - <p>JBoss Messaging can use a JAAS security manager by specifying it in <a href="server0/hornetq-jboss-beans.xml">hornetq-jboss-beans.xml</a>:</p> + <p>HornetQ can use a JAAS security manager by specifying it in <a href="server0/hornetq-jboss-beans.xml">hornetq-jboss-beans.xml</a>:</p> <pre> <code>  Modified: trunk/examples/jms/jmx/build.xml =================================================================== --- trunk/examples/jms/jmx/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/jmx/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -15,7 +15,7 @@ ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging JMX Example"> +<project default="run" name="HornetQ JMX Example"> <import file="../../common/build.xml"/> <property file="ant.properties"/> Modified: trunk/examples/jms/jmx/readme.html =================================================================== --- trunk/examples/jms/jmx/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/jmx/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,16 +1,16 @@ <html> <head> - <title>JBoss Messaging JMX Management Example</title> + <title>HornetQ JMX Management Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> <h1>JMX Management Example</h1> <br> - <p>This example shows how to manage JBoss Messaging using <a href="http://java.sun.com/javase/technologies/core/mntr-mgmt/javamanagement/">JMX</a></p> + <p>This example shows how to manage HornetQ using <a href="http://java.sun.com/javase/technologies/core/mntr-mgmt/javamanagement/">JMX</a></p> <h2>Example configuration</h2> - <p>JBoss Messaging exposes its managed resources by default on the platform MBeanServer.</p> + <p>HornetQ exposes its managed resources by default on the platform MBeanServer.</p> <p>To access this MBeanServer remotely, the Java Virtual machine must be started with system properties: <pre> <code>-Dcom.sun.management.jmxremote @@ -20,7 +20,7 @@ </pre> <p>These properties are explained in the Java 5 <a href="http://java.sun.com/j2se/1.5.0/docs/guide/management/agent.html#remote">Management guide</a> (please note that for this example, we will disable user authentication for simplicity sake).</p> - <p>With these properties, JBoss Messaging server will be manageable remotely using standard JMX URL on port <code>3000</code>.</p> + <p>With these properties, HornetQ server will be manageable remotely using standard JMX URL on port <code>3000</code>.</p> </p> <h2>Example step-by-step</h2> @@ -154,10 +154,10 @@ <ul> <li>User Manual's <a href="../../../docs/user-manual/en/html_single/index.html#management.jmx">Using Management Via JMX chapter</a></li> <li><a href="http://java.sun.com/j2se/1.5.0/docs/guide/management/agent.html">Java 5 Management guide</a></li> - <li>JBoss Messaging defines a set of MBeans for this core + <li>HornetQ defines a set of MBeans for this core API (<a href="../../../docs/api/org/jboss/messaging/core/management/package-summary.html">org.hornetq.core.management</a> package) and its JMS API (in the <a href="../../../docs/api/org/jboss/messaging/jms/server/management/package-summary.html">org.hornetq.jms.server.management</a> package) - <li><a href="../../../docs/api/org/jboss/messaging/core/management/ObjectNames.html">ObjectNames</a> is a helper class used to build the ObjectName of JBoss Messaging manageable resources</li> + <li><a href="../../../docs/api/org/jboss/messaging/core/management/ObjectNames.html">ObjectNames</a> is a helper class used to build the ObjectName of HornetQ manageable resources</li> </ul> </body> </html> \ No newline at end of file Modified: trunk/examples/jms/jmx/server0/hornetq-configuration.xml =================================================================== --- trunk/examples/jms/jmx/server0/hornetq-configuration.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/jmx/server0/hornetq-configuration.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -2,7 +2,7 @@ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:hornetq /schema/hornetq-configuration.xsd"> -  +  <jmx-management-enabled>true</jmx-management-enabled>  Modified: trunk/examples/jms/jmx/src/org/hornetq/jms/example/JMXExample.java =================================================================== --- trunk/examples/jms/jmx/src/org/hornetq/jms/example/JMXExample.java 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/jmx/src/org/hornetq/jms/example/JMXExample.java 2009-08-20 15:17:39 UTC (rev 7830) @@ -34,7 +34,7 @@ import java.util.HashMap; /** - * An example that shows how to manage JBoss Messaging using JMX. + * An example that shows how to manage HornetQ using JMX. * * @author <a href="mailto:jmesnil@redhat.com">Jeff Mesnil</a> */ Modified: trunk/examples/jms/large-message/build.xml =================================================================== --- trunk/examples/jms/large-message/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/large-message/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -15,7 +15,7 @@ ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging Large Message Example"> +<project default="run" name="HornetQ Large Message Example"> <import file="../../common/build.xml"/> <property file="ant.properties"/> Modified: trunk/examples/jms/large-message/readme.html =================================================================== --- trunk/examples/jms/large-message/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/large-message/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,15 +1,15 @@ <html> <head> - <title>JBoss Messaging Large Message Example</title> + <title>HornetQ Large Message Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> <h1>Large Message Example</h1> <br> - <p>This example shows you how to send and receive very large messages with JBoss Messaging.</p> - <p>JBoss Messaging supports the sending and receiving of huge messages, much larger than can fit in available RAM + <p>This example shows you how to send and receive very large messages with HornetQ.</p> + <p>HornetQ supports the sending and receiving of huge messages, much larger than can fit in available RAM on the client or server. Effectively the only limit to message size is the amount of disk space you have on the server.</p> - <p>Large messages are persisted on the server so they can survive a server restart. In other words JBoss Messaging doesn't just + <p>Large messages are persisted on the server so they can survive a server restart. In other words HornetQ doesn't just do a simple socket stream from the sender to the consumer.</p> <p>In order to do this JBossMessaging provides an extension to JMS where you can use an InputStream or OutputStream as the source and destination for your messages. You can send messages as large as it would fit in your disk.</p> <p>You may also choose to read LargeMessages using the regular ByteStream or ByteMessage methods, but using the InputStream and OutputStream will provide you a much better performance</p> @@ -18,7 +18,7 @@ <p><i>To run the example, simply type <code>ant</code> from this directory</i></p> <p>In this example we limit both the server and the client to be running in a maximum of 50MB of RAM, and we send a message with a body of size 256MB.</p> - <p>JBoss Messaging can support much large message sizes but we + <p>HornetQ can support much large message sizes but we choose these sizes and limit RAM so the example runs more quickly.</p> <p>We create a file on disk representing the message body, create a FileInputStream on that file and set that InputStream as the body of the message before sending.</p> Modified: trunk/examples/jms/large-message/src/org/hornetq/jms/example/LargeMessageExample.java =================================================================== --- trunk/examples/jms/large-message/src/org/hornetq/jms/example/LargeMessageExample.java 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/large-message/src/org/hornetq/jms/example/LargeMessageExample.java 2009-08-20 15:17:39 UTC (rev 7830) @@ -31,7 +31,7 @@ import java.io.IOException; /** - * This example demonstrates the ability of JBoss Messaging to send and consume a very large message, much + * This example demonstrates the ability of HornetQ to send and consume a very large message, much * bigger than can fit in RAM. * * @author <a href="tim.fox(a)jboss.com">Tim Fox</a> @@ -45,7 +45,7 @@ } // The message we will send is size 256MB, even though we are only running in 50MB of RAM on both client and server. - // JBoss Messaging will support much larger message sizes, but we use 512MB so the example runs in reasonable time. + // HornetQ will support much larger message sizes, but we use 512MB so the example runs in reasonable time. private final long FILE_SIZE = 256 * 1024 * 1024; public boolean runExample() throws Exception Modified: trunk/examples/jms/last-value-queue/build.xml =================================================================== --- trunk/examples/jms/last-value-queue/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/last-value-queue/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -14,7 +14,7 @@ ~ implied. See the License for the specific language governing ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging Last-Value Queue Example"> +<project default="run" name="HornetQ Last-Value Queue Example"> <import file="../../common/build.xml"/> Modified: trunk/examples/jms/last-value-queue/readme.html =================================================================== --- trunk/examples/jms/last-value-queue/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/last-value-queue/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,6 +1,6 @@ <html> <head> - <title>JBoss Messaging Last-Value Queue Example</title> + <title>HornetQ Last-Value Queue Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> @@ -56,7 +56,7 @@ System.out.format("Sent message: %s\n", message.getText());</code> </pre> - <p><em>The <em>Last-Value</em> key is defined in JBoss Messaging's MessageImpl class. Its value is <code>"_HQ_LVQ_NAME"</code></em></p> + <p><em>The <em>Last-Value</em> key is defined in HornetQ's MessageImpl class. Its value is <code>"_HQ_LVQ_NAME"</code></em></p> <li>We will create and send a <em>second</em> text message with the Last-Value property set to <code>STOCK_NAME</code></li> <pre> Modified: trunk/examples/jms/management/build.xml =================================================================== --- trunk/examples/jms/management/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/management/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -15,7 +15,7 @@ ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging Management Example"> +<project default="run" name="HornetQ Management Example"> <import file="../../common/build.xml"/> Modified: trunk/examples/jms/management/readme.html =================================================================== --- trunk/examples/jms/management/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/management/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,16 +1,16 @@ <html> <head> - <title>JBoss Messaging Management Example</title> + <title>HornetQ Management Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> <h1> Management Example</h1> - <p>This example shows how to manage JBoss Messaging using JMS Messages to invoke management operations on the server.</a></p> - <p>To manage JBoss Messaging using JMX, see the <a href="../jmx/readme.html">JMX</a> example.</p> + <p>This example shows how to manage HornetQ using JMS Messages to invoke management operations on the server.</a></p> + <p>To manage HornetQ using JMX, see the <a href="../jmx/readme.html">JMX</a> example.</p> <h2>Example configuration</h2> - <p>JBoss Messaging can be managed by sending JMS messages with specific properties to its <em>management</em> queue.</p> + <p>HornetQ can be managed by sending JMS messages with specific properties to its <em>management</em> queue.</p> </p>By default, the management name is called <code>hornetq.management</code> but this can be configured in <a href="server0/hornetq-configuration.xml">hornetq-configuration.xml</a> <pre> <code><management-address>hornetq.management</management-address></code> @@ -90,7 +90,7 @@ <code>Message m = session.createMessage();</code> </pre> - <li>a <em>management</em> message has well-defined properties that JBoss Messaging server needs to know to perform management operations.<br /> + <li>a <em>management</em> message has well-defined properties that HornetQ server needs to know to perform management operations.<br /> We use a helper class <a href="../../../docs/api/org/jboss/messaging/jms/server/management/impl/JMSManagementHelper.html">JMSManagementHelper</a> to fill these properties: <ul> <li>The name of the resource to manage <code>jms.queue.exampleQueue</code> @@ -182,10 +182,10 @@ <ul> <li>User Manual's <a href="../../../docs/user-manual/en/html_single/index.html#management.jms">Using Management Via JMS chapter</a></li> - <li>JBoss Messaging defines a set of resources for this core + <li>HornetQ defines a set of resources for this core API (<a href="../../../docs/api/org/jboss/messaging/core/management/package-summary.html">org.hornetq.core.management</a> package) and its JMS API (in the <a href="../../../docs/api/org/jboss/messaging/jms/server/management/package-summary.html">org.hornetq.jms.server.management</a> package) - <li><a href="../../../docs/api/org/jboss/messaging/core/management/ResourceNames.html">ResourceNames</a> is a helper class used to build the name of JBoss Messaging resources by messages<br /> + <li><a href="../../../docs/api/org/jboss/messaging/core/management/ResourceNames.html">ResourceNames</a> is a helper class used to build the name of HornetQ resources by messages<br /> The convention is simple: <code>jms.queue.</code> followed by the name of the queue for a JMS queue, <code>jms.topic.</code> followed by the name of a topic for a JMS topic, etc.<br /> The name for the JMS server resource is <code>jms.server</code></li> </p> Modified: trunk/examples/jms/management/src/org/hornetq/jms/example/ManagementExample.java =================================================================== --- trunk/examples/jms/management/src/org/hornetq/jms/example/ManagementExample.java 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/management/src/org/hornetq/jms/example/ManagementExample.java 2009-08-20 15:17:39 UTC (rev 7830) @@ -29,7 +29,7 @@ import org.hornetq.jms.server.management.impl.JMSManagementHelper; /** - * An example that shows how to manage JBoss Messaging using JMS messages. + * An example that shows how to manage HornetQ using JMS messages. * * @author <a href="mailto:jmesnil@redhat.com">Jeff Mesnil</a> */ Modified: trunk/examples/jms/management-notifications/build.xml =================================================================== --- trunk/examples/jms/management-notifications/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/management-notifications/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -15,7 +15,7 @@ ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging Management Notifications Example"> +<project default="run" name="HornetQ Management Notifications Example"> <import file="../../common/build.xml"/> Modified: trunk/examples/jms/management-notifications/readme.html =================================================================== --- trunk/examples/jms/management-notifications/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/management-notifications/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,12 +1,12 @@ <html> <head> - <title>JBoss Messaging Management Notification Example</title> + <title>HornetQ Management Notification Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> <h1>Management Notification Example</h1> - <p>This example shows how to receive management notifications from JBoss Messaging using JMS Messages.</p> - <p>JBoss Messaging servers emit management notifications when events of interest occur (consumers are created or closed, + <p>This example shows how to receive management notifications from HornetQ using JMS Messages.</p> + <p>HornetQ servers emit management notifications when events of interest occur (consumers are created or closed, destinations are created or deleted, security authentication fails, etc.).<br /> These notifications can be received either by using JMX (see <a href="../jmx/readme.html">JMX example</a>) or by receiving JMS Messages from a well-known destination.</p> @@ -15,7 +15,7 @@ <h2>Example configuration</h2> - <p>JBoss Messaging can configured to send JMS messages when management notifications are emitted on the server.</p> + <p>HornetQ can configured to send JMS messages when management notifications are emitted on the server.</p> <p>By default, the management name is called <code>hornetq.notifications</code> but this can be configured in <a href="server0/hornetq-configuration.xml">hornetq-configuration.xml</a>. For this example, we will set it to <code>example.notifications</code>.</p> <pre> @@ -172,7 +172,7 @@ ------------------------ </code> </pre> - <p>The notification tells us that a user named <code>not.a.valid.user</code> failed to authenticate when creating a connection to JBoss Messaging.</p> + <p>The notification tells us that a user named <code>not.a.valid.user</code> failed to authenticate when creating a connection to HornetQ.</p> <li>And finally, <b>always</b> remember to close your JMS connections and resources after use, in a <code>finally</code> block. Closing a JMS connection will automatically close all of its sessions, consumers, producer and browser objects</li> Modified: trunk/examples/jms/message-counters/build.xml =================================================================== --- trunk/examples/jms/message-counters/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/message-counters/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -15,7 +15,7 @@ ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging Message Counter Example"> +<project default="run" name="HornetQ Message Counter Example"> <import file="../../common/build.xml"/> <property file="ant.properties"/> Modified: trunk/examples/jms/message-counters/readme.html =================================================================== --- trunk/examples/jms/message-counters/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/message-counters/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,6 +1,6 @@ <html> <head> - <title>JBoss Messaging Message Counter Example</title> + <title>HornetQ Message Counter Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> @@ -20,9 +20,9 @@ </pre> <p>By default, Message counter is not enabled (for performance reason). To enable them, set <code>message-counter-enabled</code> to <code>true</code>.<br /> Queues are sampled every 10 seconds by default. For this example we will reduce it to 2 seconds by setting <code>message-counter-sample-period</code> to <code>2000</code>.<br /> - JBoss Messaging holds in memory the message counters' history for a maximum number of days (10 by default). We can change the number of days the history is kept by setting + HornetQ holds in memory the message counters' history for a maximum number of days (10 by default). We can change the number of days the history is kept by setting the <code>message-counter-max-day-history</code> parameter.</p> - <p>The sample period and the max day history parameters have an small impact on the performance of JBoss Messaging (the resources taken to sample a queue are not available to the system's + <p>The sample period and the max day history parameters have an small impact on the performance of HornetQ (the resources taken to sample a queue are not available to the system's normal use). You should set these parameters accordingly to the use and throughput of your messages.</p> <h2>Example step-by-step</h2> @@ -66,7 +66,7 @@ <p>We now need to retrieve the message counters. They're available from the JMS Queue management resource. In this example, we will retrieve them using JMX (see the <a href="../jmx/readme.html">JMX example</a> for a more complete description). You can also use JMS message to retrieve them (see the <a href="../management/readme.html">Management example</a> to - learn about managing JBoss Messaging using JMS messages).</p> + learn about managing HornetQ using JMS messages).</p> <li>We retrieve the JMX MBean used to manage the JMS queue</li> <pre> Modified: trunk/examples/jms/message-group/build.xml =================================================================== --- trunk/examples/jms/message-group/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/message-group/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -14,7 +14,7 @@ ~ implied. See the License for the specific language governing ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging JMS Message Group Example"> +<project default="run" name="HornetQ JMS Message Group Example"> <import file="../../common/build.xml"/> Modified: trunk/examples/jms/message-group/readme.html =================================================================== --- trunk/examples/jms/message-group/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/message-group/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,12 +1,12 @@ <html> <head> - <title>JBoss Messaging Message Group Example</title> + <title>HornetQ Message Group Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> <h1>Message Group Example</h1> <br> - <p>This example shows you how to configure and use message groups with JBoss Messaging.</p> + <p>This example shows you how to configure and use message groups with HornetQ.</p> <p>Message groups are sets of messages that has the following characteristics: </p> <li>Messages in a message group share the same group id, i.e. they have same JMSXGroupID string property values.</li> @@ -18,7 +18,7 @@ where the 10 'Group-0' group messages are to be sent. You can see that with message grouping enabled, all the 10 messages will be received by the first consumer. The second consumer will receive none. </p> - <p>Alternatively, JBoss Messaging's connection factories can be configured to <em>auto group</em> messages. By setting <code>autogroup</code> to </code>true</code> on the <code>JBossConnectonFactory</code> + <p>Alternatively, HornetQ's connection factories can be configured to <em>auto group</em> messages. By setting <code>autogroup</code> to </code>true</code> on the <code>JBossConnectonFactory</code> (or setting <code><autogroup>true</autogroup></code> in <code>hornetq-jms.xml</code>'s connection factory settings), a random unique id will be picked to create a message group. <em>Every messages</em> sent by a producer created from this connection factory will automatically be part of this message group.</p> Modified: trunk/examples/jms/message-priority/build.xml =================================================================== --- trunk/examples/jms/message-priority/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/message-priority/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -15,7 +15,7 @@ ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging JMS Message Priority Example"> +<project default="run" name="HornetQ JMS Message Priority Example"> <import file="../../common/build.xml"/> Modified: trunk/examples/jms/message-priority/readme.html =================================================================== --- trunk/examples/jms/message-priority/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/message-priority/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,6 +1,6 @@ <html> <head> - <title>JBoss Messaging JMS Message Priority Example</title> + <title>HornetQ JMS Message Priority Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> Modified: trunk/examples/jms/no-consumer-buffering/build.xml =================================================================== --- trunk/examples/jms/no-consumer-buffering/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/no-consumer-buffering/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -15,7 +15,7 @@ ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging JMS No Consumer Buffering Example"> +<project default="run" name="HornetQ JMS No Consumer Buffering Example"> <import file="../../common/build.xml"/> Modified: trunk/examples/jms/no-consumer-buffering/readme.html =================================================================== --- trunk/examples/jms/no-consumer-buffering/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/no-consumer-buffering/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,18 +1,18 @@ <html> <head> - <title>JBoss Messaging No Consumer Buffering Example</title> + <title>HornetQ No Consumer Buffering Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> - <h1>JBoss Messaging <br>No Consumer Buffering Example</h1> + <h1>HornetQ <br>No Consumer Buffering Example</h1> <br><br> - <p>By default, JBoss Messaging consumers buffer messages from the server in a client side buffer + <p>By default, HornetQ consumers buffer messages from the server in a client side buffer before you actually receive them on the client side.</p> <p>This improves performance since otherwise every time you called receive() or had processed the last - message in a MessageListener onMessage() method, the JBoss Messaging client would have to go the + message in a MessageListener onMessage() 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.</p> <p>This would involve a network round trip for every message and really reduce performance.</p> - <p>Therefore, by default, JBoss Messaging pre-fetches messages into a buffer on each consumer. The total maximum size of + <p>Therefore, by default, HornetQ pre-fetches messages into a buffer on each consumer. The total maximum size of messages in bytes that will be buffered on each consumer is determined by the <code>consumer-window-size</code> parameter on the connection factory.</p> <p>In some cases it is not desirable to buffer any messages on the client side consumer.</p> @@ -22,7 +22,7 @@ to process orders which were already in the client side buffer of another consumer.</p> <p>To turn off client side buffering of messages, set <code>consumer-window-size</code> to zero.</p> - <p>With JBoss Messaging you can specify a maximum consume rate at which a JMS MessageConsumer will consume messages. + <p>With HornetQ you can specify a maximum consume rate at which a JMS MessageConsumer will consume messages. This can be specified when creating or deploying the connection factory. See <code>hornetq-jms.xml</code></p> <h2>Example step-by-step</h2> <p>In this example we specify a <code>consumer-window-size</code> of <code>0</code> bytes in the <code>hornetq-jms.xml</code> Modified: trunk/examples/jms/no-consumer-buffering/src/org/hornetq/jms/example/NoConsumerBufferingExample.java =================================================================== --- trunk/examples/jms/no-consumer-buffering/src/org/hornetq/jms/example/NoConsumerBufferingExample.java 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/no-consumer-buffering/src/org/hornetq/jms/example/NoConsumerBufferingExample.java 2009-08-20 15:17:39 UTC (rev 7830) @@ -24,7 +24,7 @@ import org.hornetq.common.example.HornetQExample; /** - * This example demonstrates how JBoss Messaging consumers can be configured to not buffer any messages from + * This example demonstrates how HornetQ consumers can be configured to not buffer any messages from * the server. * * @author <a href="tim.fox(a)jboss.com">Tim Fox</a> Modified: trunk/examples/jms/paging/build.xml =================================================================== --- trunk/examples/jms/paging/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/paging/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -14,7 +14,7 @@ ~ implied. See the License for the specific language governing ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging Paging Example"> +<project default="run" name="HornetQ Paging Example"> <import file="../../common/build.xml"/> <property file="ant.properties"/> Modified: trunk/examples/jms/paging/readme.html =================================================================== --- trunk/examples/jms/paging/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/paging/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,12 +1,12 @@ <html> <head> - <title>JBoss Messaging Paging Example</title> + <title>HornetQ Paging Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"/> </head> <body> <h1>Paging Example</h1> <br> - <p>This example shows how JBoss Messaging would avoid running out of resources by paging messages.</p> + <p>This example shows how HornetQ would avoid running out of resources by paging messages.</p> <p>A maxSize could be specified per Destination on the destinations settings (hornetq-configuration.xml).</p> <p>When the buffered messages are consuming too much memory, JBossMessaging starts writing messages on the file-system, and as the memory is released by message acknowledgement or transaction commits those messages are recovered from disk and placed in memory</p> <p>Acknowledgement plays an important factor on paging as messages will stay on the file system until the memory is released</p> Modified: trunk/examples/jms/perf/build.xml =================================================================== --- trunk/examples/jms/perf/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/perf/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -15,7 +15,7 @@ ~ permissions and limitations under the License. --> -<project name="JBoss Messaging JMS Perf Example"> +<project name="HornetQ JMS Perf Example"> <import file="../../common/build.xml"/> Modified: trunk/examples/jms/pre-acknowledge/build.xml =================================================================== --- trunk/examples/jms/pre-acknowledge/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/pre-acknowledge/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -14,7 +14,7 @@ ~ implied. See the License for the specific language governing ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging JMS Pre-acknowledge example"> +<project default="run" name="HornetQ JMS Pre-acknowledge example"> <import file="../../common/build.xml"/> Modified: trunk/examples/jms/pre-acknowledge/readme.html =================================================================== --- trunk/examples/jms/pre-acknowledge/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/pre-acknowledge/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,10 +1,10 @@ <html> <head> - <title>JBoss Messaging JMS Pre-Acknowledge Example</title> + <title>HornetQ JMS Pre-Acknowledge Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> - <h1>JBoss Messaging JMS Pre-Acknowledge Example</h1> + <h1>HornetQ JMS Pre-Acknowledge Example</h1> <br> <p>Standard JMS supports three acknowledgement modes: AUTO_ACKNOWLEDGE, CLIENT_ACKNOWLEDGE, and DUPS_OK_ACKNOWLEDGE. For a full description on these modes please consult the JMS specification, or any @@ -21,8 +21,8 @@ <p>An example of a use-case where it might be a good idea to use pre-acknowledge, is for stock price update messages. With these messages it might be ok to lose a message in event of crash, since the next price update message will arrive soon, overriding the previous price.</p> - <p>In order to use pre-acknowledge functionality with JBoss Messaging the session has to be created with - a special, JBoss Messaging specific acknowledgement mode, given by the value of + <p>In order to use pre-acknowledge functionality with HornetQ the session has to be created with + a special, HornetQ specific acknowledgement mode, given by the value of <code>JBossSession.PRE_ACKNOWLEDGE</code>. <h2>Example step-by-step</h2> <p><i>To run the example, simply type <code>ant</code> from this directory</i></p> Modified: trunk/examples/jms/pre-acknowledge/src/org/hornetq/jms/example/PreacknowledgeExample.java =================================================================== --- trunk/examples/jms/pre-acknowledge/src/org/hornetq/jms/example/PreacknowledgeExample.java 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/pre-acknowledge/src/org/hornetq/jms/example/PreacknowledgeExample.java 2009-08-20 15:17:39 UTC (rev 7830) @@ -32,7 +32,7 @@ /** * - * This example demonstrates the use of JBoss Messaging "pre-acknowledge" functionality where + * This example demonstrates the use of HornetQ "pre-acknowledge" functionality where * messages are acknowledged before they are delivered to the consumer. * * Please see the readme.html for more details. Modified: trunk/examples/jms/producer-rate-limit/build.xml =================================================================== --- trunk/examples/jms/producer-rate-limit/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/producer-rate-limit/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -15,7 +15,7 @@ ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging JMS Producer Rate Limit Example"> +<project default="run" name="HornetQ JMS Producer Rate Limit Example"> <import file="../../common/build.xml"/> Modified: trunk/examples/jms/producer-rate-limit/readme.html =================================================================== --- trunk/examples/jms/producer-rate-limit/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/producer-rate-limit/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,14 +1,14 @@ <html> <head> - <title>JBoss Messaging JMS Message Producer Rate Limiting</title> + <title>HornetQ JMS Message Producer Rate Limiting</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> - <h1>JBoss Messaging JMS Message Producer Rate Limiting</h1> + <h1>HornetQ JMS Message Producer Rate Limiting</h1> <br> - <p>With JBoss Messaging you can specify a maximum send rate at which a JMS MessageProducer will send messages. + <p>With HornetQ you can specify a maximum send rate at which a JMS MessageProducer will send messages. This can be specified when creating or deploying the connection factory. See <code>hornetq-jms.xml</code></p> - <p>If this value is specified then JBoss Messaging will ensure that messages are never produced at a rate higher than + <p>If this value is specified then HornetQ will ensure that messages are never produced at a rate higher than the specified rate. This is a form of producer <i>throttling</i>.</p> <h2>Example step-by-step</h2> <p>In this example we specify a <code>producer-max-rate</code> of <code>50</code> messages per second in the <code>hornetq-jms.xml</code> Modified: trunk/examples/jms/queue/build.xml =================================================================== --- trunk/examples/jms/queue/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/queue/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -14,7 +14,7 @@ ~ implied. See the License for the specific language governing ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging JMS Queue Example"> +<project default="run" name="HornetQ JMS Queue Example"> <import file="../../common/build.xml"/> Modified: trunk/examples/jms/queue/readme.html =================================================================== --- trunk/examples/jms/queue/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/queue/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,12 +1,12 @@ <html> <head> - <title>JBoss Messaging JMS Queue Example</title> + <title>HornetQ JMS Queue Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> <h1>JMS Queue Example</h1> <br> - <p>This example shows you how to send and receive a message to a JMS Queue with JBoss Messaging.</p> + <p>This example shows you how to send and receive a message to a JMS Queue with HornetQ.</p> <p>Queues are a standard part of JMS, please consult the JMS 1.1 specification for full details.</p> <p>A Queue is used to send messages point to point, from a producer to a consumer. The queue guarantees message ordering between these 2 points.</p> <br> Modified: trunk/examples/jms/queue-message-redistribution/build.xml =================================================================== --- trunk/examples/jms/queue-message-redistribution/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/queue-message-redistribution/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -15,7 +15,7 @@ ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging JMS Queue Message Redistribution Example"> +<project default="run" name="HornetQ JMS Queue Message Redistribution Example"> <import file="../../common/build.xml"/> Modified: trunk/examples/jms/queue-message-redistribution/readme.html =================================================================== --- trunk/examples/jms/queue-message-redistribution/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/queue-message-redistribution/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,18 +1,18 @@ <html> <head> - <title>JBoss Messaging Message Redistribution Example</title> + <title>HornetQ Message Redistribution Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> - <h1>JBoss Messaging Message Redistribution Example</h1> + <h1>HornetQ Message Redistribution Example</h1> <br> <p>This example demonstrates message redistribution between queues with the same name deployed in different nodes of a cluster.</p> <p>As demontrated in the clustered queue example, if queues with the same name are deployed on different nodes of - a cluster, JBoss Messaging can be configured to load balance messages between the nodes on the server side.</p> + a cluster, HornetQ can be configured to load balance messages between the nodes on the server side.</p> <p>However, if the consumer(s) on a particular node are closed, then messages in the queue at that node can appear to be stranded, since they have no local consumers.</p> - <p>If this is undesirable, JBoss Messaging can be configured to <b>redistribute</b> messages from the node + <p>If this is undesirable, HornetQ can be configured to <b>redistribute</b> messages from the node with no consumers, to nodes where there are consumers. If the consumers have JMS selectors set on them, then they will only be redistributed to nodes with consumers whose selectors match.</p> <p>By default, message redistribution is disabled, but can be enabled by specifying some AddressSettings configuration @@ -31,7 +31,7 @@ </address-setting> </code> </pre> - <p>For more information on JBoss Messaging load balancing, and clustering in general, please see the clustering + <p>For more information on HornetQ load balancing, and clustering in general, please see the clustering section of the user manual.</p> <h2>Example step-by-step</h2> <p><i>To run the example, simply type <code>ant</code> from this directory</i></p> @@ -135,8 +135,8 @@ <li>We now consume those messages on *both* server 0 and server 1. We note the messages have been distributed between servers in a round robin fashion. - JBoss Messaging has <b>load balanced</b> the messages between the available consumers on the different nodes. - JBoss Messaging can be configured to always load balance messages to all nodes, or to only balance messages + HornetQ has <b>load balanced</b> the messages between the available consumers on the different nodes. + HornetQ can be configured to always load balance messages to all nodes, or to only balance messages to nodes which have consumers with no or matching selectors. See the user manual for more details.</li> JMS Queues implement point-to-point message where each message is only ever consumed by a maximum of one consumer. @@ -171,7 +171,7 @@ </pre> <li>Since there is no more consumer on node 1, the messages on node 1 are now stranded (no local consumers) - so JBoss Messaging will redistribute them to node 0 so they can be consumed. We consume them from + so HornetQ will redistribute them to node 0 so they can be consumed. We consume them from node 0.</li> <pre> <code> Modified: trunk/examples/jms/queue-message-redistribution/src/org/hornetq/jms/example/QueueMessageRedistributionExample.java =================================================================== --- trunk/examples/jms/queue-message-redistribution/src/org/hornetq/jms/example/QueueMessageRedistributionExample.java 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/queue-message-redistribution/src/org/hornetq/jms/example/QueueMessageRedistributionExample.java 2009-08-20 15:17:39 UTC (rev 7830) @@ -134,7 +134,7 @@ session1.close(); // Step 17. Since there is no more consumer on node 1, the messages on node 1 are now stranded (no local consumers) - // so JBoss Messaging will redistribute them to node 0 so they can be consumed. + // so HornetQ will redistribute them to node 0 so they can be consumed. for (int i = 0; i < numMessages; i += 2) { Modified: trunk/examples/jms/queue-requestor/build.xml =================================================================== --- trunk/examples/jms/queue-requestor/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/queue-requestor/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -15,7 +15,7 @@ ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging JMS Queue Requestor Example"> +<project default="run" name="HornetQ JMS Queue Requestor Example"> <import file="../../common/build.xml"/> Modified: trunk/examples/jms/queue-requestor/readme.html =================================================================== --- trunk/examples/jms/queue-requestor/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/queue-requestor/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,12 +1,12 @@ <html> <head> - <title>JBoss Messaging JMS QueueRequestor Example</title> + <title>HornetQ JMS QueueRequestor Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> <h1>JMS QueueRequestor Example</h1> <br> - <p>This example shows you how to use a <a href="http://java.sun.com/javaee/5/docs/api/javax/jms/QueueRequestor.html">QueueRequestor</a> with JBoss Messaging.</p> + <p>This example shows you how to use a <a href="http://java.sun.com/javaee/5/docs/api/javax/jms/QueueRequestor.html">QueueRequestor</a> with HornetQ.</p> <p>JMS is mainly used to send messages asynchronously so that the producer of a message is not waiting for the result of the message consumption. However, there are cases where it is necessary to have a synchronous behavior: the code sending a message requires a reply for this message before continuing its execution.<br /> Modified: trunk/examples/jms/queue-selector/build.xml =================================================================== --- trunk/examples/jms/queue-selector/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/queue-selector/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -15,7 +15,7 @@ ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging JMS Queue Selector Example"> +<project default="run" name="HornetQ JMS Queue Selector Example"> <import file="../../common/build.xml"/> Modified: trunk/examples/jms/queue-selector/readme.html =================================================================== --- trunk/examples/jms/queue-selector/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/queue-selector/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,6 +1,6 @@ <html> <head> - <title>JBoss Messaging JMS Queue Selector Example</title> + <title>HornetQ JMS Queue Selector Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> Modified: trunk/examples/jms/reconnect-same-node/build.xml =================================================================== --- trunk/examples/jms/reconnect-same-node/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/reconnect-same-node/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -15,7 +15,7 @@ ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging Reconnect Same Node Example"> +<project default="run" name="HornetQ Reconnect Same Node Example"> <import file="../../common/build.xml"/> Modified: trunk/examples/jms/reconnect-same-node/readme.html =================================================================== --- trunk/examples/jms/reconnect-same-node/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/reconnect-same-node/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,16 +1,16 @@ <html> <head> - <title>JBoss Messaging JMS Automatic Reconnect Same Server Example</title> + <title>HornetQ JMS Automatic Reconnect Same Server Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> - <h1>JBoss Messaging JMS Reconnect Same Server Example</h1> + <h1>HornetQ JMS Reconnect Same Server Example</h1> <br> - <p>This example demonstrates how JBoss Messaging connections can be configured to be resilient to + <p>This example demonstrates how HornetQ connections can be configured to be resilient to temporary network failures.</p> <p>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 server in good time after a ping is sent, instead of - failing the connection immediately and notifying any user ExceptionListener objects, JBoss Messaging + failing the connection immediately and notifying any user ExceptionListener objects, HornetQ can be configured to automatically retry the connection, and reconnect to the server when it becomes available again across the network.</p> <p>In the case that the server didn't actually crash, i.e. the network was temporarily unavailable, the client will @@ -29,7 +29,7 @@ related attributes in the <code>hornetq-jms.xml</code> file.</p> <p>For more details on how to configure this and for clustering in general - please consult the JBoss Messaging user manual.</p> + please consult the HornetQ user manual.</p> <br> <h2>Example step-by-step</h2> Modified: trunk/examples/jms/request-reply/build.xml =================================================================== --- trunk/examples/jms/request-reply/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/request-reply/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -14,7 +14,7 @@ ~ implied. See the License for the specific language governing ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging JMS Request-Reply Example"> +<project default="run" name="HornetQ JMS Request-Reply Example"> <import file="../../common/build.xml"/> Modified: trunk/examples/jms/request-reply/readme.html =================================================================== --- trunk/examples/jms/request-reply/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/request-reply/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,6 +1,6 @@ <html> <head> - <title>JBoss Messaging JMS Request-Reply Example</title> + <title>HornetQ JMS Request-Reply Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> Modified: trunk/examples/jms/scheduled-message/build.xml =================================================================== --- trunk/examples/jms/scheduled-message/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/scheduled-message/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -15,7 +15,7 @@ ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging Scheduled Message Example"> +<project default="run" name="HornetQ Scheduled Message Example"> <import file="../../common/build.xml"/> Modified: trunk/examples/jms/scheduled-message/readme.html =================================================================== --- trunk/examples/jms/scheduled-message/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/scheduled-message/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,12 +1,12 @@ <html> <head> - <title>JBoss Messaging Scheduled Message Example</title> + <title>HornetQ Scheduled Message Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> <h1>JMS Scheduled Message Example</h1> <br> - <p>This example shows you how to send a scheduled message to a JMS Queue with JBoss Messaging.</p> + <p>This example shows you how to send a scheduled message to a JMS Queue with HornetQ.</p> <p>A Scheduled Message is a message that will be delivered at a time specified by the sender. To do this, simply set a HDR_SCHEDULED_DELIVERY_TIME header property. The value of the property should be the time of deliver in milliseconds. </p> Modified: trunk/examples/jms/security/build.xml =================================================================== --- trunk/examples/jms/security/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/security/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -15,7 +15,7 @@ ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging JMS Security Example"> +<project default="run" name="HornetQ JMS Security Example"> <import file="../../common/build.xml"/> Modified: trunk/examples/jms/security/readme.html =================================================================== --- trunk/examples/jms/security/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/security/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,21 +1,21 @@ <html> <head> - <title>JBoss Messaging JMS Security Example</title> + <title>HornetQ JMS Security Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> <h1>JMS Security Example</h1> <br> - <p>This example shows you how configure and use security with JBoss Messaging.</p> + <p>This example shows you how configure and use security with HornetQ.</p> - <p>With security properly configured, JBoss Messaging can restrict client access to its resouces, including + <p>With security properly configured, HornetQ can restrict client access to its resouces, including connection creation, message sending/receiving, etc. This is done by configuring users and roles as well as permissions in the configuration files. </p> - <p>JBoss Messaging supports wild-card in security configuration. This feature makes security configuration very much + <p>HornetQ supports wild-card in security configuration. This feature makes security configuration very much flexible and it enables fine-grained control over permissions in an efficient way.</p> - <p>For a full description of how to configure security with JBoss Messaging, please consult the user + <p>For a full description of how to configure security with HornetQ, please consult the user manual.</p> <p>This example demonstrates how to configure users/roles, how to configure topics with proper permissions using wild-card @@ -54,8 +54,8 @@ belongs to role 'europe-user', user 'frank' also belongs to 'us-user' and 'news-user', and user 'sam' also belongs to 'news-user'. </p> <p> - User name and password consists of a valid account that can be used to establish connections to a JBoss Messaging server, while - roles are used in controling the access privileges against JBoss Messaging topics and queues. You can achieve this control by + User name and password consists of a valid account that can be used to establish connections to a HornetQ server, while + roles are used in controling the access privileges against HornetQ topics and queues. You can achieve this control by configuring proper permissions in <code>hornetq-configuration.xml</code>, like in the following </p> <pre><code> @@ -105,7 +105,7 @@ <p>To illustrate the effect of permissions, three topics are deployed. Topic 'genericTopic' matches 'jms.topic.#' wild-card, topic 'news.europe.europeTopic' matches jms.topic.news.europe.#' wild-cards, and topic 'news.us.usTopic' matches 'jms.topic.news.us.#'.</p> - <p>With JBoss Messaging, the security manager is also configurable. You can use JAASSecurityManager or JBossASSecurityManager based on you need. Please + <p>With HornetQ, the security manager is also configurable. You can use JAASSecurityManager or JBossASSecurityManager based on you need. Please check out the hornetq-jboss-beans.xml for how to do. In this example we just use the basic HornetQSecurityManagerImpl which reads users/roles/passwords from the xml file <code>hornetq-users.xml</code>. Modified: trunk/examples/jms/send-acknowledgements/build.xml =================================================================== --- trunk/examples/jms/send-acknowledgements/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/send-acknowledgements/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -14,7 +14,7 @@ ~ implied. See the License for the specific language governing ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging Send Acknowledgements Example"> +<project default="run" name="HornetQ Send Acknowledgements Example"> <import file="../../common/build.xml"/> Modified: trunk/examples/jms/send-acknowledgements/readme.html =================================================================== --- trunk/examples/jms/send-acknowledgements/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/send-acknowledgements/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,12 +1,12 @@ <html> <head> - <title>JBoss Messaging Asynchronous Send Acknowledgements Example</title> + <title>HornetQ Asynchronous Send Acknowledgements Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> <h1>Asynchronous Send Acknowledgements Example</h1> <br> - <p>Asynchronous Send Acknowledgements are an advanced feature of JBoss Messaging which allow you to + <p>Asynchronous Send Acknowledgements are an advanced feature of HornetQ which allow you to receive acknowledgements that messages were successfully received at the server in a separate stream to the stream of messages being sent to the server.<p/> <p>In this example we create a normal JMS session, then set a SendAcknowledgementHandler on the JMS Modified: trunk/examples/jms/send-acknowledgements/src/org/hornetq/jms/example/SendAcknowledgementsExample.java =================================================================== --- trunk/examples/jms/send-acknowledgements/src/org/hornetq/jms/example/SendAcknowledgementsExample.java 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/send-acknowledgements/src/org/hornetq/jms/example/SendAcknowledgementsExample.java 2009-08-20 15:17:39 UTC (rev 7830) @@ -28,7 +28,7 @@ /** * - * Asynchronous Send Acknowledgements are an advanced feature of JBoss Messaging which allow you to + * Asynchronous Send Acknowledgements are an advanced feature of HornetQ which allow you to * receive acknowledgements that messages were successfully received at the server in a separate stream * to the stream of messages being sent to the server. * For more information please see the readme.html file Modified: trunk/examples/jms/ssl-enabled/build.xml =================================================================== --- trunk/examples/jms/ssl-enabled/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/ssl-enabled/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -14,7 +14,7 @@ ~ implied. See the License for the specific language governing ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging JMS SSL Example"> +<project default="run" name="HornetQ JMS SSL Example"> <import file="../../common/build.xml"/> Modified: trunk/examples/jms/ssl-enabled/readme.html =================================================================== --- trunk/examples/jms/ssl-enabled/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/ssl-enabled/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,14 +1,14 @@ <html> <head> - <title>JBoss Messaging JMS SSL Example</title> + <title>HornetQ JMS SSL Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> <h1>JMS SSL Example</h1> <br> - <p>This example shows you how to configure SSL with JBoss Messaging to send and receive message. </p> + <p>This example shows you how to configure SSL with HornetQ to send and receive message. </p> - <p>Using SSL can make your messaging applications interact with JBoss Messaging service securely. An application can + <p>Using SSL can make your messaging applications interact with HornetQ service securely. An application can be secured transparently without extra coding effort. To secure your messaging application with SSL, you need to configure connector and acceptor as follows:</p> <p> Modified: trunk/examples/jms/static-selector/build.xml =================================================================== --- trunk/examples/jms/static-selector/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/static-selector/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -15,7 +15,7 @@ ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging Static Selector Example"> +<project default="run" name="HornetQ Static Selector Example"> <import file="../../common/build.xml"/> Modified: trunk/examples/jms/static-selector/readme.html =================================================================== --- trunk/examples/jms/static-selector/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/static-selector/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,18 +1,18 @@ <html> <head> - <title>JBoss Messaging Static Message Selector Example</title> + <title>HornetQ Static Message Selector Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> <h1>Static Message Selector Example</h1> <br> - <p>This example shows you how to configure a JBoss Messaging queue with static message selectors (filters) + <p>This example shows you how to configure a HornetQ queue with static message selectors (filters) (to configure a static selector directly on a <em>JMS</em> queue, please see the <a href="../static-selector-jms/readme.html">static-selector-jms example</a>).</p> - <p>Static message selectors are JBoss Messaging's extension to message selectors as defined in JMS spec 1.1. + <p>Static message selectors are HornetQ's extension to message selectors as defined in JMS spec 1.1. Rather than specifying the selector in the application code, static message selectors are defined in one of - JBoss Messaging's configuration files, hornetq-configuration.xml, as an element called 'filter' inside each queue + HornetQ's configuration files, hornetq-configuration.xml, as an element called 'filter' inside each queue definition, like</p> <pre><code> Modified: trunk/examples/jms/static-selector-jms/build.xml =================================================================== --- trunk/examples/jms/static-selector-jms/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/static-selector-jms/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -15,7 +15,7 @@ ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging Static Selector Example jms"> +<project default="run" name="HornetQ Static Selector Example jms"> <import file="../../common/build.xml"/> Modified: trunk/examples/jms/static-selector-jms/readme.html =================================================================== --- trunk/examples/jms/static-selector-jms/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/static-selector-jms/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,6 +1,6 @@ <html> <head> - <title>JBoss Messaging Static Message Selector Example</title> + <title>HornetQ Static Message Selector Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> @@ -8,9 +8,9 @@ <br> <p>This example shows you how to configure a JMS queue with static message selectors (filters).</p> - <p>Static message selectors are JBoss Messaging's extension to message selectors as defined in JMS spec 1.1. + <p>Static message selectors are HornetQ's extension to message selectors as defined in JMS spec 1.1. Rather than specifying the selector in the application code, static message selectors are defined in one of - JBoss Messaging's configuration files, hornetq-jms.xml, as an element called 'selector' inside each JMS queue + HornetQ's configuration files, hornetq-jms.xml, as an element called 'selector' inside each JMS queue definition:</p> <pre><code> Modified: trunk/examples/jms/symmetric-cluster/build.xml =================================================================== --- trunk/examples/jms/symmetric-cluster/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/symmetric-cluster/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -14,7 +14,7 @@ ~ implied. See the License for the specific language governing ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging JMS Symmetric Cluster Example"> +<project default="run" name="HornetQ JMS Symmetric Cluster Example"> <import file="../../common/build.xml"/> <property file="ant.properties"/> Modified: trunk/examples/jms/symmetric-cluster/readme.html =================================================================== --- trunk/examples/jms/symmetric-cluster/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/symmetric-cluster/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,13 +1,13 @@ <html> <head> - <title>JBoss Messaging JMS Symmetric Cluster Example</title> + <title>HornetQ JMS Symmetric Cluster Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> - <h1>JBoss Messaging Symmetric Cluster Example</h1> + <h1>HornetQ Symmetric Cluster Example</h1> <br> - <p>This examples demonstrates a <b>symmetric cluster</b> set-up with JBoss Messaging.</p> - <p>JBoss Messaging has extremely flexible clustering which allows you to set-up servers in + <p>This examples demonstrates a <b>symmetric cluster</b> set-up with HornetQ.</p> + <p>HornetQ has extremely flexible clustering which allows you to set-up servers in many different topologies.</p> <p>The most common topology that you'll perhaps be familiar with if you are used to application server clustering is a <b>symmetric cluster</b>.</p> @@ -15,9 +15,9 @@ as every other node, and every node is connected to every other node in the cluster.</p> <p>By connecting node in such a way, we can, from a JMS point of view, give the impression of distributed JMS queues and topics.</p> - <p>The configuration used in this example is very similar to the configuration used by JBoss Messaging + <p>The configuration used in this example is very similar to the configuration used by HornetQ when installed as a clustered profile in JBoss Application Server.</p> - <p>To set up JBoss Messaging to form a symmetric cluster we simply need to mark each server as <code>clustered</code> + <p>To set up HornetQ to form a symmetric cluster we simply need to mark each server as <code>clustered</code> and we need to define a <code>cluster-connection</code> in <code>hornetq-configuration.xml</code>.</p> <p>The <code>cluster-connection</code> tells the nodes what other nodes to make connections to. With a <code>cluster-connection</code> each node that we connect to can either be specified @@ -47,7 +47,7 @@ by consumers on different nodes.</p> <p>During the example will will also kill each live server in turn, at different times, and verify that the sending consuming of messages carries on uninterrupted, as connections transparently fail over from live to backup.</p> - <p>For more information on configuring JBoss Messaging clustering in general, please see the clustering + <p>For more information on configuring HornetQ clustering in general, please see the clustering section of the user manual.</p> <h2>Example step-by-step</h2> <p><i>To run the example, simply type <code>ant</code> from this directory</i></p> Modified: trunk/examples/jms/symmetric-cluster/src/org/hornetq/jms/example/SymmetricClusterExample.java =================================================================== --- trunk/examples/jms/symmetric-cluster/src/org/hornetq/jms/example/SymmetricClusterExample.java 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/symmetric-cluster/src/org/hornetq/jms/example/SymmetricClusterExample.java 2009-08-20 15:17:39 UTC (rev 7830) @@ -33,7 +33,7 @@ * This is probably the most obvious clustering topology and the one most people will be familiar with from * using clustering in an app server, where every node has pretty much identical configuration to every other node. * - * By clustering nodes symmetrically, JBoss Messaging can give the impression of clustered queues, topics and + * By clustering nodes symmetrically, HornetQ can give the impression of clustered queues, topics and * durable subscriptions. * * In this example we send some messages to a distributed queue and topic and kill all the live servers at different Modified: trunk/examples/jms/temp-queue/build.xml =================================================================== --- trunk/examples/jms/temp-queue/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/temp-queue/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -14,7 +14,7 @@ ~ implied. See the License for the specific language governing ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging JMS Temporary Queue Example"> +<project default="run" name="HornetQ JMS Temporary Queue Example"> <import file="../../common/build.xml"/> Modified: trunk/examples/jms/temp-queue/readme.html =================================================================== --- trunk/examples/jms/temp-queue/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/temp-queue/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,12 +1,12 @@ <html> <head> - <title>JBoss Messaging JMS Temporary Queue Example</title> + <title>HornetQ JMS Temporary Queue Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> <h1>JMS Temporary Queue Example</h1> <br> - <p>This example shows you how to use a TemporaryQueue object with JBoss Messaging. First it creates a temporary queue to send and receive a message, then delete it. Then it creates another temporary queue and tries to use it after its connection is closed -- to illustrate its scope.</p> + <p>This example shows you how to use a TemporaryQueue object with HornetQ. First it creates a temporary queue to send and receive a message, then delete it. Then it creates another temporary queue and tries to use it after its connection is closed -- to illustrate its scope.</p> <p>TemporaryQueue is a JMS queue that lives within lifetime of its connection. It is often used in request-reply type messaging where the reply is sent through a temporary destination. The temporary queue is often created as a server resource, so after using, the user should call delete() method to release the resources. Please consult the JMS 1.1 specification for full details.</p> <br> <h2>Example step-by-step</h2> Modified: trunk/examples/jms/topic/build.xml =================================================================== --- trunk/examples/jms/topic/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/topic/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -16,7 +16,7 @@ --> -<project default="run" name="JBoss Messaging JMS Topic Example"> +<project default="run" name="HornetQ JMS Topic Example"> <import file="../../common/build.xml"/> Modified: trunk/examples/jms/topic/readme.html =================================================================== --- trunk/examples/jms/topic/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/topic/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,12 +1,12 @@ <html> <head> - <title>JBoss Messaging JMS Topic Example</title> + <title>HornetQ JMS Topic Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> <h1>JMS Topic Example</h1> <br> - <p>This example shows you how to send and receive a message to a JMS Topic with JBoss Messaging.</p> + <p>This example shows you how to send and receive a message to a JMS Topic with HornetQ.</p> <p>Topics are a standard part of JMS, please consult the JMS 1.1 specification for full details.</p> <p>A Topic is used to send messages using the publish-subscribe model, from a producer to 1 or more consumers.</p> <br> Modified: trunk/examples/jms/topic-hierarchies/build.xml =================================================================== --- trunk/examples/jms/topic-hierarchies/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/topic-hierarchies/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -15,7 +15,7 @@ ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging JMS Queue Example"> +<project default="run" name="HornetQ JMS Queue Example"> <import file="../../common/build.xml"/> Modified: trunk/examples/jms/topic-hierarchies/readme.html =================================================================== --- trunk/examples/jms/topic-hierarchies/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/topic-hierarchies/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,14 +1,14 @@ <html> <head> - <title>JBoss Messaging Topic Hierarchy Example</title> + <title>HornetQ Topic Hierarchy Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> - <h1>JBoss Messaging Topic Hierarchy Example</h1> + <h1>HornetQ Topic Hierarchy Example</h1> <br> - <p>JBoss Messaging supports topic hierarchies. With a topic hierarchy you can register a subscriber with a wild-card + <p>HornetQ supports topic hierarchies. With a topic hierarchy you can register a subscriber with a wild-card and that subscriber will receive any messages sent to an address that matches the wildcard.</p> - <p>JBoss Messaging wild-cards can use the character '#' which means "match any number of words", and + <p>HornetQ wild-cards can use the character '#' which means "match any number of words", and the character '*' which means "match a single word". Words are delimited by the character "."</p> <p>For example if I subscribe using the wild-card "news.europe.#", then that matches messages sent to the addresses "news.europe", "news.europe.sport" and "news.europe.entertainment", but it does not match messages sent to the Modified: trunk/examples/jms/topic-selector-example1/build.xml =================================================================== --- trunk/examples/jms/topic-selector-example1/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/topic-selector-example1/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -15,7 +15,7 @@ ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging JMS Topic Selector Example 1"> +<project default="run" name="HornetQ JMS Topic Selector Example 1"> <import file="../../common/build.xml"/> Modified: trunk/examples/jms/topic-selector-example1/readme.html =================================================================== --- trunk/examples/jms/topic-selector-example1/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/topic-selector-example1/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,12 +1,12 @@ <html> <head> - <title>JBoss Messaging JMS Topic Selector Example 1</title> + <title>HornetQ JMS Topic Selector Example 1</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> <h1>JMS Topic Selector Example 1</h1> <br> - <p>This example shows you how to send message to a JMS Topic, and subscribe them using selectors with JBoss Messaging, also creating 3 non durable subscribers. 2 subscriptions using selectors, and a third one that should receive the complete set of messages.</p> + <p>This example shows you how to send message to a JMS Topic, and subscribe them using selectors with HornetQ, also creating 3 non durable subscribers. 2 subscriptions using selectors, and a third one that should receive the complete set of messages.</p> <p>Topics and selectors are a standard part of JMS, please consult the JMS 1.1 specification for full details.</p> <p>A regular subscriber would receive every message sent to the topic, but when you use a selector you would limit the messages you receive by the logic expression you choose only getting the messages that will matter to your processing.</p> <br> Modified: trunk/examples/jms/topic-selector-example2/build.xml =================================================================== --- trunk/examples/jms/topic-selector-example2/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/topic-selector-example2/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -15,7 +15,7 @@ ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging JMS Topic Selector Example 2"> +<project default="run" name="HornetQ JMS Topic Selector Example 2"> <import file="../../common/build.xml"/> Modified: trunk/examples/jms/topic-selector-example2/readme.html =================================================================== --- trunk/examples/jms/topic-selector-example2/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/topic-selector-example2/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,6 +1,6 @@ <html> <head> - <title>JBoss Messaging JMS Topic Selector Example 2</title> + <title>HornetQ JMS Topic Selector Example 2</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> Modified: trunk/examples/jms/transactional/build.xml =================================================================== --- trunk/examples/jms/transactional/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/transactional/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -15,7 +15,7 @@ ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging JMS Transactional Example"> +<project default="run" name="HornetQ JMS Transactional Example"> <import file="../../common/build.xml"/> Modified: trunk/examples/jms/transactional/readme.html =================================================================== --- trunk/examples/jms/transactional/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/transactional/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,12 +1,12 @@ <html> <head> - <title>JBoss Messaging JMS Transactional Session Example</title> + <title>HornetQ JMS Transactional Session Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> <h1>JMS Transactional Session Example</h1> <br> - <p>This example shows you how to use a transactional Session with JBoss Messaging. It creates a transactional session. At first it sends out two messages and tries to receive without session commit. Then it commits the sending session and receives only one messages before it rolls back the receiving session. It then receives all the messages and commits the session.</p> + <p>This example shows you how to use a transactional Session with HornetQ. It creates a transactional session. At first it sends out two messages and tries to receive without session commit. Then it commits the sending session and receives only one messages before it rolls back the receiving session. It then receives all the messages and commits the session.</p> <p>Messages can be sent and received over transactional sessions. Messages in a transactional session will not be sent or acknowledged until the session is committed. It a session is rolled back, the produced messages will be destroyed and consumed messages will be recovered. Please consult the JMS 1.1 specification for full details.</p> Modified: trunk/examples/jms/xa-heuristic/build.xml =================================================================== --- trunk/examples/jms/xa-heuristic/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/xa-heuristic/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -15,7 +15,7 @@ ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging JMS XA Heuristic Example"> +<project default="run" name="HornetQ JMS XA Heuristic Example"> <import file="../../common/build.xml"/> <property file="ant.properties"/> Modified: trunk/examples/jms/xa-heuristic/readme.html =================================================================== --- trunk/examples/jms/xa-heuristic/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/xa-heuristic/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,6 +1,6 @@ <html> <head> - <title>JBoss Messaging JMS XA Heuristic Example</title> + <title>HornetQ JMS XA Heuristic Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> @@ -19,7 +19,7 @@ Then we get the MBeanServerConnection object to manipulate the prepared transactions. To illustrate, we roll back the first transaction but commit the second. This will result in that only the message 'world' is received. </p> - <p>This example uses JMX to manipulate transactions in a JBoss Messaging Server. For details on JMX facilities with JBoss + <p>This example uses JMX to manipulate transactions in a HornetQ Server. For details on JMX facilities with JBoss Messaging, please look at the JMX Example.</p> <br> Modified: trunk/examples/jms/xa-receive/build.xml =================================================================== --- trunk/examples/jms/xa-receive/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/xa-receive/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -15,7 +15,7 @@ ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging JMS XA Receive Example"> +<project default="run" name="HornetQ JMS XA Receive Example"> <import file="../../common/build.xml"/> Modified: trunk/examples/jms/xa-receive/readme.html =================================================================== --- trunk/examples/jms/xa-receive/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/xa-receive/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,16 +1,16 @@ <html> <head> - <title>JBoss Messaging JMS XA Receive Example</title> + <title>HornetQ JMS XA Receive Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> <h1>JMS XA Receive Example</h1> <br> - <p>This example shows you how message receiving behaves in an XA transaction in JBoss Messaging. In an XA + <p>This example shows you how message receiving behaves in an XA transaction in HornetQ. In an XA Transaction, only if the associated XAResource are commited, will the messages be removed from the queue. Otherwise, the messages maybe redelivered after rollback or during the XA recovery.</p> - <p>JBoss Messaging is JTA aware, meaning you can use JBoss Messaging in a XA transactional environment + <p>HornetQ is JTA aware, meaning you can use HornetQ in a XA transactional environment and participate in XA transactions. It provides the javax.transaction.xa.XAResource interface for that purpose. Users can get a XAConnectionFactory to create XAConnections and XASessions.</p> Modified: trunk/examples/jms/xa-send/build.xml =================================================================== --- trunk/examples/jms/xa-send/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/xa-send/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -15,7 +15,7 @@ ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging JMS XA Send Example"> +<project default="run" name="HornetQ JMS XA Send Example"> <import file="../../common/build.xml"/> Modified: trunk/examples/jms/xa-send/readme.html =================================================================== --- trunk/examples/jms/xa-send/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/xa-send/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,16 +1,16 @@ <html> <head> - <title>JBoss Messaging JMS XA Send Example</title> + <title>HornetQ JMS XA Send Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> <h1>JMS XA Send Example</h1> <br> - <p>This example shows you how message sending behaves in an XA transaction in JBoss Messaging. In an XA + <p>This example shows you how message sending behaves in an XA transaction in HornetQ. In an XA Transaction, only if the associated XAResource are commited, will the messages be sent to the queue. Otherwise, the messages to be sent will be discarded.</p> - <p>JBoss Messaging is JTA aware, meaning you can use JBoss Messaging in a XA transactional environment + <p>HornetQ is JTA aware, meaning you can use HornetQ in a XA transactional environment and participate in XA transactions. It provides the javax.transaction.xa.XAResource interface for that purpose. Users can get a XAConnectionFactory to create XAConnections and XASessions.</p> Modified: trunk/examples/jms/xa-with-jta/build.xml =================================================================== --- trunk/examples/jms/xa-with-jta/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/xa-with-jta/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -15,7 +15,7 @@ ~ permissions and limitations under the License. --> -<project default="run" name="JBoss Messaging JMS XA with JTA Example"> +<project default="run" name="HornetQ JMS XA with JTA Example"> <import file="../../common/build.xml"/> Modified: trunk/examples/jms/xa-with-jta/readme.html =================================================================== --- trunk/examples/jms/xa-with-jta/readme.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/xa-with-jta/readme.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -1,15 +1,15 @@ <html> <head> - <title>JBoss Messaging JMS XA with JTA Example</title> + <title>HornetQ JMS XA with JTA Example</title> <link rel="stylesheet" type="text/css" href="../../common/common.css"> </head> <body> <h1>JMS XA with JTA Example</h1> <br> - <p>This example shows you how to use JTA interfaces to control transactions with JBoss Messaging. JTA provides + <p>This example shows you how to use JTA interfaces to control transactions with HornetQ. JTA provides facilities to start and stop a transaction, enlist XA resources into a transaction.</p> - <p>JBoss Messaging is JTA aware, meaning you can use JBoss Messaging in a XA transactional environment + <p>HornetQ is JTA aware, meaning you can use HornetQ in a XA transactional environment and participate in XA transactions. It provides the javax.transaction.xa.XAResource interface for that purpose. Users can get a XAConnectionFactory to create XAConnections and XASessions.</p> Modified: trunk/examples/jms/xa-with-jta/src/org/hornetq/jms/example/XAwithJTAExample.java =================================================================== --- trunk/examples/jms/xa-with-jta/src/org/hornetq/jms/example/XAwithJTAExample.java 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/jms/xa-with-jta/src/org/hornetq/jms/example/XAwithJTAExample.java 2009-08-20 15:17:39 UTC (rev 7830) @@ -31,7 +31,7 @@ import org.hornetq.common.example.HornetQExample; /** - * A simple JMS example showing the JBoss Messaging XA support with JTA. + * A simple JMS example showing the HornetQ XA support with JTA. * * @author <a href="hgao(a)redhat.com">Howard Gao</a> */ Modified: trunk/examples/soak/normal/build.xml =================================================================== --- trunk/examples/soak/normal/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/examples/soak/normal/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -16,7 +16,7 @@ permissions and limitations under the License. --> -<project name="JBoss Messaging JMS Soak Example"> +<project name="HornetQ JMS Soak Example"> <import file="../../common/build.xml" /> Modified: trunk/src/config/jboss-as/build.xml =================================================================== --- trunk/src/config/jboss-as/build.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/src/config/jboss-as/build.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -11,18 +11,18 @@ implied. See the License for the specific language governing permissions and limitations under the License. --> -<project default="default" name="JBoss Messaging integration with JBoss AS 5"> +<project default="default" name="HornetQ integration with JBoss AS 5"> <property environment="ENV"/> <property name="jboss.home" value="${ENV.JBOSS_HOME}"/> <property name="src.bin.dir" value="../../bin"/> <property name="dest.bin.dir" value="${jboss.home}/bin"/> <property name="lib.dir" value="../../lib"/> - <target name="default" description="Create JBoss AS 5 profiles to use JBoss Messaging"> + <target name="default" description="Create JBoss AS 5 profiles to use HornetQ"> <antcall target="create-profile">  <param name="jbossas.profile.source" value="default"/> -  +  <param name="messaging.config.dir" value="./non-clustered"/>  <param name="messaging.profile.target" value="default-with-hornetq"/> @@ -30,7 +30,7 @@ <antcall target="create-profile">  <param name="jbossas.profile.source" value="all"/> -  +  <param name="messaging.config.dir" value="clustered"/>  <param name="messaging.profile.target" value="all-with-hornetq"/> Modified: trunk/src/config/ra.xml =================================================================== --- trunk/src/config/ra.xml 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/src/config/ra.xml 2009-08-20 15:17:39 UTC (rev 7830) @@ -8,8 +8,8 @@ http://java.sun.com/xml/ns/j2ee/connector_1_5.xsd" version="1.5"> - <description>JBoss Messaging 2.0 Resource Adapter</description> - <display-name>JBoss Messaging 2.0 Resource Adapter</display-name> + <description>HornetQ 2.0 Resource Adapter</description> + <display-name>HornetQ 2.0 Resource Adapter</display-name> <vendor-name>Red Hat Middleware LLC</vendor-name> <eis-type>JMS 1.1 Server</eis-type> Modified: trunk/src/main/org/hornetq/core/buffers/package.html =================================================================== --- trunk/src/main/org/hornetq/core/buffers/package.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/src/main/org/hornetq/core/buffers/package.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -12,7 +12,7 @@ </head> <body> -<h2>JBoss Messaging Buffering</h2> +<h2>HornetQ Buffering</h2> <p>This package is a stripped down version of org.jboss.netty.buffer, and we kept only what we needed for JBossMessaging buffers.</p> Modified: trunk/src/main/org/hornetq/core/filter/impl/FilterImpl.java =================================================================== --- trunk/src/main/org/hornetq/core/filter/impl/FilterImpl.java 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/src/main/org/hornetq/core/filter/impl/FilterImpl.java 2009-08-20 15:17:39 UTC (rev 7830) @@ -24,7 +24,7 @@ import org.hornetq.core.filter.impl.FilterParser; /** -* This class implements a JBoss Messaging filter +* This class implements a HornetQ filter * * @author <a href="mailto:tim.fox@jboss.com">Tim Fox</a> * @author <a href="jmesnil(a)redhat.com">Jeff Mesnil</a> Modified: trunk/src/main/org/hornetq/core/management/impl/ManagementServiceImpl.java =================================================================== --- trunk/src/main/org/hornetq/core/management/impl/ManagementServiceImpl.java 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/src/main/org/hornetq/core/management/impl/ManagementServiceImpl.java 2009-08-20 15:17:39 UTC (rev 7830) @@ -139,7 +139,7 @@ if (ConfigurationImpl.DEFAULT_MANAGEMENT_CLUSTER_USER.equals(user) && ConfigurationImpl.DEFAULT_MANAGEMENT_CLUSTER_PASSWORD.equals(password)) { log.warn("It has been detected that the cluster admin user and password which are used to " + "replicate management operation from one node to the other have not been changed from the installation default. " - + "Please see the JBoss Messaging user guide for instructions on how to do this."); + + "Please see the HornetQ user guide for instructions on how to do this."); } } Modified: trunk/src/main/org/hornetq/core/management/package.html =================================================================== --- trunk/src/main/org/hornetq/core/management/package.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/src/main/org/hornetq/core/management/package.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -12,11 +12,11 @@ </head> <body> -<p>Provides management for JBoss Messaging</p> +<p>Provides management for HornetQ</p> <h2>Usage</h2> -<p>JBoss Messaging can be managed by sending well-formatted <em>messages</em> to a well-known <em>management address</em>. +<p>HornetQ can be managed by sending well-formatted <em>messages</em> to a well-known <em>management address</em>. The invocation of management operations (and retrieval of management attributes) is based on JMX semantics. Managed resources are identified by <code>ObjectNames</code> (defined in <code>ManagementServiceImpl.getXXXObjectName()</code> methods).</p> @@ -33,20 +33,20 @@ <management-address>admin.management</management-address> <management-notification-address>admin.notification</management-notification-address> -  +  <jmx-management-enabled>true</jmx-management-enabled> </code></pre> <h2>Management using JMX</h2> -<p>In addition to using messages, JBoss Messaging can also be managed using JMX (if the configuration property +<p>In addition to using messages, HornetQ can also be managed using JMX (if the configuration property <code>jmx-management-enabled</code> is set to <code>true</code>).<br /> -JBoss Messaging is run in standalone to allow remote JMX management from the same machine (<code>-Dcom.sun.management.jmxremote</code>). -A JMX client (e.g. <code>jconsole</code>) can be used locally to manage JBoss Messaging.</p> +HornetQ is run in standalone to allow remote JMX management from the same machine (<code>-Dcom.sun.management.jmxremote</code>). +A JMX client (e.g. <code>jconsole</code>) can be used locally to manage HornetQ.</p> <h2>Design</h2> -<p>The core of the management support in JBoss Messaging is the ManagementServiceImpl class.<br /> +<p>The core of the management support in HornetQ is the ManagementServiceImpl class.<br /> This class is responsible to:</p> <ul> @@ -63,7 +63,7 @@ <h2>Management in a clustered environment and JMX</h2> -<p>Using core messages to manage JBoss Messaging also works in a clustered environment: the management messages are +<p>Using core messages to manage HornetQ also works in a clustered environment: the management messages are replicated on the nodes of the cluster, ensuring that the state is replicated on all the nodes.</p> <p>To allow JMX to work in a clustered environment, the MBean implementation do not delegates directly to the resources Modified: trunk/src/main/org/hornetq/core/remoting/Interceptor.java =================================================================== --- trunk/src/main/org/hornetq/core/remoting/Interceptor.java 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/src/main/org/hornetq/core/remoting/Interceptor.java 2009-08-20 15:17:39 UTC (rev 7830) @@ -17,7 +17,7 @@ /** * - * This is class is a simple way to intercepting server calls on JBoss Messaging. + * This is class is a simple way to intercepting server calls on HornetQ. * * To Add this interceptor, you have to modify hornetq-configuration.xml * Modified: trunk/src/main/org/hornetq/core/server/impl/MessagingServerImpl.java =================================================================== --- trunk/src/main/org/hornetq/core/server/impl/MessagingServerImpl.java 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/src/main/org/hornetq/core/server/impl/MessagingServerImpl.java 2009-08-20 15:17:39 UTC (rev 7830) @@ -287,7 +287,7 @@ // so it can be initialised by the live node remotingService.start(); - log.info("JBoss Messaging Server version " + getVersion().getFullVersion() + " started"); + log.info("HornetQ Server version " + getVersion().getFullVersion() + " started"); } @Override @@ -419,7 +419,7 @@ initialised = false; uuid = null; nodeID = null; - log.info("JBoss Messaging Server version " + getVersion().getFullVersion() + " stopped"); + log.info("HornetQ Server version " + getVersion().getFullVersion() + " stopped"); } // MessagingServer implementation Modified: trunk/src/main/org/hornetq/core/transaction/Transaction.java =================================================================== --- trunk/src/main/org/hornetq/core/transaction/Transaction.java 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/src/main/org/hornetq/core/transaction/Transaction.java 2009-08-20 15:17:39 UTC (rev 7830) @@ -21,7 +21,7 @@ import org.hornetq.core.server.Queue; /** - * A JBoss Messaging internal transaction + * A HornetQ internal transaction * * @author <a href="mailto:tim.fox@jboss.com">Tim Fox</a> * @author <a href="mailto:andy.taylor@jboss.org>Andy Taylor</a> Modified: trunk/src/main/org/hornetq/integration/bootstrap/HornetQBootstrapServer.java =================================================================== --- trunk/src/main/org/hornetq/integration/bootstrap/HornetQBootstrapServer.java 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/src/main/org/hornetq/integration/bootstrap/HornetQBootstrapServer.java 2009-08-20 15:17:39 UTC (rev 7830) @@ -66,7 +66,7 @@ */ public static void main(final String[] args) throws Exception { - log.info("Starting JBoss Messaging Server"); + log.info("Starting HornetQ Server"); final HornetQBootstrapServer bootstrap = new HornetQBootstrapServer(args); @@ -96,7 +96,7 @@ { try { - log.info("Stopping JBoss Messaging Server"); + log.info("Stopping HornetQ Server"); shutDown(); timer.cancel(); } Modified: trunk/src/main/org/hornetq/jms/bridge/QualityOfServiceMode.java =================================================================== --- trunk/src/main/org/hornetq/jms/bridge/QualityOfServiceMode.java 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/src/main/org/hornetq/jms/bridge/QualityOfServiceMode.java 2009-08-20 15:17:39 UTC (rev 7830) @@ -39,7 +39,7 @@ * * 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 JBoss Messaging server + * 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 transaction. If the source and destination are on different * servers this is achieved by enlisting the sending and consuming sessions in a Modified: trunk/src/main/org/hornetq/jms/client/HornetQConnectionMetaData.java =================================================================== --- trunk/src/main/org/hornetq/jms/client/HornetQConnectionMetaData.java 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/src/main/org/hornetq/jms/client/HornetQConnectionMetaData.java 2009-08-20 15:17:39 UTC (rev 7830) @@ -224,7 +224,7 @@ { // Constants ----------------------------------------------------- - public static final String JBOSS_MESSAGING = "JBoss Messaging"; + public static final String JBOSS_MESSAGING = "HornetQ"; // Static -------------------------------------------------------- Modified: trunk/src/main/org/hornetq/jms/client/HornetQTextMessage.java =================================================================== --- trunk/src/main/org/hornetq/jms/client/HornetQTextMessage.java 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/src/main/org/hornetq/jms/client/HornetQTextMessage.java 2009-08-20 15:17:39 UTC (rev 7830) @@ -264,7 +264,7 @@ } /** - * A copy constructor for non-JBoss Messaging JMS TextMessages. + * A copy constructor for non-HornetQ JMS TextMessages. */ public HornetQTextMessage(final TextMessage foreign, final ClientSession session) throws JMSException { Modified: trunk/src/main/org/hornetq/ra/HornetQRAConnectionMetaData.java =================================================================== --- trunk/src/main/org/hornetq/ra/HornetQRAConnectionMetaData.java 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/src/main/org/hornetq/ra/HornetQRAConnectionMetaData.java 2009-08-20 15:17:39 UTC (rev 7830) @@ -289,7 +289,7 @@ log.trace("getJMSProviderName()"); } - return "JBoss Messaging"; + return "HornetQ"; } /** Modified: trunk/src/main/org/hornetq/ra/HornetQRAMetaData.java =================================================================== --- trunk/src/main/org/hornetq/ra/HornetQRAMetaData.java 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/src/main/org/hornetq/ra/HornetQRAMetaData.java 2009-08-20 15:17:39 UTC (rev 7830) @@ -252,7 +252,7 @@ log.trace("getEISProductName()"); } - return "JBoss Messaging"; + return "HornetQ"; } /** Modified: trunk/src/main/org/hornetq/ra/HornetQResourceAdapter.java =================================================================== --- trunk/src/main/org/hornetq/ra/HornetQResourceAdapter.java 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/src/main/org/hornetq/ra/HornetQResourceAdapter.java 2009-08-20 15:17:39 UTC (rev 7830) @@ -36,7 +36,7 @@ import org.hornetq.ra.inflow.HornetQActivationSpec; /** - * The resource adapter for JBoss Messaging + * The resource adapter for HornetQ * * @author <a href="adrian(a)jboss.com">Adrian Brock</a> * @author <a href="jesper.pedersen(a)jboss.org">Jesper Pedersen</a> @@ -181,7 +181,7 @@ this.ctx = ctx; - log.info("JBoss Messaging resource adaptor started"); + log.info("HornetQ resource adaptor started"); } /** @@ -208,7 +208,7 @@ activations.clear(); - log.info("JBoss Messaging resource adapter stopped"); + log.info("HornetQ resource adapter stopped"); } public void setConnectorClassName(final String connectorClassName) Modified: trunk/src/main/org/hornetq/ra/package.html =================================================================== --- trunk/src/main/org/hornetq/ra/package.html 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/src/main/org/hornetq/ra/package.html 2009-08-20 15:17:39 UTC (rev 7830) @@ -18,7 +18,7 @@ </head> <body bgcolor="white"> - <h1>JBoss Messaging Resource Adaptor</h1> + <h1>HornetQ Resource Adaptor</h1> </body> </html> Modified: trunk/tests/jms-tests/src/org/hornetq/jmstests/message/foreign/ForeignBytesMessageTest.java =================================================================== --- trunk/tests/jms-tests/src/org/hornetq/jmstests/message/foreign/ForeignBytesMessageTest.java 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/tests/jms-tests/src/org/hornetq/jmstests/message/foreign/ForeignBytesMessageTest.java 2009-08-20 15:17:39 UTC (rev 7830) @@ -37,7 +37,7 @@ log.debug("creating JMS Message type " + m.getClass().getName()); - String bytes = "jboss messaging"; + String bytes = "HornetQ"; m.writeBytes(bytes.getBytes()); return m; } @@ -56,6 +56,6 @@ sb.append(new String(buffer,0,n)); n = byteMsg.readBytes(buffer); } - assertEquals("jboss messaging",sb.toString()); + assertEquals("HornetQ",sb.toString()); } } \ No newline at end of file Modified: trunk/tests/jms-tests/src/org/hornetq/jmstests/tools/ant/GenerateSmokeReport.java =================================================================== --- trunk/tests/jms-tests/src/org/hornetq/jmstests/tools/ant/GenerateSmokeReport.java 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/tests/jms-tests/src/org/hornetq/jmstests/tools/ant/GenerateSmokeReport.java 2009-08-20 15:17:39 UTC (rev 7830) @@ -329,10 +329,10 @@ try { pw.println("<html>"); - pw.println("<head><title>JBoss Messaging Smoke Test Results</title></head>"); + pw.println("<head><title>HornetQ Smoke Test Results</title></head>"); pw.println("<body>"); - pw.println("<h1>JBoss Messaging Smoke Test Results</h1>"); + pw.println("<h1>HornetQ Smoke Test Results</h1>"); pw.print("Java version: "); pw.print(System.getProperty("java.version")); Modified: trunk/tests/src/org/hornetq/tests/unit/core/filter/impl/FilterParserTest.java =================================================================== --- trunk/tests/src/org/hornetq/tests/unit/core/filter/impl/FilterParserTest.java 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/tests/src/org/hornetq/tests/unit/core/filter/impl/FilterParserTest.java 2009-08-20 15:17:39 UTC (rev 7830) @@ -25,7 +25,7 @@ import org.hornetq.core.filter.impl.FilterParser; /** - Tests of the JavaCC LL(1) parser for the JBoss Messaging filters + Tests of the JavaCC LL(1) parser for the HornetQ filters @author Scott.Stark(a)jboss.org @author d_jencks(a)users.sourceforge.net Modified: trunk/tests/src/org/hornetq/tests/unit/core/filter/impl/FilterTest.java =================================================================== --- trunk/tests/src/org/hornetq/tests/unit/core/filter/impl/FilterTest.java 2009-08-20 14:44:18 UTC (rev 7829) +++ trunk/tests/src/org/hornetq/tests/unit/core/filter/impl/FilterTest.java 2009-08-20 15:17:39 UTC (rev 7830) @@ -24,7 +24,7 @@ import org.hornetq.utils.SimpleString; /** - * Tests the compliance with the JBoss Messaging Filter syntax. + * Tests the compliance with the HornetQ Filter syntax. * * @author <a href="mailto:jason@planet57.com">Jason Dillon</a> * @author <a href="mailto:tim.fox@jboss.com">Tim Fox</a>

15 years, 6 months

1
0
0 / 0

JBoss hornetq SVN: r7828 - trunk/tests/joram-tests/config.

by do-not-reply＠jboss.org

Author: jmesnil Date: 2009-08-20 08:07:28 -0400 (Thu, 20 Aug 2009) New Revision: 7828 Modified: trunk/tests/joram-tests/config/provider.properties Log: fixed Admin class name Modified: trunk/tests/joram-tests/config/provider.properties =================================================================== --- trunk/tests/joram-tests/config/provider.properties 2009-08-20 11:22:06 UTC (rev 7827) +++ trunk/tests/joram-tests/config/provider.properties 2009-08-20 12:07:28 UTC (rev 7828) @@ -27,7 +27,7 @@ # Uncomment the chosen provider and comment the other ones ## -jms.provider.admin.class=org.hornetq.jms.JBossMessagingAdmin +jms.provider.admin.class=org.hornetq.jms.HornetQAdmin #jms.provider.admin.class = org.hornetq.jms.GenericAdmin #jms.provider.admin.class = org.objectweb.jtests.providers.admin.JoramAdmin #jms.provider.admin.class = org.objectweb.jtests.providers.admin.AshnaMQAdmin

15 years, 6 months

1
0
0 / 0

JBoss hornetq SVN: r7827 - trunk/src/main/org/hornetq/utils/concurrent.

by do-not-reply＠jboss.org

Author: ataylor Date: 2009-08-20 07:22:06 -0400 (Thu, 20 Aug 2009) New Revision: 7827 Modified: trunk/src/main/org/hornetq/utils/concurrent/BlockingDeque.java trunk/src/main/org/hornetq/utils/concurrent/Deque.java trunk/src/main/org/hornetq/utils/concurrent/LinkedBlockingDeque.java Log: updated licenses Modified: trunk/src/main/org/hornetq/utils/concurrent/BlockingDeque.java =================================================================== --- trunk/src/main/org/hornetq/utils/concurrent/BlockingDeque.java 2009-08-20 11:14:21 UTC (rev 7826) +++ trunk/src/main/org/hornetq/utils/concurrent/BlockingDeque.java 2009-08-20 11:22:06 UTC (rev 7827) @@ -1,22 +1,9 @@ /* - * Copyright 2009 Red Hat, Inc. - * Red Hat licenses this file to you under the Apache License, version - * 2.0 (the "License"); you may not use this file except in compliance - * with the License. You may obtain a copy of the License at - * http://www.apache.org/licenses/LICENSE-2.0 - * Unless required by applicable law or agreed to in writing, software - * distributed under the License is distributed on an "AS IS" BASIS, - * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or - * implied. See the License for the specific language governing - * permissions and limitations under the License. + * Written by Doug Lea and Josh Bloch with assistance from members of + * JCP JSR-166 Expert Group and released to the public domain, as explained + * at http://creativecommons.org/licenses/publicdomain */ -/* - * Written by Doug Lea with assistance from members of JCP JSR-166 - * Expert Group and released to the public domain, as explained at - * http://creativecommons.org/licenses/publicdomain - */ - package org.hornetq.utils.concurrent; // XXX This belongs in java.util!!! XXX import java.util.concurrent.*; // XXX This import goes away XXX import java.util.*; Modified: trunk/src/main/org/hornetq/utils/concurrent/Deque.java =================================================================== --- trunk/src/main/org/hornetq/utils/concurrent/Deque.java 2009-08-20 11:14:21 UTC (rev 7826) +++ trunk/src/main/org/hornetq/utils/concurrent/Deque.java 2009-08-20 11:22:06 UTC (rev 7827) @@ -1,17 +1,4 @@ /* - * Copyright 2009 Red Hat, Inc. - * Red Hat licenses this file to you under the Apache License, version - * 2.0 (the "License"); you may not use this file except in compliance - * with the License. You may obtain a copy of the License at - * http://www.apache.org/licenses/LICENSE-2.0 - * Unless required by applicable law or agreed to in writing, software - * distributed under the License is distributed on an "AS IS" BASIS, - * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or - * implied. See the License for the specific language governing - * permissions and limitations under the License. - */ - -/* * Written by Doug Lea and Josh Bloch with assistance from members of * JCP JSR-166 Expert Group and released to the public domain, as explained * at http://creativecommons.org/licenses/publicdomain Modified: trunk/src/main/org/hornetq/utils/concurrent/LinkedBlockingDeque.java =================================================================== --- trunk/src/main/org/hornetq/utils/concurrent/LinkedBlockingDeque.java 2009-08-20 11:14:21 UTC (rev 7826) +++ trunk/src/main/org/hornetq/utils/concurrent/LinkedBlockingDeque.java 2009-08-20 11:22:06 UTC (rev 7827) @@ -1,22 +1,9 @@ /* - * Copyright 2009 Red Hat, Inc. - * Red Hat licenses this file to you under the Apache License, version - * 2.0 (the "License"); you may not use this file except in compliance - * with the License. You may obtain a copy of the License at - * http://www.apache.org/licenses/LICENSE-2.0 - * Unless required by applicable law or agreed to in writing, software - * distributed under the License is distributed on an "AS IS" BASIS, - * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or - * implied. See the License for the specific language governing - * permissions and limitations under the License. + * Written by Doug Lea and Josh Bloch with assistance from members of + * JCP JSR-166 Expert Group and released to the public domain, as explained + * at http://creativecommons.org/licenses/publicdomain */ -/* - * Written by Doug Lea with assistance from members of JCP JSR-166 - * Expert Group and released to the public domain, as explained at - * http://creativecommons.org/licenses/publicdomain - */ - package org.hornetq.utils.concurrent; import java.util.*;

15 years, 6 months

1
0
0 / 0

JBoss hornetq SVN: r7822 - in trunk/src/main/org/hornetq/core/security: impl and 1 other directory.

by do-not-reply＠jboss.org

Author: timfox Date: 2009-08-20 04:13:32 -0400 (Thu, 20 Aug 2009) New Revision: 7822 Modified: trunk/src/main/org/hornetq/core/security/CheckType.java trunk/src/main/org/hornetq/core/security/impl/JAASSecurityManager.java trunk/src/main/org/hornetq/core/security/impl/SecurityStoreImpl.java Log: removed invalid author tags as per legal Modified: trunk/src/main/org/hornetq/core/security/CheckType.java =================================================================== --- trunk/src/main/org/hornetq/core/security/CheckType.java 2009-08-20 08:02:01 UTC (rev 7821) +++ trunk/src/main/org/hornetq/core/security/CheckType.java 2009-08-20 08:13:32 UTC (rev 7822) @@ -205,8 +205,6 @@ package org.hornetq.core.security; /** - * @author Peter Antman - * @author <a href="mailto:Scott.Stark@jboss.org">Scott Stark</a> * @author <a href="mailto:jmesnil@redhat.com">Jeff Mesnil</a> * @author <a href="mailto:andy.taylor@jboss.org>Andy Taylor</a> * @version $Revision: 2925 $ Modified: trunk/src/main/org/hornetq/core/security/impl/JAASSecurityManager.java =================================================================== --- trunk/src/main/org/hornetq/core/security/impl/JAASSecurityManager.java 2009-08-20 08:02:01 UTC (rev 7821) +++ trunk/src/main/org/hornetq/core/security/impl/JAASSecurityManager.java 2009-08-20 08:13:32 UTC (rev 7822) @@ -230,8 +230,6 @@ * @author <a href="ataylor(a)redhat.com">Andy Taylor</a> * @author <a href="tim.fox(a)jboss.com">Tim Fox</a> * @author <a href="jmesnil(a)redhat.com">Jeff Mesnil</a> - * @author <a href="on(a)ibis.odessa.ua">Oleg Nitz</a> - * @author Scott.Stark(a)jboss.org */ public class JAASSecurityManager implements JBMSecurityManager, MessagingComponent { Modified: trunk/src/main/org/hornetq/core/security/impl/SecurityStoreImpl.java =================================================================== --- trunk/src/main/org/hornetq/core/security/impl/SecurityStoreImpl.java 2009-08-20 08:02:01 UTC (rev 7821) +++ trunk/src/main/org/hornetq/core/security/impl/SecurityStoreImpl.java 2009-08-20 08:13:32 UTC (rev 7822) @@ -233,12 +233,7 @@ * @author <a href="mailto:tim.fox@jboss.com">Tim Fox</a> * @author <a href="ataylor(a)redhat.com">Andy Taylor</a> * - * Parts based on old version by: * - * @author Peter Antman - * @author <a href="mailto:Scott.Stark@jboss.org">Scott Stark</a> - * @author <a href="mailto:ovidiu@feodorov.com">Ovidiu Feodorov</a> - * * @version $Revision$ * * $Id$

15 years, 7 months

1
0
0 / 0

JBoss hornetq SVN: r7821 - in trunk: src/main/org/hornetq/core/buffers and 3 other directories.

by do-not-reply＠jboss.org

Author: timfox Date: 2009-08-20 04:02:01 -0400 (Thu, 20 Aug 2009) New Revision: 7821 Modified: trunk/build-hornetq.xml trunk/build-maven.xml trunk/pom.xml trunk/src/main/org/hornetq/core/buffers/AbstractChannelBuffer.java trunk/src/main/org/hornetq/core/client/impl/LargeMessageBufferImpl.java trunk/src/main/org/hornetq/core/management/ObjectNames.java trunk/src/main/org/hornetq/integration/transports/netty/ChannelBufferWrapper.java Log: remove remaining refs to org.jboss.messaging from files Modified: trunk/build-hornetq.xml =================================================================== --- trunk/build-hornetq.xml 2009-08-20 07:39:00 UTC (rev 7820) +++ trunk/build-hornetq.xml 2009-08-20 08:02:01 UTC (rev 7821) @@ -1102,7 +1102,7 @@ <bottom><![CDATA[<i>Copyright © 2006 JBoss Inc. All Rights Reserved.</i>]]></bottom> <tag name="todo" scope="all" description="To do:"/> <group title="JMS Facade" packages="org.jboss.jms.*"/> - <group title="Messaging Core" packages="org.jboss.messaging.*"/> + <group title="Messaging Core" packages="org.hornetq.*"/> </javadoc> </target> Modified: trunk/build-maven.xml =================================================================== --- trunk/build-maven.xml 2009-08-20 07:39:00 UTC (rev 7820) +++ trunk/build-maven.xml 2009-08-20 08:02:01 UTC (rev 7821) @@ -283,7 +283,7 @@ <exec executable="mvn"> <arg value="-s settings.xml"/> <arg value="deploy:deploy-file"/> - <arg value="-DgroupId=org.jboss.messaging"/> + <arg value="-DgroupId=org.hornetq"/> <arg value="-DartifactId=${artifact.id}"/> <arg value="-Dversion=${jbm.version}"/> <arg value="-Dpackaging=${artifact.type}"/> Modified: trunk/pom.xml =================================================================== --- trunk/pom.xml 2009-08-20 07:39:00 UTC (rev 7820) +++ trunk/pom.xml 2009-08-20 08:02:01 UTC (rev 7821) @@ -207,15 +207,15 @@ xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> <modelVersion>4.0.0</modelVersion> - <groupId>org.jboss.messaging</groupId> + <groupId>org.hornetq</groupId> <artifactId>messaging</artifactId> <packaging>pom</packaging> <version>2.0.0.BETA3-SNAPSHOT</version> - <name>The JBoss Messaging Project</name> - <url>http://www.jboss.org/jbossmessaging</url> + <name>HornetQ</name> + <url>http://hornetq.org</url> <description> - JBoss Messaging enables high performance, clustered messaging for Java. + Putting the buzz in messaging </description> <organization> Modified: trunk/src/main/org/hornetq/core/buffers/AbstractChannelBuffer.java =================================================================== --- trunk/src/main/org/hornetq/core/buffers/AbstractChannelBuffer.java 2009-08-20 07:39:00 UTC (rev 7820) +++ trunk/src/main/org/hornetq/core/buffers/AbstractChannelBuffer.java 2009-08-20 08:02:01 UTC (rev 7821) @@ -908,7 +908,7 @@ } /* (non-Javadoc) - * @see org.hornetq.core.remoting.spi.MessagingBuffer#writeNullableSimpleString(org.jboss.messaging.util.SimpleString) + * @see org.hornetq.core.remoting.spi.MessagingBuffer#writeNullableSimpleString(org.hornetq.util.SimpleString) */ public void writeNullableSimpleString(final SimpleString val) { @@ -940,7 +940,7 @@ } /* (non-Javadoc) - * @see org.hornetq.core.remoting.spi.MessagingBuffer#writeSimpleString(org.jboss.messaging.util.SimpleString) + * @see org.hornetq.core.remoting.spi.MessagingBuffer#writeSimpleString(org.hornetq.util.SimpleString) */ public void writeSimpleString(final SimpleString val) { Modified: trunk/src/main/org/hornetq/core/client/impl/LargeMessageBufferImpl.java =================================================================== --- trunk/src/main/org/hornetq/core/client/impl/LargeMessageBufferImpl.java 2009-08-20 07:39:00 UTC (rev 7820) +++ trunk/src/main/org/hornetq/core/client/impl/LargeMessageBufferImpl.java 2009-08-20 08:02:01 UTC (rev 7821) @@ -1328,7 +1328,7 @@ } /* (non-Javadoc) - * @see org.hornetq.core.remoting.spi.MessagingBuffer#writeNullableSimpleString(org.jboss.messaging.util.SimpleString) + * @see org.hornetq.core.remoting.spi.MessagingBuffer#writeNullableSimpleString(org.hornetq.util.SimpleString) */ public void writeNullableSimpleString(final SimpleString val) { @@ -1344,7 +1344,7 @@ } /* (non-Javadoc) - * @see org.hornetq.core.remoting.spi.MessagingBuffer#writeSimpleString(org.jboss.messaging.util.SimpleString) + * @see org.hornetq.core.remoting.spi.MessagingBuffer#writeSimpleString(org.hornetq.util.SimpleString) */ public void writeSimpleString(final SimpleString val) { Modified: trunk/src/main/org/hornetq/core/management/ObjectNames.java =================================================================== --- trunk/src/main/org/hornetq/core/management/ObjectNames.java 2009-08-20 07:39:00 UTC (rev 7820) +++ trunk/src/main/org/hornetq/core/management/ObjectNames.java 2009-08-20 08:02:01 UTC (rev 7821) @@ -223,7 +223,7 @@ // Constants ----------------------------------------------------- - public static final String DOMAIN = "org.jboss.messaging"; + public static final String DOMAIN = "org.hornetq"; public static final String JMS_MODULE = "JMS"; Modified: trunk/src/main/org/hornetq/integration/transports/netty/ChannelBufferWrapper.java =================================================================== --- trunk/src/main/org/hornetq/integration/transports/netty/ChannelBufferWrapper.java 2009-08-20 07:39:00 UTC (rev 7820) +++ trunk/src/main/org/hornetq/integration/transports/netty/ChannelBufferWrapper.java 2009-08-20 08:02:01 UTC (rev 7821) @@ -525,7 +525,7 @@ } /* (non-Javadoc) - * @see org.hornetq.core.remoting.spi.MessagingBuffer#writeNullableSimpleString(org.jboss.messaging.util.SimpleString) + * @see org.hornetq.core.remoting.spi.MessagingBuffer#writeNullableSimpleString(org.hornetq.util.SimpleString) */ public void writeNullableSimpleString(final SimpleString val) { @@ -557,7 +557,7 @@ } /* (non-Javadoc) - * @see org.hornetq.core.remoting.spi.MessagingBuffer#writeSimpleString(org.jboss.messaging.util.SimpleString) + * @see org.hornetq.core.remoting.spi.MessagingBuffer#writeSimpleString(org.hornetq.util.SimpleString) */ public void writeSimpleString(final SimpleString val) {

15 years, 7 months

1
0
0 / 0

JBoss hornetq SVN: r7820 - in trunk: licenses and 1 other directory.

by do-not-reply＠jboss.org

Author: ataylor Date: 2009-08-20 03:39:00 -0400 (Thu, 20 Aug 2009) New Revision: 7820 Added: trunk/NOTICE trunk/licenses/LICENSE.txt Removed: trunk/JBossORG-EULA.txt Log: license files updates Deleted: trunk/JBossORG-EULA.txt =================================================================== --- trunk/JBossORG-EULA.txt 2009-08-20 07:36:14 UTC (rev 7819) +++ trunk/JBossORG-EULA.txt 2009-08-20 07:39:00 UTC (rev 7820) @@ -1,106 +0,0 @@ -LICENSE AGREEMENT -JBOSS(r) - -This License Agreement governs the use of the Software Packages and any updates to the Software -Packages, regardless of the delivery mechanism. Each Software Package is a collective work -under U.S. Copyright Law. Subject to the following terms, Red Hat, Inc. ("Red Hat") grants to -the user ("Client") a license to the applicable collective work(s) pursuant to the -GNU Lesser General Public License v. 2.1 except for the following Software Packages: -(a) JBoss Portal Forums and JBoss Transactions JTS, each of which is licensed pursuant to the -GNU General Public License v.2; - -(b) JBoss Rules, which is licensed pursuant to the Apache License v.2.0; - -(c) an optional download for JBoss Cache for the Berkeley DB for Java database, which is licensed under the -(open source) Sleepycat License (if Client does not wish to use the open source version of this database, -it may purchase a license from Sleepycat Software); - -and (d) the BPEL extension for JBoss jBPM, which is licensed under the Common Public License v.1, -and, pursuant to the OASIS BPEL4WS standard, requires parties wishing to redistribute to enter various -royalty-free patent licenses. - -Each of the foregoing licenses is available at http://www.opensource.org/licenses/index.php. - -1. The Software. "Software Packages" refer to the various software modules that are created and made available -for distribution by the JBoss.org open source community at http://www.jboss.org. Each of the Software Packages -may be comprised of hundreds of software components. The end user license agreement for each component is located in -the component's source code. With the exception of certain image files identified in Section 2 below, -the license terms for the components permit Client to copy, modify, and redistribute the component, -in both source code and binary code forms. This agreement does not limit Client's rights under, -or grant Client rights that supersede, the license terms of any particular component. - -2. Intellectual Property Rights. The Software Packages are owned by Red Hat and others and are protected under copyright -and other laws. Title to the Software Packages and any component, or to any copy, modification, or merged portion shall -remain with the aforementioned, subject to the applicable license. The "JBoss" trademark, "Red Hat" trademark, the -individual Software Package trademarks, and the "Shadowman" logo are registered trademarks of Red Hat and its affiliates -in the U.S. and other countries. This agreement permits Client to distribute unmodified copies of the Software Packages -using the Red Hat trademarks that Red Hat has inserted in the Software Packages on the condition that Client follows Red Hat's -trademark guidelines for those trademarks located at http://www.redhat.com/about/corporate/trademark/. Client must abide by -these trademark guidelines when distributing the Software Packages, regardless of whether the Software Packages have been modified. -If Client modifies the Software Packages, then Client must replace all Red Hat trademarks and logos identified at -http://www.jboss.com/company/logos, unless a separate agreement with Red Hat is executed or other permission granted. -Merely deleting the files containing the Red Hat trademarks may corrupt the Software Packages. - -3. Limited Warranty. Except as specifically stated in this Paragraph 3 or a license for a particular -component, to the maximum extent permitted under applicable law, the Software Packages and the -components are provided and licensed "as is" without warranty of any kind, expressed or implied, -including the implied warranties of merchantability, non-infringement or fitness for a particular purpose. -Red Hat warrants that the media on which Software Packages may be furnished will be free from defects in -materials and manufacture under normal use for a period of 30 days from the date of delivery to Client. -Red Hat does not warrant that the functions contained in the Software Packages will meet Client's requirements -or that the operation of the Software Packages will be entirely error free or appear precisely as described -in the accompanying documentation. This warranty extends only to the party that purchases the Services -pertaining to the Software Packages from Red Hat or a Red Hat authorized distributor. - -4. Limitation of Remedies and Liability. To the maximum extent permitted by applicable law, the remedies -described below are accepted by Client as its only remedies. Red Hat's entire liability, and Client's -exclusive remedies, shall be: If the Software media is defective, Client may return it within 30 days of -delivery along with a copy of Client's payment receipt and Red Hat, at its option, will replace it or -refund the money paid by Client for the Software. To the maximum extent permitted by applicable law, -Red Hat or any Red Hat authorized dealer will not be liable to Client for any incidental or consequential -damages, including lost profits or lost savings arising out of the use or inability to use the Software, -even if Red Hat or such dealer has been advised of the possibility of such damages. In no event shall -Red Hat's liability under this agreement exceed the amount that Client paid to Red Hat under this -Agreement during the twelve months preceding the action. - -5. Export Control. As required by U.S. law, Client represents and warrants that it: -(a) understands that the Software Packages are subject to export controls under the -U.S. Commerce Department's Export Administration Regulations ("EAR"); - -(b) is not located in a prohibited destination country under the EAR or U.S. sanctions regulations -(currently Cuba, Iran, Iraq, Libya, North Korea, Sudan and Syria); - -(c) will not export, re-export, or transfer the Software Packages to any prohibited destination, entity, -or individual without the necessary export license(s) or authorizations(s) from the U.S. Government; - -(d) will not use or transfer the Software Packages for use in any sensitive nuclear, chemical or -biological weapons, or missile technology end-uses unless authorized by the U.S. Government by -regulation or specific license; - -(e) understands and agrees that if it is in the United States and exports or transfers the Software -Packages to eligible end users, it will, as required by EAR Section 740.17(e), submit semi-annual -reports to the Commerce Department's Bureau of Industry & Security (BIS), which include the name and -address (including country) of each transferee; - -and (f) understands that countries other than the United States may restrict the import, use, or -export of encryption products and that it shall be solely responsible for compliance with any such -import, use, or export restrictions. - -6. Third Party Programs. Red Hat may distribute third party software programs with the Software Packages -that are not part of the Software Packages and which Client must install separately. These third party -programs are subject to their own license terms. The license terms either accompany the programs or -can be viewed at http://www.redhat.com/licenses/. If Client does not agree to abide by the applicable -license terms for such programs, then Client may not install them. If Client wishes to install the programs -on more than one system or transfer the programs to another party, then Client must contact the licensor -of the programs. - -7. General. If any provision of this agreement is held to be unenforceable, that shall not affect the -enforceability of the remaining provisions. This License Agreement shall be governed by the laws of the -State of North Carolina and of the United States, without regard to any conflict of laws provisions, -except that the United Nations Convention on the International Sale of Goods shall not apply. - -Copyright 2006 Red Hat, Inc. All rights reserved. -"JBoss" and the JBoss logo are registered trademarks of Red Hat, Inc. -All other trademarks are the property of their respective owners. - - Page 1 of 1 18 October 2006 Added: trunk/NOTICE =================================================================== --- trunk/NOTICE (rev 0) +++ trunk/NOTICE 2009-08-20 07:39:00 UTC (rev 7820) @@ -0,0 +1,14 @@ +JBoss Messaging +Copyright 2009 Red Hat, Inc. Licensed under the Apache License, version 2.0. +Unless required by applicable law, JBoss Messaging is distributed on +an "AS IS" BASIS, WITHOUT WARRANTIES OF ANY KIND, either express or +implied, including the implied warranties of TITLE, NON-INFRINGEMENT, +MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. + +Certain portions of JBoss Messaging are based on code made available +under the GNU Lesser General Public License, version 2.1 or later +(http://www.fsf.org/licensing/licenses/lgpl.html). +"JBoss" and "Red Hat" are trademarks of Red Hat, Inc. and/or its +affiliates, registered in the U.S. and other countries. Your +permissions under the licensing terms governing JBoss Messaging do +not include a license, express or implied, to any Red Hat trademark. \ No newline at end of file Added: trunk/licenses/LICENSE.txt =================================================================== --- trunk/licenses/LICENSE.txt (rev 0) +++ trunk/licenses/LICENSE.txt 2009-08-20 07:39:00 UTC (rev 7820) @@ -0,0 +1,202 @@ + + Apache License + Version 2.0, January 2004 + http://www.apache.org/licenses/ + + TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION + + 1. Definitions. + + "License" shall mean the terms and conditions for use, reproduction, + and distribution as defined by Sections 1 through 9 of this document. + + "Licensor" shall mean the copyright owner or entity authorized by + the copyright owner that is granting the License. + + "Legal Entity" shall mean the union of the acting entity and all + other entities that control, are controlled by, or are under common + control with that entity. For the purposes of this definition, + "control" means (i) the power, direct or indirect, to cause the + direction or management of such entity, whether by contract or + otherwise, or (ii) ownership of fifty percent (50%) or more of the + outstanding shares, or (iii) beneficial ownership of such entity. + + "You" (or "Your") shall mean an individual or Legal Entity + exercising permissions granted by this License. + + "Source" form shall mean the preferred form for making modifications, + including but not limited to software source code, documentation + source, and configuration files. + + "Object" form shall mean any form resulting from mechanical + transformation or translation of a Source form, including but + not limited to compiled object code, generated documentation, + and conversions to other media types. + + "Work" shall mean the work of authorship, whether in Source or + Object form, made available under the License, as indicated by a + copyright notice that is included in or attached to the work + (an example is provided in the Appendix below). + + "Derivative Works" shall mean any work, whether in Source or Object + form, that is based on (or derived from) the Work and for which the + editorial revisions, annotations, elaborations, or other modifications + represent, as a whole, an original work of authorship. For the purposes + of this License, Derivative Works shall not include works that remain + separable from, or merely link (or bind by name) to the interfaces of, + the Work and Derivative Works thereof. + + "Contribution" shall mean any work of authorship, including + the original version of the Work and any modifications or additions + to that Work or Derivative Works thereof, that is intentionally + submitted to Licensor for inclusion in the Work by the copyright owner + or by an individual or Legal Entity authorized to submit on behalf of + the copyright owner. For the purposes of this definition, "submitted" + means any form of electronic, verbal, or written communication sent + to the Licensor or its representatives, including but not limited to + communication on electronic mailing lists, source code control systems, + and issue tracking systems that are managed by, or on behalf of, the + Licensor for the purpose of discussing and improving the Work, but + excluding communication that is conspicuously marked or otherwise + designated in writing by the copyright owner as "Not a Contribution." + + "Contributor" shall mean Licensor and any individual or Legal Entity + on behalf of whom a Contribution has been received by Licensor and + subsequently incorporated within the Work. + + 2. Grant of Copyright License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + copyright license to reproduce, prepare Derivative Works of, + publicly display, publicly perform, sublicense, and distribute the + Work and such Derivative Works in Source or Object form. + + 3. Grant of Patent License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + (except as stated in this section) patent license to make, have made, + use, offer to sell, sell, import, and otherwise transfer the Work, + where such license applies only to those patent claims licensable + by such Contributor that are necessarily infringed by their + Contribution(s) alone or by combination of their Contribution(s) + with the Work to which such Contribution(s) was submitted. If You + institute patent litigation against any entity (including a + cross-claim or counterclaim in a lawsuit) alleging that the Work + or a Contribution incorporated within the Work constitutes direct + or contributory patent infringement, then any patent licenses + granted to You under this License for that Work shall terminate + as of the date such litigation is filed. + + 4. Redistribution. You may reproduce and distribute copies of the + Work or Derivative Works thereof in any medium, with or without + modifications, and in Source or Object form, provided that You + meet the following conditions: + + (a) You must give any other recipients of the Work or + Derivative Works a copy of this License; and + + (b) You must cause any modified files to carry prominent notices + stating that You changed the files; and + + (c) You must retain, in the Source form of any Derivative Works + that You distribute, all copyright, patent, trademark, and + attribution notices from the Source form of the Work, + excluding those notices that do not pertain to any part of + the Derivative Works; and + + (d) If the Work includes a "NOTICE" text file as part of its + distribution, then any Derivative Works that You distribute must + include a readable copy of the attribution notices contained + within such NOTICE file, excluding those notices that do not + pertain to any part of the Derivative Works, in at least one + of the following places: within a NOTICE text file distributed + as part of the Derivative Works; within the Source form or + documentation, if provided along with the Derivative Works; or, + within a display generated by the Derivative Works, if and + wherever such third-party notices normally appear. The contents + of the NOTICE file are for informational purposes only and + do not modify the License. You may add Your own attribution + notices within Derivative Works that You distribute, alongside + or as an addendum to the NOTICE text from the Work, provided + that such additional attribution notices cannot be construed + as modifying the License. + + You may add Your own copyright statement to Your modifications and + may provide additional or different license terms and conditions + for use, reproduction, or distribution of Your modifications, or + for any such Derivative Works as a whole, provided Your use, + reproduction, and distribution of the Work otherwise complies with + the conditions stated in this License. + + 5. Submission of Contributions. Unless You explicitly state otherwise, + any Contribution intentionally submitted for inclusion in the Work + by You to the Licensor shall be under the terms and conditions of + this License, without any additional terms or conditions. + Notwithstanding the above, nothing herein shall supersede or modify + the terms of any separate license agreement you may have executed + with Licensor regarding such Contributions. + + 6. Trademarks. This License does not grant permission to use the trade + names, trademarks, service marks, or product names of the Licensor, + except as required for reasonable and customary use in describing the + origin of the Work and reproducing the content of the NOTICE file. + + 7. Disclaimer of Warranty. Unless required by applicable law or + agreed to in writing, Licensor provides the Work (and each + Contributor provides its Contributions) on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or + implied, including, without limitation, any warranties or conditions + of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A + PARTICULAR PURPOSE. You are solely responsible for determining the + appropriateness of using or redistributing the Work and assume any + risks associated with Your exercise of permissions under this License. + + 8. Limitation of Liability. In no event and under no legal theory, + whether in tort (including negligence), contract, or otherwise, + unless required by applicable law (such as deliberate and grossly + negligent acts) or agreed to in writing, shall any Contributor be + liable to You for damages, including any direct, indirect, special, + incidental, or consequential damages of any character arising as a + result of this License or out of the use or inability to use the + Work (including but not limited to damages for loss of goodwill, + work stoppage, computer failure or malfunction, or any and all + other commercial damages or losses), even if such Contributor + has been advised of the possibility of such damages. + + 9. Accepting Warranty or Additional Liability. While redistributing + the Work or Derivative Works thereof, You may choose to offer, + and charge a fee for, acceptance of support, warranty, indemnity, + or other liability obligations and/or rights consistent with this + License. However, in accepting such obligations, You may act only + on Your own behalf and on Your sole responsibility, not on behalf + of any other Contributor, and only if You agree to indemnify, + defend, and hold each Contributor harmless for any liability + incurred by, or claims asserted against, such Contributor by reason + of your accepting any such warranty or additional liability. + + END OF TERMS AND CONDITIONS + + APPENDIX: How to apply the Apache License to your work. + + To apply the Apache License to your work, attach the following + boilerplate notice, with the fields enclosed by brackets "[]" + replaced with your own identifying information. (Don't include + the brackets!) The text should be enclosed in the appropriate + comment syntax for the file format. We also recommend that a + file or class name and description of purpose be included on the + same "printed page" as the copyright notice for easier + identification within third-party archives. + + Copyright [yyyy] [name of copyright owner] + + Licensed under the Apache License, Version 2.0 (the "License"); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. \ No newline at end of file

15 years, 7 months

1
0
0 / 0

JBoss hornetq SVN: r7819 - in trunk: src/config and 1 other directory.

by do-not-reply＠jboss.org

Author: ataylor Date: 2009-08-20 03:36:14 -0400 (Thu, 20 Aug 2009) New Revision: 7819 Modified: trunk/examples/javaee/jca-config/server2/ra.xml trunk/src/config/ra.xml Log: updated ra files to apache license Modified: trunk/examples/javaee/jca-config/server2/ra.xml =================================================================== --- trunk/examples/javaee/jca-config/server2/ra.xml 2009-08-20 07:34:14 UTC (rev 7818) +++ trunk/examples/javaee/jca-config/server2/ra.xml 2009-08-20 07:36:14 UTC (rev 7819) @@ -19,25 +19,208 @@ <license> <description> - JBoss, Home of Professional Open Source. - Copyright 2009, Red Hat Middleware LLC, and individual contributors - as indicated by the @author tags. See the copyright.txt file in the - distribution for a full listing of individual contributors. - This is free software; you can redistribute it and/or modify it - under the terms of the GNU Lesser General Public License as - published by the Free Software Foundation; either version 2.1 of - the License, or (at your option) any later version. + Apache License + Version 2.0, January 2004 + http://www.apache.org/licenses/ - This software is distributed in the hope that it will be useful, - but WITHOUT ANY WARRANTY; without even the implied warranty of - MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU - Lesser General Public License for more details. + TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION - You should have received a copy of the GNU Lesser General Public - License along with this software; if not, write to the Free - Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA - 02110-1301 USA, or see the FSF site: http://www.fsf.org. + 1. Definitions. + + "License" shall mean the terms and conditions for use, reproduction, + and distribution as defined by Sections 1 through 9 of this document. + + "Licensor" shall mean the copyright owner or entity authorized by + the copyright owner that is granting the License. + + "Legal Entity" shall mean the union of the acting entity and all + other entities that control, are controlled by, or are under common + control with that entity. For the purposes of this definition, + "control" means (i) the power, direct or indirect, to cause the + direction or management of such entity, whether by contract or + otherwise, or (ii) ownership of fifty percent (50%) or more of the + outstanding shares, or (iii) beneficial ownership of such entity. + + "You" (or "Your") shall mean an individual or Legal Entity + exercising permissions granted by this License. + + "Source" form shall mean the preferred form for making modifications, + including but not limited to software source code, documentation + source, and configuration files. + + "Object" form shall mean any form resulting from mechanical + transformation or translation of a Source form, including but + not limited to compiled object code, generated documentation, + and conversions to other media types. + + "Work" shall mean the work of authorship, whether in Source or + Object form, made available under the License, as indicated by a + copyright notice that is included in or attached to the work + (an example is provided in the Appendix below). + + "Derivative Works" shall mean any work, whether in Source or Object + form, that is based on (or derived from) the Work and for which the + editorial revisions, annotations, elaborations, or other modifications + represent, as a whole, an original work of authorship. For the purposes + of this License, Derivative Works shall not include works that remain + separable from, or merely link (or bind by name) to the interfaces of, + the Work and Derivative Works thereof. + + "Contribution" shall mean any work of authorship, including + the original version of the Work and any modifications or additions + to that Work or Derivative Works thereof, that is intentionally + submitted to Licensor for inclusion in the Work by the copyright owner + or by an individual or Legal Entity authorized to submit on behalf of + the copyright owner. For the purposes of this definition, "submitted" + means any form of electronic, verbal, or written communication sent + to the Licensor or its representatives, including but not limited to + communication on electronic mailing lists, source code control systems, + and issue tracking systems that are managed by, or on behalf of, the + Licensor for the purpose of discussing and improving the Work, but + excluding communication that is conspicuously marked or otherwise + designated in writing by the copyright owner as "Not a Contribution." + + "Contributor" shall mean Licensor and any individual or Legal Entity + on behalf of whom a Contribution has been received by Licensor and + subsequently incorporated within the Work. + + 2. Grant of Copyright License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + copyright license to reproduce, prepare Derivative Works of, + publicly display, publicly perform, sublicense, and distribute the + Work and such Derivative Works in Source or Object form. + + 3. Grant of Patent License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + (except as stated in this section) patent license to make, have made, + use, offer to sell, sell, import, and otherwise transfer the Work, + where such license applies only to those patent claims licensable + by such Contributor that are necessarily infringed by their + Contribution(s) alone or by combination of their Contribution(s) + with the Work to which such Contribution(s) was submitted. If You + institute patent litigation against any entity (including a + cross-claim or counterclaim in a lawsuit) alleging that the Work + or a Contribution incorporated within the Work constitutes direct + or contributory patent infringement, then any patent licenses + granted to You under this License for that Work shall terminate + as of the date such litigation is filed. + + 4. Redistribution. You may reproduce and distribute copies of the + Work or Derivative Works thereof in any medium, with or without + modifications, and in Source or Object form, provided that You + meet the following conditions: + + (a) You must give any other recipients of the Work or + Derivative Works a copy of this License; and + + (b) You must cause any modified files to carry prominent notices + stating that You changed the files; and + + (c) You must retain, in the Source form of any Derivative Works + that You distribute, all copyright, patent, trademark, and + attribution notices from the Source form of the Work, + excluding those notices that do not pertain to any part of + the Derivative Works; and + + (d) If the Work includes a "NOTICE" text file as part of its + distribution, then any Derivative Works that You distribute must + include a readable copy of the attribution notices contained + within such NOTICE file, excluding those notices that do not + pertain to any part of the Derivative Works, in at least one + of the following places: within a NOTICE text file distributed + as part of the Derivative Works; within the Source form or + documentation, if provided along with the Derivative Works; or, + within a display generated by the Derivative Works, if and + wherever such third-party notices normally appear. The contents + of the NOTICE file are for informational purposes only and + do not modify the License. You may add Your own attribution + notices within Derivative Works that You distribute, alongside + or as an addendum to the NOTICE text from the Work, provided + that such additional attribution notices cannot be construed + as modifying the License. + + You may add Your own copyright statement to Your modifications and + may provide additional or different license terms and conditions + for use, reproduction, or distribution of Your modifications, or + for any such Derivative Works as a whole, provided Your use, + reproduction, and distribution of the Work otherwise complies with + the conditions stated in this License. + + 5. Submission of Contributions. Unless You explicitly state otherwise, + any Contribution intentionally submitted for inclusion in the Work + by You to the Licensor shall be under the terms and conditions of + this License, without any additional terms or conditions. + Notwithstanding the above, nothing herein shall supersede or modify + the terms of any separate license agreement you may have executed + with Licensor regarding such Contributions. + + 6. Trademarks. This License does not grant permission to use the trade + names, trademarks, service marks, or product names of the Licensor, + except as required for reasonable and customary use in describing the + origin of the Work and reproducing the content of the NOTICE file. + + 7. Disclaimer of Warranty. Unless required by applicable law or + agreed to in writing, Licensor provides the Work (and each + Contributor provides its Contributions) on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or + implied, including, without limitation, any warranties or conditions + of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A + PARTICULAR PURPOSE. You are solely responsible for determining the + appropriateness of using or redistributing the Work and assume any + risks associated with Your exercise of permissions under this License. + + 8. Limitation of Liability. In no event and under no legal theory, + whether in tort (including negligence), contract, or otherwise, + unless required by applicable law (such as deliberate and grossly + negligent acts) or agreed to in writing, shall any Contributor be + liable to You for damages, including any direct, indirect, special, + incidental, or consequential damages of any character arising as a + result of this License or out of the use or inability to use the + Work (including but not limited to damages for loss of goodwill, + work stoppage, computer failure or malfunction, or any and all + other commercial damages or losses), even if such Contributor + has been advised of the possibility of such damages. + + 9. Accepting Warranty or Additional Liability. While redistributing + the Work or Derivative Works thereof, You may choose to offer, + and charge a fee for, acceptance of support, warranty, indemnity, + or other liability obligations and/or rights consistent with this + License. However, in accepting such obligations, You may act only + on Your own behalf and on Your sole responsibility, not on behalf + of any other Contributor, and only if You agree to indemnify, + defend, and hold each Contributor harmless for any liability + incurred by, or claims asserted against, such Contributor by reason + of your accepting any such warranty or additional liability. + + END OF TERMS AND CONDITIONS + + APPENDIX: How to apply the Apache License to your work. + + To apply the Apache License to your work, attach the following + boilerplate notice, with the fields enclosed by brackets "[]" + replaced with your own identifying information. (Don't include + the brackets!) The text should be enclosed in the appropriate + comment syntax for the file format. We also recommend that a + file or class name and description of purpose be included on the + same "printed page" as the copyright notice for easier + identification within third-party archives. + + Copyright [yyyy] [name of copyright owner] + + Licensed under the Apache License, Version 2.0 (the "License"); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. </description> <license-required>true</license-required> </license> Modified: trunk/src/config/ra.xml =================================================================== --- trunk/src/config/ra.xml 2009-08-20 07:34:14 UTC (rev 7818) +++ trunk/src/config/ra.xml 2009-08-20 07:36:14 UTC (rev 7819) @@ -17,25 +17,208 @@ <license> <description> - JBoss, Home of Professional Open Source. - Copyright 2009, Red Hat Middleware LLC, and individual contributors - as indicated by the @author tags. See the copyright.txt file in the - distribution for a full listing of individual contributors. - This is free software; you can redistribute it and/or modify it - under the terms of the GNU Lesser General Public License as - published by the Free Software Foundation; either version 2.1 of - the License, or (at your option) any later version. + Apache License + Version 2.0, January 2004 + http://www.apache.org/licenses/ - This software is distributed in the hope that it will be useful, - but WITHOUT ANY WARRANTY; without even the implied warranty of - MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU - Lesser General Public License for more details. + TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION - You should have received a copy of the GNU Lesser General Public - License along with this software; if not, write to the Free - Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA - 02110-1301 USA, or see the FSF site: http://www.fsf.org. + 1. Definitions. + + "License" shall mean the terms and conditions for use, reproduction, + and distribution as defined by Sections 1 through 9 of this document. + + "Licensor" shall mean the copyright owner or entity authorized by + the copyright owner that is granting the License. + + "Legal Entity" shall mean the union of the acting entity and all + other entities that control, are controlled by, or are under common + control with that entity. For the purposes of this definition, + "control" means (i) the power, direct or indirect, to cause the + direction or management of such entity, whether by contract or + otherwise, or (ii) ownership of fifty percent (50%) or more of the + outstanding shares, or (iii) beneficial ownership of such entity. + + "You" (or "Your") shall mean an individual or Legal Entity + exercising permissions granted by this License. + + "Source" form shall mean the preferred form for making modifications, + including but not limited to software source code, documentation + source, and configuration files. + + "Object" form shall mean any form resulting from mechanical + transformation or translation of a Source form, including but + not limited to compiled object code, generated documentation, + and conversions to other media types. + + "Work" shall mean the work of authorship, whether in Source or + Object form, made available under the License, as indicated by a + copyright notice that is included in or attached to the work + (an example is provided in the Appendix below). + + "Derivative Works" shall mean any work, whether in Source or Object + form, that is based on (or derived from) the Work and for which the + editorial revisions, annotations, elaborations, or other modifications + represent, as a whole, an original work of authorship. For the purposes + of this License, Derivative Works shall not include works that remain + separable from, or merely link (or bind by name) to the interfaces of, + the Work and Derivative Works thereof. + + "Contribution" shall mean any work of authorship, including + the original version of the Work and any modifications or additions + to that Work or Derivative Works thereof, that is intentionally + submitted to Licensor for inclusion in the Work by the copyright owner + or by an individual or Legal Entity authorized to submit on behalf of + the copyright owner. For the purposes of this definition, "submitted" + means any form of electronic, verbal, or written communication sent + to the Licensor or its representatives, including but not limited to + communication on electronic mailing lists, source code control systems, + and issue tracking systems that are managed by, or on behalf of, the + Licensor for the purpose of discussing and improving the Work, but + excluding communication that is conspicuously marked or otherwise + designated in writing by the copyright owner as "Not a Contribution." + + "Contributor" shall mean Licensor and any individual or Legal Entity + on behalf of whom a Contribution has been received by Licensor and + subsequently incorporated within the Work. + + 2. Grant of Copyright License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + copyright license to reproduce, prepare Derivative Works of, + publicly display, publicly perform, sublicense, and distribute the + Work and such Derivative Works in Source or Object form. + + 3. Grant of Patent License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + (except as stated in this section) patent license to make, have made, + use, offer to sell, sell, import, and otherwise transfer the Work, + where such license applies only to those patent claims licensable + by such Contributor that are necessarily infringed by their + Contribution(s) alone or by combination of their Contribution(s) + with the Work to which such Contribution(s) was submitted. If You + institute patent litigation against any entity (including a + cross-claim or counterclaim in a lawsuit) alleging that the Work + or a Contribution incorporated within the Work constitutes direct + or contributory patent infringement, then any patent licenses + granted to You under this License for that Work shall terminate + as of the date such litigation is filed. + + 4. Redistribution. You may reproduce and distribute copies of the + Work or Derivative Works thereof in any medium, with or without + modifications, and in Source or Object form, provided that You + meet the following conditions: + + (a) You must give any other recipients of the Work or + Derivative Works a copy of this License; and + + (b) You must cause any modified files to carry prominent notices + stating that You changed the files; and + + (c) You must retain, in the Source form of any Derivative Works + that You distribute, all copyright, patent, trademark, and + attribution notices from the Source form of the Work, + excluding those notices that do not pertain to any part of + the Derivative Works; and + + (d) If the Work includes a "NOTICE" text file as part of its + distribution, then any Derivative Works that You distribute must + include a readable copy of the attribution notices contained + within such NOTICE file, excluding those notices that do not + pertain to any part of the Derivative Works, in at least one + of the following places: within a NOTICE text file distributed + as part of the Derivative Works; within the Source form or + documentation, if provided along with the Derivative Works; or, + within a display generated by the Derivative Works, if and + wherever such third-party notices normally appear. The contents + of the NOTICE file are for informational purposes only and + do not modify the License. You may add Your own attribution + notices within Derivative Works that You distribute, alongside + or as an addendum to the NOTICE text from the Work, provided + that such additional attribution notices cannot be construed + as modifying the License. + + You may add Your own copyright statement to Your modifications and + may provide additional or different license terms and conditions + for use, reproduction, or distribution of Your modifications, or + for any such Derivative Works as a whole, provided Your use, + reproduction, and distribution of the Work otherwise complies with + the conditions stated in this License. + + 5. Submission of Contributions. Unless You explicitly state otherwise, + any Contribution intentionally submitted for inclusion in the Work + by You to the Licensor shall be under the terms and conditions of + this License, without any additional terms or conditions. + Notwithstanding the above, nothing herein shall supersede or modify + the terms of any separate license agreement you may have executed + with Licensor regarding such Contributions. + + 6. Trademarks. This License does not grant permission to use the trade + names, trademarks, service marks, or product names of the Licensor, + except as required for reasonable and customary use in describing the + origin of the Work and reproducing the content of the NOTICE file. + + 7. Disclaimer of Warranty. Unless required by applicable law or + agreed to in writing, Licensor provides the Work (and each + Contributor provides its Contributions) on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or + implied, including, without limitation, any warranties or conditions + of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A + PARTICULAR PURPOSE. You are solely responsible for determining the + appropriateness of using or redistributing the Work and assume any + risks associated with Your exercise of permissions under this License. + + 8. Limitation of Liability. In no event and under no legal theory, + whether in tort (including negligence), contract, or otherwise, + unless required by applicable law (such as deliberate and grossly + negligent acts) or agreed to in writing, shall any Contributor be + liable to You for damages, including any direct, indirect, special, + incidental, or consequential damages of any character arising as a + result of this License or out of the use or inability to use the + Work (including but not limited to damages for loss of goodwill, + work stoppage, computer failure or malfunction, or any and all + other commercial damages or losses), even if such Contributor + has been advised of the possibility of such damages. + + 9. Accepting Warranty or Additional Liability. While redistributing + the Work or Derivative Works thereof, You may choose to offer, + and charge a fee for, acceptance of support, warranty, indemnity, + or other liability obligations and/or rights consistent with this + License. However, in accepting such obligations, You may act only + on Your own behalf and on Your sole responsibility, not on behalf + of any other Contributor, and only if You agree to indemnify, + defend, and hold each Contributor harmless for any liability + incurred by, or claims asserted against, such Contributor by reason + of your accepting any such warranty or additional liability. + + END OF TERMS AND CONDITIONS + + APPENDIX: How to apply the Apache License to your work. + + To apply the Apache License to your work, attach the following + boilerplate notice, with the fields enclosed by brackets "[]" + replaced with your own identifying information. (Don't include + the brackets!) The text should be enclosed in the appropriate + comment syntax for the file format. We also recommend that a + file or class name and description of purpose be included on the + same "printed page" as the copyright notice for easier + identification within third-party archives. + + Copyright [yyyy] [name of copyright owner] + + Licensed under the Apache License, Version 2.0 (the "License"); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. </description> <license-required>true</license-required> </license>

15 years, 7 months

1
0
0 / 0

JBoss hornetq SVN: r7816 - trunk.

by do-not-reply＠jboss.org

Author: clebert.suconic(a)jboss.com Date: 2009-08-20 02:05:30 -0400 (Thu, 20 Aug 2009) New Revision: 7816 Modified: trunk/build-hornetq.xml Log: "fixing" exclude lists Modified: trunk/build-hornetq.xml =================================================================== --- trunk/build-hornetq.xml 2009-08-20 05:58:43 UTC (rev 7815) +++ trunk/build-hornetq.xml 2009-08-20 06:05:30 UTC (rev 7816) @@ -1193,8 +1193,10 @@ <fileset dir="${test.jms.classes.dir}"> <include name="**/jmstests/**/${test-mask}.class"/> <exclude name="**/jmstests/XARecoveryTest.class"/> - <exclude name="**/jms/XAResourceRecoveryTest.class"/> - <exclude name="**/jms/XATest.class"/> + <exclude name="**/jmstests/XAResourceRecoveryTest.class"/> + <exclude name="**/jmstests/XATest.class"/> + <exclude name="**/jmstests/stress/**"/> + <exclude name="**/jmstests/manual/**"/> </fileset> </batchtest> </junit>

15 years, 7 months

1
0
0 / 0

JBoss hornetq SVN: r7815 - trunk.

by do-not-reply＠jboss.org

Author: clebert.suconic(a)jboss.com Date: 2009-08-20 01:58:43 -0400 (Thu, 20 Aug 2009) New Revision: 7815 Modified: trunk/ Log: svn:ignore Property changes on: trunk ___________________________________________________________________ Name: svn:ignore - build eclipse-output thirdparty logs ObjectStore tmp data + build eclipse-output thirdparty logs ObjectStore tmp data junit*.properties

15 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

hornetq-commits August 2009