[jboss-cvs] JBoss Messaging SVN: r6896 - in trunk/docs/user-manual: en and 1 other directories.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Tue May 19 13:15:23 EDT 2009
Author: timfox
Date: 2009-05-19 13:15:23 -0400 (Tue, 19 May 2009)
New Revision: 6896
Added:
trunk/docs/user-manual/en/modules/project-info.xml
Modified:
trunk/docs/user-manual/en/master.xml
trunk/docs/user-manual/en/modules/configuring-transports.xml
trunk/docs/user-manual/en/modules/using-core.xml
trunk/docs/user-manual/user-manual.xpr
Log:
project info
Modified: trunk/docs/user-manual/en/master.xml
===================================================================
--- trunk/docs/user-manual/en/master.xml 2009-05-19 17:00:38 UTC (rev 6895)
+++ trunk/docs/user-manual/en/master.xml 2009-05-19 17:15:23 UTC (rev 6896)
@@ -32,6 +32,7 @@
<!ENTITY persistence SYSTEM "modules/persistence.xml">
<!ENTITY pre-acknowledge SYSTEM "modules/pre-acknowledge.xml">
<!ENTITY preface SYSTEM "modules/preface.xml">
+ <!ENTITY project-info SYSTEM "modules/project-info.xml">
<!ENTITY queue-attributes SYSTEM "modules/queue-attributes.xml">
<!ENTITY scheduled-messages SYSTEM "modules/scheduled-messages.xml">
<!ENTITY security SYSTEM "modules/security.xml">
@@ -41,7 +42,7 @@
<!ENTITY using-core SYSTEM "modules/using-core.xml">
<!ENTITY using-jms SYSTEM "modules/using-jms.xml">
<!ENTITY using-server SYSTEM "modules/using-server.xml">
- <!ENTITY wildcard-syntax SYSTEM "modules/wildcard-syntax.xml">
+ <!ENTITY wildcard-syntax SYSTEM "modules/wildcard-syntax.xml">
]>
<book lang="en">
<bookinfo>
@@ -92,5 +93,6 @@
&interoperability;
&perf-tuning;
&configuration-index;
+ &project-info;
</book>
Modified: trunk/docs/user-manual/en/modules/configuring-transports.xml
===================================================================
--- trunk/docs/user-manual/en/modules/configuring-transports.xml 2009-05-19 17:00:38 UTC (rev 6895)
+++ trunk/docs/user-manual/en/modules/configuring-transports.xml 2009-05-19 17:15:23 UTC (rev 6896)
@@ -386,7 +386,7 @@
</itemizedlist>
<para>The servlet pattern configured in the <literal>web.xml</literal> is the path of
the URL that is used. The connector param <literal
- >jbm.remoting.netty.servletpath</literal> on the connector config must match
+ >jbm.remoting.netty.servletpath</literal> on the connector config must match
this using the application context of the web app if there is one.</para>
</section>
</section>
Added: trunk/docs/user-manual/en/modules/project-info.xml
===================================================================
--- trunk/docs/user-manual/en/modules/project-info.xml (rev 0)
+++ trunk/docs/user-manual/en/modules/project-info.xml 2009-05-19 17:15:23 UTC (rev 6896)
@@ -0,0 +1,17 @@
+<?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/"
+ >here</ulink>. You can download any releases from there.</para>
+ <para>If you have any user questions please use our <ulink
+ url="http://www.jboss.org/index.html?module=bb&op=viewforum&f=238">user
+ forum</ulink></para>
+ <para>If you have development related questions, please use our <ulink
+ url="http://www.jboss.org/index.html?module=bb&op=viewforum&f=153">development
+ forum</ulink></para>
+ <para>Pop in and chat to us in our <ulink url="irc://irc.freenode.net:6667/jbossmessaging">IRC channel</ulink></para>
+ <para>JBoss Messaging svn TRUNK is <ulink url="http://anonsvn.jboss.org/repos/messaging/trunk">here</ulink></para>
+ <para>All our release tags are <ulink url="http://anonsvn.jboss.org/repos/messaging/tags">here</ulink></para>
+ <para>The JBoss Messaging permanent dev team is <ulink url="jbossfox.blogspot.com">Tim Fox</ulink>, Howard Gao, Jeff Mesnil, Clebert
+ Suconic, and Andy Taylor</para>
+</chapter>
Modified: trunk/docs/user-manual/en/modules/using-core.xml
===================================================================
--- trunk/docs/user-manual/en/modules/using-core.xml 2009-05-19 17:00:38 UTC (rev 6895)
+++ trunk/docs/user-manual/en/modules/using-core.xml 2009-05-19 17:15:23 UTC (rev 6896)
@@ -1,47 +1,80 @@
<?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 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 complications. It also provides features that are not normally available using JMS.</para>
+ <para>JBoss Messaging 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 complications. It also provides features
+ that are not normally available using JMS.</para>
<section>
<title>Core Messaging Concepts</title>
- <para>Some of the core messaging concepts are similar to JMS concepts, but Core messaging concepts differ in some ways.</para>
- <para>In core, there is no concept of a Topic, Topic is a JMS only term. Instead, in core, we just deal with <emphasis>addresses</emphasis>
- and <emphasis>queues</emphasis>.</para>
- <para>Queues can de durable, meaning they survive a server crash or restart, as long as the messages in them are durable. Non durable queues
- do not survive a server restart or crash even if the messages they contain are durable.</para>
- <para>Queues can also be temporary, meaning they are automatically deleted when the client connection is closed, if they are not explicitly
- deleted before that.</para>
- <para>Messages can durable or non durable. Durable messages in a durable queue will survive a server crash or restart. Non durable messages
- will never survive a server crash or restart.</para>
- <para>Clients use <literal>ClientSessionFactory</literal> instances to create <literal>ClientSession</literal> instances. <literal>ClientSessionFactory</literal>
- instances know how to connect to the server to create sessions.</para>
- <para>Clients create <literal>ClientProducer</literal> instances on <literal>ClientSession</literal> instances so they can send
- messages.</para>
- <para>Messages are sent to <literal>addresses</literal>. When the message arrives on the server the server routes it to zero or more
- queues depending on the address. Many queues can be bound to a particular address on the server. The server will route the message
- to all queues bound to that address.</para>
- <para>For example, a JMS topic would implemented by a single address to which many queues are bound. Each queue represents a subscription of the topic. A JMS
- Queue would be implemented as a single address to which one queue is bound - that queue represents the JMS queue.</para>
- <para>Queues can be bound with an optional filter expression. If a filter expression is supplied then the server will only route messages
- who match that filter expression to any queues bound to the address.</para>
- <para>Clients use <literal>ClientConsumer</literal> instances to consume messages from a queue. Core Messaging supports both synchronous
- and asynchronous message consumption semantics. <literal>ClientConsumer</literal> instances can be configured with an optional
- filter expression and will only consume messages which match that expression.</para>
- <para>Core Messaging also fully supports both local and XA transactional semantics.</para>
- <para>TODO insert diagram showing core routing queue and addresses</para>
+ <para>Some of the core messaging concepts are similar to JMS concepts, but Core messaging
+ concepts differ in some ways. In general the core messaging API is simply than the JMS
+ API, since we remove distinctions between queues, topics and subscriptions. We'll
+ discuss each of the major core messaging concepts in turn:</para>
+ <section>
+ <title>Message</title>
+ <para>Messages are sent to <literal>addresses</literal>. When the message arrives on the
+ server the server routes it to zero or more queues depending on the address. Many
+ queues can be bound to a particular address on the server. The server will route the
+ message to all queues bound to that address.</para>
+ <para>Messages can durable or non durable. Durable messages in a durable queue will
+ survive a server crash or restart. Non durable messages will never survive a server
+ crash or restart.</para>
+ </section>
+ <section>
+ <title>Address</title>
+ <para>In core, there is no concept of a Topic, Topic is a JMS only term. Instead, in
+ core, we just deal with <emphasis>addresses</emphasis> and
+ <emphasis>queues</emphasis>.</para>
+ <para>For example, a JMS topic would implemented by a single address to which many
+ queues are bound. Each queue represents a subscription of the topic. A JMS Queue
+ would be implemented as a single address to which one queue is bound - that queue
+ represents the JMS queue.</para>
+ </section>
+ <section>
+ <title>Queue</title>
+ <para>Queues can de durable, meaning they survive a server crash or restart, as long as
+ the messages in them are durable. Non durable queues do not survive a server restart
+ or crash even if the messages they contain are durable.</para>
+ <para>Queues can also be temporary, meaning they are automatically deleted when the
+ client connection is closed, if they are not explicitly deleted before that.</para>
+ <para>Queues can be bound with an optional filter expression. If a filter expression is
+ supplied then the server will only route messages who match that filter expression
+ to any queues bound to the address.</para>
+ </section>
+ <section>
+ <title>ClientSessionFactory</title>
+ <para>Clients use <literal>ClientSessionFactory</literal> instances to create <literal
+ >ClientSession</literal> instances. <literal>ClientSessionFactory</literal>
+ instances know how to connect to the server to create sessions.</para>
+ </section>
+ <section>
+ <title>ClientSession</title>
+ <para>blah blah blah</para>
+ <para>ClientSession also fully supports both local and XA transactional
+ semantics.</para>
+ </section>
+ <section>
+ <title>ClientConsumer</title>
+ <para>Clients use <literal>ClientConsumer</literal> instances to consume messages from a
+ queue. Core Messaging supports both synchronous and asynchronous message consumption
+ semantics. <literal>ClientConsumer</literal> instances can be configured with an
+ optional filter expression and will only consume messages which match that
+ expression.</para>
+ </section>
+ <section>
+ <title>ClientProducer</title>
+ <para>Clients create <literal>ClientProducer</literal> instances on <literal
+ >ClientSession</literal> instances so they can send messages.</para>
+ </section>
</section>
<section>
<title>A simple example of using Core</title>
- <para></para>
+ <para/>
</section>
<section>
<title>Core transactions</title>
- <para></para>
+ <para/>
</section>
-
-
-
-
</chapter>
Modified: trunk/docs/user-manual/user-manual.xpr
===================================================================
--- trunk/docs/user-manual/user-manual.xpr 2009-05-19 17:00:38 UTC (rev 6895)
+++ trunk/docs/user-manual/user-manual.xpr 2009-05-19 17:15:23 UTC (rev 6896)
@@ -39,9 +39,11 @@
<file name="en/modules/persistence.xml"/>
<file name="en/modules/pre-acknowledge.xml"/>
<file name="en/modules/preface.xml"/>
+ <file name="en/modules/project-info.xml"/>
<file name="en/modules/queue-attributes.xml"/>
<file name="en/modules/scheduled-messages.xml"/>
<file name="en/modules/security.xml"/>
+ <file name="en/modules/send-guarantees.xml"/>
<file name="en/modules/thread-pooling.xml"/>
<file name="en/modules/undelivered-messages.xml"/>
<file name="en/modules/using-core.xml"/>
More information about the jboss-cvs-commits
mailing list