[jboss-cvs] JBoss Messaging SVN: r6948 - in trunk: examples/core/embedded and 1 other directories.

jboss-cvs-commits at lists.jboss.org jboss-cvs-commits at lists.jboss.org
Wed May 20 18:11:13 EDT 2009


Author: clebert.suconic at jboss.com
Date: 2009-05-20 18:11:13 -0400 (Wed, 20 May 2009)
New Revision: 6948

Added:
   trunk/docs/user-manual/en/jar-dependencies.xml
Modified:
   trunk/docs/user-manual/en/embedding-jbm.xml
   trunk/docs/user-manual/en/examples.xml
   trunk/docs/user-manual/en/master.xml
   trunk/docs/user-manual/en/paging.xml
   trunk/docs/user-manual/en/using-server.xml
   trunk/examples/core/embedded/build.xml
   trunk/examples/jms/embedded/build.xml
Log:
Tweaks on docs, adding jar-dependencies (not finished yet)

Modified: trunk/docs/user-manual/en/embedding-jbm.xml
===================================================================
--- trunk/docs/user-manual/en/embedding-jbm.xml	2009-05-20 20:29:18 UTC (rev 6947)
+++ trunk/docs/user-manual/en/embedding-jbm.xml	2009-05-20 22:11:13 UTC (rev 6948)
@@ -56,8 +56,7 @@
         new MessagingServerImpl(config,
                                 ManagementFactory.getPlatformMBeanServer(),
                                 new JBMSecurityManagerImpl());
-server.start();
-        </programlisting>
+server.start();</programlisting>
     </section>
     <section>
         <title>Dependency Frameworks</title>
@@ -141,7 +140,7 @@
                       new TransportConfiguration(
                               InVMConnectorFactory.class.getName()), null);
 
-ClientSession session = factory.createSession();
+ClientSession session = factory.createSession(false, true, true);
 session.createQueue("example", "example", true);
 
 ClientProducer producer = session.createProducer("example");
@@ -158,8 +157,7 @@
 ClientMessage msgReceived = consumer.receive();
 System.out.println("message = " + msgReceived.getBody().readString());
 
-session.close();
-            </programlisting>
+session.close();</programlisting>
         </section>
         <section>
             <title>JMS API</title>
@@ -192,8 +190,7 @@
 
 sess.commit();
 
-conn.close();
-            </programlisting>
+conn.close();</programlisting>
         </section>
     </section>
     <section>

Modified: trunk/docs/user-manual/en/examples.xml
===================================================================
--- trunk/docs/user-manual/en/examples.xml	2009-05-20 20:29:18 UTC (rev 6947)
+++ trunk/docs/user-manual/en/examples.xml	2009-05-20 22:11:13 UTC (rev 6948)
@@ -75,7 +75,6 @@
                 temporary connection failure allowing them to be an ideal choice for forwarding over
                 unreliable connections, e.g. a WAN.</para>
         </section>
-        
         <section>
             <title>Client Kickoff</title>
             <para>This example shows how to kick off a client connected to JBoss Messaging using
@@ -96,8 +95,6 @@
                 messages via the producer, and we verify that both subscribers receive all the sent
                 messages.</para>
         </section>
-        
-       
         <section>
             <title>Dead Letter</title>
             <para>This example shows you how to define and deal with dead letter messages. Messages
@@ -144,9 +141,6 @@
             <para>This example shows how to embed the JBoss Messaging Server within your own
                 code.</para>
         </section>
-        
-        
-        
         <section>
             <title>HTTP Transport</title>
             <para>This example shows you how to configure JBoss Messaging to use HTTP protocol as
@@ -309,12 +303,10 @@
                 delivering it to the client. This example demonstrates how JBoss Messaging soes
                 this.</para>
         </section>
-        
         <section>
             <title>Queue</title>
             <para>A simple example demonstrating a JMS Queue.</para>
         </section>
-        
         <section>
             <title>Queue Requestor</title>
             <para>A simple example demonstrating a JMS queue requestor.</para>
@@ -324,7 +316,6 @@
             <para>This example shows you how to selectively consume messages using message selectors
                 with queue consumers.</para>
         </section>
-        
         <section>
             <title>Request-Reply</title>
             <para>A simple example showing the JMS request-reply pattern.</para>
@@ -338,7 +329,6 @@
             <title>Security</title>
             <para>This example shows you how configure and use security with JBoss Messaging.</para>
         </section>
-        
         <section>
             <title>Static Message Selector</title>
             <para>This example shows you how to configure a JBoss Messaging queue with static
@@ -417,6 +407,16 @@
         </section>
     </section>
     <section>
+        <title>Core API Examples</title>
+        <para>To run a Core API example, simply <literal>cd</literal> into the appropriate example
+            directory and type <literal>ant</literal></para>
+        <section>
+            <title>Embedded</title>
+            <para>This example shows how to embed the JBoss Messaging Server within your own
+                code.</para>
+        </section>
+    </section>
+    <section>
         <title>Java EE Examples</title>
         <para>Most of the Java EE examples can be run the following way. simply cd into the
             appropriate example directory an type <literal>ant deploy</literal>. This will create a

