[jboss-cvs] JBoss Messaging SVN: r6936 - trunk/docs/quickstart-guide/en.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Wed May 20 11:10:39 EDT 2009
Author: ataylor
Date: 2009-05-20 11:10:38 -0400 (Wed, 20 May 2009)
New Revision: 6936
Modified:
trunk/docs/quickstart-guide/en/about.xml
trunk/docs/quickstart-guide/en/examples.xml
trunk/docs/quickstart-guide/en/introduction.xml
trunk/docs/quickstart-guide/en/running.xml
Log:
reformatted code and tables for quick start guide and added intro and about chapters
Modified: trunk/docs/quickstart-guide/en/about.xml
===================================================================
--- trunk/docs/quickstart-guide/en/about.xml 2009-05-20 14:36:24 UTC (rev 6935)
+++ trunk/docs/quickstart-guide/en/about.xml 2009-05-20 15:10:38 UTC (rev 6936)
@@ -1,5 +1,42 @@
<?xml version="1.0" encoding="UTF-8"?>
<chapter id="about">
<title>About JBoss Messaging</title>
- <para>TODO: copy blurb from User Guide</para>
+ <para>The goal of JBoss Messaging 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 a few of the reasons:</para>
+ <itemizedlist>
+ <listitem>
+ <para>100% open source software. We use the Apache Software License version 2.0 to limit
+ restrictions on use.</para>
+ </listitem>
+ <listitem>
+ <para>Written in Java. Runs on any platform with a J2SE 5.0 JDK, that's everything from
+ Windows desktops to IBM mainframes.</para>
+ </listitem>
+ <listitem>
+ <para>Superb performance. Our class beating high performance journal provides persistent
+ messaging performance at rates normally seen for non persistent messaging.</para>
+ </listitem>
+ <listitem>
+ <para>Full feature set. All the features you'd expect in any serious messaging system,
+ and others you won't find anywhere else.</para>
+ </listitem>
+ <listitem>
+ <para>Elegant POJO based design with minimal third party dependencies. Run JBoss
+ Messaging stand-alone, run it in integrated in your favourite JEE application
+ server, or run it embedded inside your own product.</para>
+ </listitem>
+ <listitem>
+ <para>Seamless high availabilty. We provide server replication and completely
+ transparent client failover so you don't have to worry about coding your client
+ specially for an HA environment.</para>
+ </listitem>
+ <listitem>
+ <para>Hugely flexible clustering. Create clusters of servers that know how to load
+ balance messages. Link geographically distributed clusters over unreliable
+ connections to form a global network. Configure routing of messages in a highly
+ flexible way.</para>
+ </listitem>
+ </itemizedlist>
</chapter>
\ No newline at end of file
Modified: trunk/docs/quickstart-guide/en/examples.xml
===================================================================
--- trunk/docs/quickstart-guide/en/examples.xml 2009-05-20 14:36:24 UTC (rev 6935)
+++ trunk/docs/quickstart-guide/en/examples.xml 2009-05-20 15:10:38 UTC (rev 6936)
@@ -113,6 +113,8 @@
<para>Once set we can then deploy the application, from inside the <literal
>examples/javaee/mdb</literal> directory run the command:</para>
<programlisting>ant deploy</programlisting>
+ <para>This will make a copy of the messaging profile in the JBoss Application server and start
+ the server.</para>
<para>In the shell window you should see something like the following output:</para>
<programlisting>Buildfile: build.xml
@@ -140,40 +142,29 @@
deploy-ear:
[copy] Copying 1 file to /home/andy/projects/jbossas5.1/build/output/jboss-5.1.0.GA
- /server/default-with-jbm2/deploy
-deploy-misc:
+ .......
-BUILD SUCCESSFUL
-Total time: 6 seconds
+
+ [exec] 16:01:04,607 INFO [JBossASKernel] Class:javax.jms.MessageListener
+ [exec] 16:01:04,607 INFO [JBossASKernel] Added bean(jboss.j2ee:ear=mdb-example.ear,
+ jar=mdb-example.jar,name=MessageMDBExample,service=EJB3) to KernelDeployment of:
+ mdb-example.jar
+ [exec] 16:01:04,702 INFO [EJBContainer] STARTED EJB: org.jboss.javaee.example.server
+ .MDBExample ejbName: MessageMDBExample
+ [exec] 16:01:09,496 INFO [TomcatDeployment] deploy, ctxPath=/mdb-example
+ [exec] 16:01:09,812 WARNING [config] Unable to process deployment descriptor for cont
+ ext '/mdb-example'
+ [exec] 16:01:09,812 INFO [config] Initializing Mojarra (1.2_12-b01-FCS) for context
+ '/mdb-example'
+ [exec] 16:01:09,958 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-
+ 8080
+ [exec] 16:01:09,990 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
+ [exec] 16:01:10,001 INFO [ServerImpl] JBoss (Microcontainer) [5.1.0.GA (build: SVNTag
+ =JBoss_5_1_0_GA date=200905151005)] Started in 6m:21s:797ms
+
</programlisting>
- <para>You can then confirm that the application has been succesfully deployed by checking the
- output from the JBoss Application Server, you should see something like:</para>
- <programlisting>
-16:26:31,584 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymen
-tContext at 1992739{vfszip:/home/andy/projects/jbossas5.1/build/output/jboss-5.1.0.GA/server
-/default-with-jbm2/deploy/mdb-example.ear/mdb-example.jar/}
-16:26:31,584 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymen
-tContext at 1992739{vfszip:/home/andy/projects/jbossas5.1/build/output/jboss-5.1.0.GA/server
-/default-with-jbm2/deploy/mdb-example.ear/mdb-example.jar/}
-16:26:31,621 INFO [JBossASKernel] Created KernelDeployment for: mdb-example.jar
-16:26:31,622 INFO [JBossASKernel] installing bean: jboss.j2ee:ear=mdb-example.ear,jar=md
-b-example.jar,name=Mes
-sageMDBExample,service=EJB3
-16:26:31,622 INFO [JBossASKernel] with dependencies:
-16:26:31,622 INFO [JBossASKernel] and demands:
-16:26:31,622 INFO [JBossASKernel] jboss.ejb:service=EJBTimerService
-16:26:31,622 INFO [JBossASKernel] and supplies:
-16:26:31,622 INFO [JBossASKernel] jndi:null
-16:26:31,622 INFO [JBossASKernel] Class:javax.jms.MessageListener
-16:26:31,622 INFO [JBossASKernel] Added bean(jboss.j2ee:ear=mdb-example.ear,jar=mdb-examp
-le.jar,name=MessageMD
-BExample,service=EJB3) to KernelDeployment of: mdb-example.jar
-16:26:31,651 INFO [EJBContainer] STARTED EJB: org.jboss.javaee.example.server.MDBExample
-ejbName: MessageMDBEx
-ample
-</programlisting>
- <para>We can now run the example, do this by running the follwing command from within the
+ <para>We can now run the example, do this by running the following command from within the
<literal>mdb</literal> directory.</para>
<programlisting>ant</programlisting>
<para>You should see some output similar to the following:</para>
Modified: trunk/docs/quickstart-guide/en/introduction.xml
===================================================================
--- trunk/docs/quickstart-guide/en/introduction.xml 2009-05-20 14:36:24 UTC (rev 6935)
+++ trunk/docs/quickstart-guide/en/introduction.xml 2009-05-20 15:10:38 UTC (rev 6936)
@@ -1,5 +1,7 @@
<?xml version="1.0" encoding="UTF-8"?>
<chapter id="introduction">
- <title>Introduction</title>
- <para>TODO</para>
-</chapter>
\ No newline at end of file
+ <title>Introduction</title>
+ <para>This guide will help you to download, install and run JBoss Messaging. It will also get
+ you started by running some examples. For more in depth information use the JBoss Messaging
+ User Guide.</para>
+</chapter>
Modified: trunk/docs/quickstart-guide/en/running.xml
===================================================================
--- trunk/docs/quickstart-guide/en/running.xml 2009-05-20 14:36:24 UTC (rev 6935)
+++ trunk/docs/quickstart-guide/en/running.xml 2009-05-20 15:10:38 UTC (rev 6936)
@@ -1,41 +1,44 @@
<?xml version="1.0" encoding="UTF-8"?>
<chapter id="running">
<title>Starting The Server</title>
-
<section id="running.standalone">
<title>Standalone JBoss Messaging</title>
- <para>To run a standalone server, open up a shell or command prompt and navigate into the <literal>bin</literal> directory.
- Then execute <literal>./run.sh</literal> (or <literal>run.bat</literal> on Windows) and you should see the following output
- </para>
+ <para>To run a standalone server, open up a shell or command prompt and navigate into the
+ <literal>bin</literal> directory. Then execute <literal>./run.sh</literal> (or <literal
+ >run.bat</literal> on Windows) and you should see the following output </para>
<programlisting>
bin$ ./run.sh
15:05:54,108 INFO @main [JBMBootstrapServer] Starting JBoss Messaging server
...
- 15:06:02,566 INFO @main [MessagingServerImpl] JBoss Messaging Server version 2.0.0.BETA1-SNAPSHOT (Stilton, 101) started
+ 15:06:02,566 INFO @main [MessagingServerImpl] JBoss Messaging Server version
+ 2.0.0.BETA1-SNAPSHOT (Stilton, 101) started
</programlisting>
- <para>JBoss Messaging is now running. If any errors are displayed or if the server was not started properly, please refer to the troubleshooting guide for help</para>
- <para>By default, JBoss Messaging is run in a <emphasis>non-clustered</emphasis> configuration (based on the configuration in
- <literal>config/stand-alone/non-clustered</literal> directory).</para>
+ <para>JBoss Messaging is now running. If any errors are displayed or if the server was not
+ started properly, please refer to the troubleshooting guide for help</para>
+ <para>By default, JBoss Messaging is run in a <emphasis>non-clustered</emphasis> configuration
+ (based on the configuration in <literal>config/stand-alone/non-clustered</literal>
+ directory).</para>
</section>
-
<section id="running.jboss.as">
<title>JBoss Messaging In JBoss AS 5</title>
- <para>To run JBoss Messaging in JBoss AS 5, you need to create the
- <link linkend="installation.jboss">AS 5 profiles for JBoss Messaging</link> first.
- Then run JBoss AS 5 with one these profiles. For example, to run JBoss AS 5 with a
- <emphasis>non-clustered</emphasis> JBoss Messaging server, got to <literal>$JBOSS_HOME/bin</literal>
- directory and type:</para>
+ <para>To run JBoss Messaging in JBoss AS 5, you need to create the <link
+ linkend="installation.jboss">AS 5 profiles for JBoss Messaging</link> first. Then run
+ JBoss AS 5 with one these profiles. For example, to run JBoss AS 5 with a
+ <emphasis>non-clustered</emphasis> JBoss Messaging server, got to <literal
+ >$JBOSS_HOME/bin</literal> directory and type:</para>
<programlisting>
bin$ ./run.sh -c default-with-jbm2
15:18:35,460 INFO [ServerImpl] Starting JBoss (Microcontainer)...
- 15:18:35,462 INFO [ServerImpl] Release ID: JBoss [The Oracle] 5.1.0.CR1 (build: SVNTag=JBoss_5_1_0_CR1 date=200904091504)
+ 15:18:35,462 INFO [ServerImpl] Release ID: JBoss [The Oracle] 5.1.0.CR1 (build:
+ SVNTag=JBoss_5_1_0_CR1 date=200904091504)
...
- 15:19:30,305 INFO [MessagingServerImpl] JBoss Messaging Server version 2.0.0.BETA1-SNAPSHOT (Stilton, 101) started
+ 15:19:30,305 INFO [MessagingServerImpl] JBoss Messaging Server version
+ 2.0.0.BETA1-SNAPSHOT (Stilton, 101) started
...
- 15:19:43,601 INFO [ServerImpl] JBoss (Microcontainer) [5.1.0.CR1 (build: SVNTag=JBoss_5_1_0_CR1 date=200904091504)] Started in 1m:8s:121ms
+ 15:19:43,601 INFO [ServerImpl] JBoss (Microcontainer) [5.1.0.CR1 (build:
+ SVNTag=JBoss_5_1_0_CR1 date=200904091504)] Started in 1m:8s:121ms
</programlisting>
</section>
-
-</chapter>
\ No newline at end of file
+</chapter>
More information about the jboss-cvs-commits
mailing list