[jboss-cvs] JBoss Messaging SVN: r6860 - trunk/docs/user-manual/en/modules.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Mon May 18 19:33:37 EDT 2009
Author: clebert.suconic at jboss.com
Date: 2009-05-18 19:33:37 -0400 (Mon, 18 May 2009)
New Revision: 6860
Modified:
trunk/docs/user-manual/en/modules/embedding-jbm.xml
trunk/docs/user-manual/en/modules/jms-core-mapping.xml
trunk/docs/user-manual/en/modules/paging.xml
Log:
just tweaks
Modified: trunk/docs/user-manual/en/modules/embedding-jbm.xml
===================================================================
--- trunk/docs/user-manual/en/modules/embedding-jbm.xml 2009-05-18 22:56:32 UTC (rev 6859)
+++ trunk/docs/user-manual/en/modules/embedding-jbm.xml 2009-05-18 23:33:37 UTC (rev 6860)
@@ -9,8 +9,8 @@
<section>
<title>POJO instantiation</title>
<para>You can follow this step-by-step guide:</para>
- <para>Create the configuration object. If you need a configuration file, use
- FileConfigurationImpl</para>
+ <para>Create the configuration object. If you need a configuration file, use <literal
+ >FileConfigurationImpl</literal></para>
<programlisting>import org.jboss.messaging.core.config.Configuration;
import org.jboss.messaging.core.config.impl.FileConfiguration;
@@ -24,8 +24,8 @@
>ConfigurationImpl</literal> and change the config parameters accordingly, such as
adding acceptors. </para>
<para>The acceptors are configured through <literal>ConfigurationImpl</literal>. Just add
- the NettyAcceptorFactory on the transports the same way you would thorugh the main
- configuration file.</para>
+ the <literal>NettyAcceptorFactory</literal> on the transports the same way you would
+ through the main configuration file.</para>
<programlisting>import org.jboss.messaging.core.config.Configuration;
import org.jboss.messaging.core.config.impl.ConfigurationImpl;
@@ -70,16 +70,16 @@
required to instantiate a Server:</para>
<itemizedlist>
<listitem>
- <para>The configuration. We will use ConfigurationImpl</para>
+ <para>The configuration. We will use <literal>ConfigurationImpl</literal></para>
</listitem>
<listitem>
- <para>A MBeanServer required by management.</para>
+ <para>A <literal>MBeanServer</literal> required by management.</para>
</listitem>
<listitem>
- <para>The Security Manager</para>
+ <para>The security manager</para>
</listitem>
<listitem>
- <para>And the Messaging Server itself.</para>
+ <para>And the messaging server itself.</para>
</listitem>
</itemizedlist>
<para>A very basic XML Bean declaration for the JBoss Micro Container would be:</para>
@@ -105,7 +105,8 @@
</bean>
<!-- The core server -->
- <bean name="MessagingServer" class="org.jboss.messaging.core.server.impl.MessagingServerImpl">
+ <bean name="MessagingServer"
+ class="org.jboss.messaging.core.server.impl.MessagingServerImpl">
<start ignored="true"/>
<stop ignored="true"/>
<constructor>
@@ -127,7 +128,7 @@
bootStrap.run();</programlisting>
</section>
<section>
- <title>Connecting to the Embedeed JBoss Messaging</title>
+ <title>Connecting to the Embedded JBoss Messaging</title>
<para>There is no special requirement on connecting to an Embedded JBoss Messaging. As you
are managing POJOs directly you just instantiate the factories.</para>
<section>
@@ -135,7 +136,9 @@
<para>If using the core API, just create the <literal>ClientSessionFactory</literal> and
use the regular core API.</para>
<programlisting>ClientSessionFactory nettyFactory = new ClientSessionFactoryImpl(
- new TransportConfiguration(InVMConnectorFactory.class.getName()), null);
+ new TransportConfiguration(
+ InVMConnectorFactory.class.getName()), null);
+
ClientSession session = factory.createSession(false, true, true);
session.createQueue("example", "example", true);
@@ -160,7 +163,7 @@
<title>JMS API</title>
<para>Connection on an Embedded JBoss Messaging through JMS is also simple. Just
instantiate <literal>JBossConnectionFactory</literal> directly. The following
- example ilustrates that.</para>
+ example illustrates that.</para>
<programlisting>JBossConnectionFactory cf = new JBossConnectionFactory(
new TransportConfiguration(InVMConnectorFactory.class.getName()));
@@ -190,4 +193,10 @@
</programlisting>
</section>
</section>
+ <section>
+ <title>Embedding Example</title>
+ <para>The <ulink url="../../../../examples/jms/embedded/readme.html"><literal
+ >Embedding</literal> Example</ulink> shows how to setup and run JBoss Messaging
+ embedded..</para>
+ </section>
</chapter>
Modified: trunk/docs/user-manual/en/modules/jms-core-mapping.xml
===================================================================
--- trunk/docs/user-manual/en/modules/jms-core-mapping.xml 2009-05-18 22:56:32 UTC (rev 6859)
+++ trunk/docs/user-manual/en/modules/jms-core-mapping.xml 2009-05-18 23:33:37 UTC (rev 6860)
@@ -1,30 +1,29 @@
<?xml version="1.0" encoding="UTF-8"?>
<chapter id="jms-core-mapping">
<title>Mapping JMS to Core API</title>
- <para>This chapter describes how JMS destinations are mapped to JBoss Messaging Core resources</para>
-
- <para>JBoss Messaging 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 which represents the JMS Queue.</para>
- <para>By convention, all JMS Queues map to core queues where the core queue name has the
- string <literal>jms.queue.</literal> prepended to it. E.g. the JMS Queue with the name
- "orders.europe" would map to the core queue with the name "jms.queue.orders.europe". The
- address at which the core queue is bound is also given by the core queue name.</para>
- <para>For JMS Topics the address at which the queues that represent the subscriptions are
- bound is given by prepending the string "jms.topic." to the name of the JMS Topic. E.g.
- the JMS Topic with name "news.europe" would map to the core address
- "jms.topic.news.europe"</para>
- <para>In other words if you send a JMS Message to a JMS Queue with name "orders.europe" it
- will get routed on the server to any core queues bound to the address
- "jms.queue.orders.europe". If you send a JMS Message to a JMS Topic with name
- "news.europe" it will get routed on the server to any core queues bound to the address
- "jms.topic.news.europe".</para>
- <para>If you want to configure settings for a JMS Queue with the name "orders.europe",
- you need to configure the corresponding core queue "jms.queue.orders.europe":</para>
- <programlisting>
- <!-- expired messages in JMS Queue "orders.europe" will be sent to the JMS Queue "expiry.europe" -->
+ <para>This chapter describes how JMS destinations are mapped to JBoss Messaging Core
+ resources</para>
+ <para>JBoss Messaging 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
+ which represents the JMS Queue.</para>
+ <para>By convention, all JMS Queues map to core queues where the core queue name has the string
+ <literal>jms.queue.</literal> prepended to it. E.g. the JMS Queue with the name
+ "orders.europe" would map to the core queue with the name "jms.queue.orders.europe". The
+ address at which the core queue is bound is also given by the core queue name.</para>
+ <para>For JMS Topics the address at which the queues that represent the subscriptions are bound
+ is given by prepending the string "jms.topic." to the name of the JMS Topic. E.g. the JMS
+ Topic with name "news.europe" would map to the core address "jms.topic.news.europe"</para>
+ <para>In other words if you send a JMS Message to a JMS Queue with name "orders.europe" it will
+ get routed on the server to any core queues bound to the address "jms.queue.orders.europe".
+ If you send a JMS Message to a JMS Topic with name "news.europe" it will get routed on the
+ server to any core queues bound to the address "jms.topic.news.europe".</para>
+ <para>If you want to configure settings for a JMS Queue with the name "orders.europe", you need
+ to configure the corresponding core queue "jms.queue.orders.europe":</para>
+ <programlisting>
+ <!-- expired messages in JMS Queue "orders.europe"
+ will be sent to the JMS Queue "expiry.europe" -->
<address-setting match="jms.queue.orders.europe">
<expiry-address>jms.queue.expiry.europe</expiry-address>
...
Modified: trunk/docs/user-manual/en/modules/paging.xml
===================================================================
--- trunk/docs/user-manual/en/modules/paging.xml 2009-05-18 22:56:32 UTC (rev 6859)
+++ trunk/docs/user-manual/en/modules/paging.xml 2009-05-18 23:33:37 UTC (rev 6860)
@@ -162,4 +162,11 @@
the Address enters in page mode, messages will be stored on disk and not routed to
queues until messages are consumed on that queue.</para>
</section>
+
+ <section>
+ <title>Paging Example</title>
+ <para>The <ulink url="../../../../examples/jms/paging/readme.html"><literal
+ >Paging</literal> Example</ulink> shows how to JBoss Messaging avoids running out of memory.</para>
+ </section>
+
</chapter>
More information about the jboss-cvs-commits
mailing list