Added: trunk/docs/user-manual/en/jar-dependencies.xml
===================================================================
--- trunk/docs/user-manual/en/jar-dependencies.xml	                        (rev 0)
+++ trunk/docs/user-manual/en/jar-dependencies.xml	2009-05-20 22:11:13 UTC (rev 6948)
@@ -0,0 +1,70 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="jar-dependencies">
+    <title>Jar Dependencies</title>
+    <para>JBoss Messaging was designed to have as few dependencies on external jars as possible. In
+        fact, JBoss Messaging core has zero dependencies on any jars other than the standard JDK
+        classes!</para>
+    <para>However depending on how you're running JBoss Messaging, you may require extra jars. Each
+        section here will explain the requirements.</para>
+    <section>
+        <title>JBoss Messaging Jars</title>
+        <table frame="topbot">
+            <title>List of jars distributed by JBoss Messaging</title>
+            <tgroup cols="3">
+                <colspec colname="c1" colnum="1"/>
+                <colspec colname="c2" colnum="2"/>
+                <colspec colname="c3" colnum="3"/>
+                <thead>
+                    <row>
+                        <entry>Name</entry>
+                        <entry>Description</entry>
+                        <entry>Dependencies</entry>
+                    </row>
+                </thead>
+                <tbody>
+                    <row>
+                        <entry><link linkend="using-core">jbm-core.jar</link></entry>
+                        <entry>JBoss Messaging Core</entry>
+                        <entry>No dependencies</entry>
+                    </row>
+                    <row>
+                        <entry><link linkend="using-core">jbm-core-client.jar</link></entry>
+                        <entry>JBoss Messaging Core Client</entry>
+                        <entry>No dependencies</entry>
+                    </row>
+                    <row>
+                        <entry><link linkend="using-jms">jbm-jms.jar</link></entry>
+                        <entry>JBoss Messaging JMS wrappers</entry>
+                        <entry>jbm-core.jar</entry>
+                    </row>
+                    <row>
+                        <entry><link linkend="using-server">jbm-bootstrap.jar</link></entry>
+                        <entry>Standalone server support</entry>
+                        <entry>jbm-core.jar and JBoss Micro Container</entry>
+                    </row>
+                    <row>
+                        <entry><link linkend="logging">jbm-logging.jar</link></entry>
+                        <entry>Wrapper to other Logger Frameworks</entry>
+                        <entry>Log4j or JBoss Logger depending on the logging configuration</entry>
+                    </row>
+                    <row>
+                        <entry><link linkend="logging">jbm-logging.jar</link></entry>
+                        <entry>Wrapper to other Logger Frameworks</entry>
+                        <entry>Log4j or JBoss Logger depending on the logging configuration</entry>
+                    </row>
+                    <row>
+                        <entry><link linkend="security">jbm-jbossas-security.jar</link></entry>
+                        <entry>Classes used to start a standalone server</entry>
+                        <entry>Only JDK if using <literal>JAAS</literal> or JBoss libraries if using <literal>JBossASSecurityManager</literal></entry>
+                    </row>
+                    <row>
+                        <entry><link linkend="configuring-transports">jbm-transports.jar</link></entry>
+                        <entry>Socket and HTTP Transport plugins</entry>
+                        <entry>Netty jars</entry>
+                    </row>
+                    
+                </tbody>
+            </tgroup>
+        </table>
+    </section>
+</chapter>


Property changes on: trunk/docs/user-manual/en/jar-dependencies.xml
___________________________________________________________________
Name: svn:mergeinfo
   + 

Modified: trunk/docs/user-manual/en/master.xml
===================================================================
--- trunk/docs/user-manual/en/master.xml	2009-05-20 20:29:18 UTC (rev 6947)
+++ trunk/docs/user-manual/en/master.xml	2009-05-20 22:11:13 UTC (rev 6948)
@@ -40,6 +40,7 @@
         <!ENTITY thread-pooling          SYSTEM "thread-pooling.xml">
         <!ENTITY undelivered-messages    SYSTEM "undelivered-messages.xml">
         <!ENTITY using-core              SYSTEM "using-core.xml">
+        <!ENTITY jar-dependencies        SYSTEM "jar-dependencies.xml">
         <!ENTITY using-jms               SYSTEM "using-jms.xml">
         <!ENTITY using-server            SYSTEM "using-server.xml">
         <!ENTITY wildcard-syntax         SYSTEM "wildcard-syntax.xml">
@@ -93,6 +94,7 @@
    &interoperability;
    &perf-tuning;
    &configuration-index;
+   &jar-dependencies;
    &project-info;
    
 </book>

Modified: trunk/docs/user-manual/en/paging.xml
===================================================================
--- trunk/docs/user-manual/en/paging.xml	2009-05-20 20:29:18 UTC (rev 6947)
+++ trunk/docs/user-manual/en/paging.xml	2009-05-20 22:11:13 UTC (rev 6948)
@@ -44,7 +44,7 @@
 ...        </programlisting>
             <para>
                 <table frame="topbot">
