[jboss-cvs] JBoss Messaging SVN: r6785 - in trunk/docs/user-manual/en: modules and 1 other directory.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Thu May 14 05:35:28 EDT 2009
Author: jmesnil
Date: 2009-05-14 05:35:28 -0400 (Thu, 14 May 2009)
New Revision: 6785
Added:
trunk/docs/user-manual/en/modules/jms-core-mapping.xml
Modified:
trunk/docs/user-manual/en/master.xml
trunk/docs/user-manual/en/modules/security.xml
Log:
user manual
* moved section about JMS to Core mapping from security chapter to
the jms-core-mapping chapter
Modified: trunk/docs/user-manual/en/master.xml
===================================================================
--- trunk/docs/user-manual/en/master.xml 2009-05-14 09:34:28 UTC (rev 6784)
+++ trunk/docs/user-manual/en/master.xml 2009-05-14 09:35:28 UTC (rev 6785)
@@ -7,6 +7,7 @@
<!ENTITY using-server SYSTEM "modules/using-server.xml">
<!ENTITY using-jms SYSTEM "modules/using-jms.xml">
<!ENTITY using-core SYSTEM "modules/using-core.xml">
+ <!ENTITY jms-core-mapping SYSTEM "modules/jms-core-mapping.xml">
<!ENTITY embedding-jbm SYSTEM "modules/embedding-jbm.xml">
<!ENTITY security SYSTEM "modules/security.xml">
<!ENTITY wildcard-syntax SYSTEM "modules/wildcard-syntax.xml">
@@ -54,6 +55,7 @@
&using-server;
&using-jms;
&using-core;
+ &jms-core-mapping;
&embedding-jbm;
&security;
&wildcard-syntax;
Added: trunk/docs/user-manual/en/modules/jms-core-mapping.xml
===================================================================
--- trunk/docs/user-manual/en/modules/jms-core-mapping.xml (rev 0)
+++ trunk/docs/user-manual/en/modules/jms-core-mapping.xml 2009-05-14 09:35:28 UTC (rev 6785)
@@ -0,0 +1,33 @@
+<?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" -->
+ <address-setting match="jms.queue.orders.europe">
+ <expiry-address>jms.queue.expiry.europe</expiry-address>
+ ...
+ </address-setting>
+ </programlisting>
+</chapter>
Modified: trunk/docs/user-manual/en/modules/security.xml
===================================================================
--- trunk/docs/user-manual/en/modules/security.xml 2009-05-14 09:34:28 UTC (rev 6784)
+++ trunk/docs/user-manual/en/modules/security.xml 2009-05-14 09:35:28 UTC (rev 6785)
@@ -11,24 +11,6 @@
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 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. A JMS
- Queue is implemented as an address (the JMS Queue name) with one 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 aty 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>JBoss Messaging 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>
More information about the jboss-cvs-commits
mailing list