[jboss-cvs] JBoss Messaging SVN: r4355 - in trunk: docs/userguide/en/modules and 1 other directory.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Fri May 30 14:36:56 EDT 2008
Author: timfox
Date: 2008-05-30 14:36:56 -0400 (Fri, 30 May 2008)
New Revision: 4355
Modified:
trunk/build.xml
trunk/docs/userguide/en/modules/about.xml
trunk/docs/userguide/en/modules/introduction.xml
Log:
Docs changes
Modified: trunk/build.xml
===================================================================
--- trunk/build.xml 2008-05-30 17:19:44 UTC (rev 4354)
+++ trunk/build.xml 2008-05-30 18:36:56 UTC (rev 4355)
@@ -77,6 +77,10 @@
<target name="build-native" depends="createthirdparty">
<ant antfile="build-messaging.xml" target="build-native"/>
</target>
+
+ <target name="userdoc">
+ <ant antfile="build-messaging.xml" target="userdoc"/>
+ </target>
<!-- ======================================================================================== -->
<!-- Archival Tasks -->
<!-- ======================================================================================== -->
Modified: trunk/docs/userguide/en/modules/about.xml
===================================================================
--- trunk/docs/userguide/en/modules/about.xml 2008-05-30 17:19:44 UTC (rev 4354)
+++ trunk/docs/userguide/en/modules/about.xml 2008-05-30 18:36:56 UTC (rev 4355)
@@ -1,34 +1,17 @@
<?xml version="1.0" encoding="UTF-8"?>
<chapter id="about">
- <title>About JBoss Messaging 2.0.0</title>
- <para>JBoss Messaging 2 is the next level of messaging system being developed by JBoss,
- designed to attend very large demanding systems with the emphasis on making JBM the most efficient Messaging
- System written in Java available
- on the market.
+ <title>About JBoss Messaging 2.0</title>
+ <para>JBoss Messaging 2.0 is the new generation of JBoss' flagship messaging project</para>
+ <para>JBM 2.0's elegant new POJO-based design and re-factored core allows it to run in JBoss Micro-container as well as being embeddable in your own applications. It also contains a new optimised persistence model that removes the database as a point of contention in the architecture and promises lightning-fast scalable persistence while retaining high availability.
+ We also have a completely new NIO based transport using Apache MINA.</para>
+ <para> The goal of JBM 2.0 is simple and uncompromising- to bring unrivalled levels of performance and reliability to messaging, and to
+ become the fastest, best featured and most scalable messaging system in the open source space</para>
+ <para>But enough marketing rhetoric!. We are not in the business of making empty statements with respect to performance so we ship this release with a set of basic performance measurements against competing messaging systems in the open source space, so you can decide for yourslef. All performance results are fully reproducible by you, using the tools shipped with this distribution.
</para>
- <para>JBoss Messaging 1.4 has been the default implementation on JBoss Service Integration Platform and JBoss 5 for
- some time already.
- </para>
- <para>JBoss Messaging is an integral part of Red Hat's strategy for
- messaging.
- </para>
<para>The procedure of installing and configuring JBoss Messaging is detailed in this guide, along with a set of
- runnable examples.
+ runnable examples. This guide will be extended, before the general availability release of JBoss Messaging 2.0
</para>
- <para>Please send your suggestions or comments to the<ulink
- url="http://www.jboss.org/index.html?module=bb&op=viewforum&f=238">JBoss
- Messaging user forum</ulink>.
- </para>
- <para>Permanent Team: Tim Fox (Project Lead), Jeff Mesnil (Core Developer),
+ <para>Team: Tim Fox (Project Lead), Jeff Mesnil (Core Developer),
Andy Taylor (Core Developer), Clebert Suconic (Core Developer)
</para>
- <para>Contributors: Ovidiu Feodorov (Project Founder), Sergey Koshcheyev,
- Ron Sigal, Madhu Konda, Jay Howell, Tyronne Wickramarathne, Aaron Walker,
- Adrian Brock, Rajdeep Dua, Tom Elrod, Alex Fu, Juha Lindfors, Alexey
- Loubyansky, Luc Texier, Scott Stark, Aslak Knutsen
- </para>
- <para>Messaging support team: Jay Howell, David Boeren, Tyronne
- Wickramarathne
- </para>
- <para>Other thanks to: Mark Little and Pete Bennett</para>
</chapter>
\ No newline at end of file
Modified: trunk/docs/userguide/en/modules/introduction.xml
===================================================================
--- trunk/docs/userguide/en/modules/introduction.xml 2008-05-30 17:19:44 UTC (rev 4354)
+++ trunk/docs/userguide/en/modules/introduction.xml 2008-05-30 18:36:56 UTC (rev 4355)
@@ -2,10 +2,10 @@
<chapter id="introduction">
<title>Introduction</title>
- <para>JBoss Messaging provides an open source and standard-based messaging
+ <para>JBoss Messaging 2.0 provides an open source and standard-based messaging
platform that brings enterprise-class messaging to the mass market.</para>
- <para>JBoss Messaging implements a high performance, robust messaging core
+ <para>JBoss Messaging 2.0 implements a high performance, robust messaging core
that is designed to support the largest and most heavily utilized SOAs,
enterprise service buses (ESBs) and other integration needs ranging from
the simplest to the highest demand networks.</para>
@@ -19,206 +19,45 @@
standard-based format. It is also designed to be able to support
other messaging protocols in the future.</para>
-
- <para>Currently JBM 2.0 is only available standalone or embedded, the current JBoss AS 5 release contains JBM 1.4.2.</para>
-
-
- <!-- <section id="support">
- <title>JBoss Messaging support cover from Red Hat</title>
-
- <para>JBoss Messaging is destined to become part of both Application
- Server Platform and Service Integration Platform as default JMS
- provider.Production support will then be fully available for these
- plaforms and it will cover JBoss Messaging.</para>
-
- <para>There is a currently an early adopters program where production
- support is given for JBoss Messaging. Applications are considered on a
- case-by-case basis.</para>
-
- <para>Currently developer support is generally available for JBoss
- Messaging when installed in JBoss 4.2.x</para>
- </section>-->
-
<section id="features">
- <title>JBoss Messaging Features</title>
+ <title>JBoss Messaging 2.0</title>
+
+ <para>JBoss Messaging 2.0 alpha, is a bare-bones messaging system. This release is designed to show case the elegant architecture and high performance transport and persistence. Many other features, including state of the art clustering will be added before the final general availability (GA) release</para>
+
+ <para>This release contains the following features</para>
- <para>New features added since JBM 1.4</para>
-
<itemizedlist>
<listitem>
- <para>Journal based persistence.</para>
- <para>An append-only file system where messages and transactions are stored at a high performance rate. An external database is no longer required.</para>
+ <para>Class beating, ultra high performance journal based persistence</para>
+ <para>We have designed and implemented a fast append only journal which handles the persistence for JBoss Messaging 2.0. The journal is written 95% in Java for portability, and can run in one of two modes:</para>
+ <para>a) Using pure Java NIO. This provides great performance and runs on any operating system ther JVM runs on.</para>
+ <para>b) Using Linux asynchronous IO (aio). This provides even better performance, impossible via Java alone. This is implemented via a thin C++ layer which the journal tasks to via JNI. This option is only available when running on Linux</para>
</listitem>
<listitem>
- <para>JBoss Messaging uses
+ <para>JBoss Messaging 2.0 has a new high performance network transport which leverages Trustin Lee's
<ulink url="http://mina.apache.org/">MINA</ulink> to provide high
- performance and high scalability for its network layer with an
+ performance and high scalability at network layer with an
asynchronous API via Java NIO.</para>
+ <para>The JBoss Messaging team work closely with Trustin to ensure the smooth integration of MINA.</para>
</listitem>
<listitem>
- <para>Asynchronous IO (Linux only at the moment)</para>
- <para>Instead of syncing the disk and waiting for slow IO operations to complete during transactions, the writes are submitted directly to the kernel and a notification is sent back when it is complete.
- With this design a very high transaction rate is supported even on very short transactions containing just few messages or acknowledgements.</para>
- </listitem>
-
- <listitem>
<para>Standalone and embedded versions.</para>
<para>JBoss Messaging can be embedded in your own system without the requirement of any servers at all. Just instantiate a few POJOS (Plain Old Java Objects) and you have a Messaging System running.</para>
</listitem>
- </itemizedlist>
-
- <para>JBoss Messaging provides:</para>
-
- <itemizedlist>
- <listitem>
- <para>A fully compatible and Sun certified JMS 1.1 implementation,
- that currently works with a standard 4.2 or later JBoss
- Application Server installation.</para>
+
+ <listitem>
+ <para>Full JMS 1.1 support</para>
+ <para>JBoss Messaging provides a full JMS 1.1 API</para>
</listitem>
-
- <listitem>
- <para>A strong focus on performance, reliability and scalability
- with high throughput and low latency.</para>
+
+ <listitem>
+ <para>JMS agnostic messaging core</para>
+ <para>JBoss Messaging core is actually 100% JMS agnostic. It provides its own non JMS API and fully supports transactional (including XA), reliable, persistent messaging without JMS. The JMS API is actually provided as a thin facade on the client side which translates calls to and from the messaging core API.</para>
</listitem>
-
- <listitem>
- <para>A foundation for JBoss ESB for SOA initiatives; JBoss ESB
- uses JBoss Messaging as its default JMS provider.</para>
- </listitem>
</itemizedlist>
- <para>Other JBoss Messaging features include:</para>
-
- <itemizedlist>
- <listitem>
- <para>Publish-subscribe and point-to-point messaging models</para>
- </listitem>
-
- <listitem>
- <para>Persistent and non-persistent messages</para>
- </listitem>
-
- <listitem>
- <para>Guaranteed message delivery that ensures that messages
- arrive once and only once where required</para>
- </listitem>
-
- <listitem>
- <para>Transactional and reliable - supporting ACID
- semantics</para>
- </listitem>
-
- <listitem>
- <para>Customizable security framework based on JAAS</para>
- </listitem>
-
- <listitem>
- <para>Fully integrated with JBoss Transactions (formerly known as
- Arjuna JTA) for full transaction recoverability.</para>
- </listitem>
-
- <listitem>
- <para>Extensive JMX management interface</para>
- </listitem>
-
- <!-- <listitem>
- <para>Support for most major databases including Oracle, Sybase,
- MS SQL Server, PostgreSQL and MySQL</para>
- </listitem> -->
-
- <!-- not available for JB2 alpha
- <listitem>
- <para>HTTP transport to allow use through firewalls that only
- allow HTTP traffic</para>
- </listitem>
- -->
-
- <listitem>
- <para>SSL transport</para>
- </listitem>
-
- <listitem>
- <para>Configurable DLQs (Dead Letter Queues) and Expiry
- Queues</para>
- </listitem>
-
- <listitem>
- <para>Message statistics. Gives you a rolling historical view of
- what messages were delivered to what queues and
- subscriptions</para>
- </listitem>
-
- <!-- <listitem>
- <para>Automatic paging of messages to storage. Allows the use of
- very large queues - too large to fit in memory at once</para>
- </listitem> -->
- </itemizedlist>
-
- <!-- <para>Clustering features:</para>
-
- <itemizedlist>
- <listitem>
- <para>Fully clustered queues and topics. "Logical" queues and
- topics are distributed across the cluster. You can send to a queue
- or a topic from any node, and receive from any other.</para>
- </listitem>
-
- <listitem>
- <para>Fully clustered durable subscriptions. A particular durable
- subscription can be accessed from any node of the cluster -
- allowing you to spread processing load from that subscription
- across the cluster.</para>
- </listitem>
-
- <listitem>
- <para>Fully clustered temporary queues. Send a message with a
- replyTo of a temp queue and it can be sent back on any node of the
- cluster.</para>
- </listitem>
-
- <listitem>
- <para>Intelligent message redistribution. Messages are
- automatically moved between different nodes of the cluster if
- consumers are faster on one node than another. This can help
- prevent starvation or build up of messages on particular
- nodes.</para>
- </listitem>
-
- <listitem>
- <para>Message order protection. If you want to ensure that the
- order of messages produced by a producer is the same as is
- consumed by a consumer then you can set this to true. This works
- even in the presence of message redistribution.</para>
- </listitem>
-
- <listitem>
- <para>Fully transparent failover. When a server fails, your
- sessions continue without exceptions on a new node as if nothing
- happened. (Fully configurable - If you don't want this you can
- fall back to exceptions being thrown and manually recreation of
- connections on another node)</para>
- </listitem>
-
- <listitem>
- <para>High availability and seamless fail-over. If the node you
- are connected to fails, you will automatically fail over to
- another node and will not lose any persistent messages. You can
- carry on with your session seamlessly where you left off. Once and
- only once delivery of persistent messages is respected at all
- times.</para>
- </listitem>
-
- <listitem>
- <para>Message bridge. JBoss Messaging contains a message bridge
- component which enables you to bridge messages between any two
- JMS1.1 destinations on the same or physical separate locations.
- (E.g. separated by a WAN). This allows you to connect
- geographically separate clusters, forming huge globally
- distributed logical queues and topics.</para>
- </listitem>
- </itemizedlist>-->
</section>
</chapter>
\ No newline at end of file
More information about the jboss-cvs-commits
mailing list