-                    <title/>
+                    <title>Paging Configuration Parameters</title>
                     <tgroup cols="3">
                         <colspec colname="c1" colnum="1"/>
                         <colspec colname="c2" colnum="2"/>
@@ -102,7 +102,7 @@
             <para>This is the list of available parameters on the address settings.</para>
             <para>
                 <table frame="topbot">
-                    <title/>
+                    <title>Paging Address Settings</title>
                     <tgroup cols="3">
                         <colspec colname="c1" colnum="1"/>
                         <colspec colname="c2" colnum="2"/>

Modified: trunk/docs/user-manual/en/using-server.xml
===================================================================
--- trunk/docs/user-manual/en/using-server.xml	2009-05-20 20:29:18 UTC (rev 6947)
+++ trunk/docs/user-manual/en/using-server.xml	2009-05-20 22:11:13 UTC (rev 6948)
@@ -40,7 +40,7 @@
             are the place to do it.</para>
     </section>
     <section>
-        <title>Server classpath</title>
+        <title>Server runtime</title>
         <para>JBoss Messaging looks for its configuration files on the Java classpath</para>
         <para>The scripts <literal>run.sh</literal> and <literal>run.bat</literal> specify the
             classpath when calling Java to run the server.</para>
@@ -183,8 +183,7 @@
 &lt;/bean&gt;
 
 &lt;!-- The core server --&gt;
-&lt;bean name="MessagingServer" 
-    class="org.jboss.messaging.core.server.impl.MessagingServerImpl"&gt;
+&lt;bean name="MessagingServer" class="org.jboss.messaging.core.server.impl.MessagingServerImpl"&gt;
 &lt;start ignored="true"/&gt;
 &lt;stop ignored="true"/&gt;  
 &lt;constructor&gt;

Modified: trunk/examples/core/embedded/build.xml
===================================================================
--- trunk/examples/core/embedded/build.xml	2009-05-20 20:29:18 UTC (rev 6947)
+++ trunk/examples/core/embedded/build.xml	2009-05-20 22:11:13 UTC (rev 6948)
@@ -32,12 +32,20 @@
 
    <import file="../../common/build.xml"/>
 
-   <target name="run">   	
-      <antcall target="runExample">
-         <param name="example.classname" value="org.jboss.core.example.EmbeddedExample"/>
-         <!-- We limit the client to running in only 50MB of RAM -->
-     	   <param name="java-min-memory" value="50M"/>
-     	   <param name="java-max-memory" value="50M"/>
-      </antcall>
+   <!-- We use a minimal classpath on this example -->
+   <path id="local.classpath">
+      <fileset dir="${jbm.jars.dir}">
+         <include name="jbm-core.jar"/>
+      </fileset>
+      <pathelement location="${classes.dir}"/>	   	
+   </path>
+
+   <target name="run" depends="compile">   	
+
+    <java classname="org.jboss.core.example.EmbeddedExample" fork="true" resultproperty="example-result">
+       <jvmarg value="-Xms50M"/>
+       <jvmarg value="-Xmx50M"/>
+       <classpath refid="local.classpath"/>
+    </java>
    </target>
 </project>

Modified: trunk/examples/jms/embedded/build.xml
===================================================================
--- trunk/examples/jms/embedded/build.xml	2009-05-20 20:29:18 UTC (rev 6947)
+++ trunk/examples/jms/embedded/build.xml	2009-05-20 22:11:13 UTC (rev 6948)
@@ -32,12 +32,26 @@
 
    <import file="../../common/build.xml"/>
 
-   <target name="run">   	
-      <antcall target="runExample">
-         <param name="example.classname" value="org.jboss.jms.example.EmbeddedExample"/>
-         <!-- We limit the client to running in only 50MB of RAM -->
-     	   <param name="java-min-memory" value="50M"/>
-     	   <param name="java-max-memory" value="50M"/>
-      </antcall>
+   <!-- We use a minimal classpath on this example -->
+   <path id="local.classpath">
+	  <fileset dir="${jbm.jars.dir}">
+	       <include name="jbm-core.jar"/>
+	       <include name="jbm-jms.jar"/>
+	  </fileset>
+	 	
+	  <fileset dir="${jars.dir}">
+	       <include name="jboss/jboss-javaee/lib/jboss-javaee.jar"/>
+	  </fileset>
+
+   	  <pathelement location="${classes.dir}"/>	   	
+   </path>
+
+   <target name="run" depends="compile">   	
+
+    <java classname="org.jboss.jms.example.EmbeddedExample" fork="true" resultproperty="example-result">
+       <jvmarg value="-Xms50M"/>
+       <jvmarg value="-Xmx50M"/>
+       <classpath refid="local.classpath"/>
+    </java>
    </target>
 </project>




More information about the jboss-cvs-commits mailing list