[prev in list] [next in list] [prev in thread] [next in thread]
List: jboss-cvs-commits
Subject: [jboss-cvs] jboss-jms/docs/gettingstarted/en/modules ...
From: Luc Texier <ltexier () jboss ! com>
Date: 2006-03-31 22:13:13
Message-ID: E1FPRrl-0007ea-Sh () committer01 ! frg ! pub ! inap ! atl ! jboss ! com
[Download RAW message or body]
User: ltexier
Date: 06/03/31 17:13:13
Modified: docs/gettingstarted/en/modules about.xml
configuration.xml gettingstarted.xml
installation.xml introduction.xml
runningexamples.xml
Log:
fixed formatting and layout
Revision Changes Path
1.2 +33 -0 jboss-jms/docs/gettingstarted/en/modules/about.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: about.xml
===================================================================
RCS file: /cvsroot/jboss/jboss-jms/docs/gettingstarted/en/modules/about.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- about.xml 31 Mar 2006 10:03:38 -0000 1.1
+++ about.xml 31 Mar 2006 22:13:13 -0000 1.2
@@ -4,5 +4,38 @@
<para>The primary focus of this manual is to introduce a brand new module in the \
JEMS stack; JBoss Messaging 1.0. </para>
+ <para> </para>
+ <para> </para>
+ <para> </para>
+ <para> </para>
+ <para> </para>
+ <para> </para>
+ <para> </para>
+ <para> </para>
+ <para> </para>
+ <para> </para>
+ <para> </para>
+ <para> </para>
+ <para> </para>
+ <para> </para>
+ <para> </para>
+
+ <para>
+ <emphasis role="bold">Team:</emphasis>
+ </para>
+
+
+ <para>
+ Ovidiu Feodorov, Project Lead
+ </para>
+
+ <para>
+ Tim Fox, Senior Core Developer Messaging
+ </para>
+
+ <para>
+ Luc Texier, Lead Support EMEA
+ </para>
+
</chapter>
\ No newline at end of file
1.3 +34 -7 jboss-jms/docs/gettingstarted/en/modules/configuration.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: configuration.xml
===================================================================
RCS file: /cvsroot/jboss/jboss-jms/docs/gettingstarted/en/modules/configuration.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- configuration.xml 31 Mar 2006 20:44:27 -0000 1.2
+++ configuration.xml 31 Mar 2006 22:13:13 -0000 1.3
@@ -8,6 +8,20 @@
<emphasis role="bold">Note:</emphasis> In JBoss Messaging 1.0 most of those \
services are configurable via mbean definitions which are <emphasis \
role="bold">all</emphasis> located in \
<literal>jboss-messaging.sar/META-INF/jboss-service.xml</literal>. In the next \
release, configurations will be broken down into separate xml files. </para>
+
+ <section id="conf.serverpeer">
+ <title>Configuring the ServerPeer</title>
+
+ <para>
+ xxxxx
+
+ </para>
+
+ </section>
+
+
+
+
<section id="conf.persistence">
<title>Configuring JDBC persistence</title>
@@ -35,7 +49,7 @@
</programlisting>
<para>
- To change the pm configuration, navigate to \
/server/$SERVER_CONF/deploy/jboss-messaging.sar/META-INF and edit jboss-service.xml \
+ To change the pm configuration, navigate to \
<literal>/server/$SERVER_CONF/deploy/jboss-messaging.sar/META-INF</literal> and edit \
<literal>jboss-service.xml</literal>
From the example folder, copy the mbean definition that is appropriate for \
your database server e.g. mysql-jdbcpersistencemanager-service.xml Paste it in place \
of the existing one then restart the server. </para>
@@ -45,10 +59,23 @@
<section id="conf.destination">
<title>Configuring destinations</title>
- <para>
- xxxx
-
+ <para>Since JBoss Messaging is deployed in its own class loading domain, you \
need to deploy the destinations you want to use with JBoss Messaging within the same \
class loading domain. </para>
+ <para>An example of a deployment descriptor that does that is presented below. \
Create a new deployment descriptor named myqueue-service.xml (or anything else that \
ends in -service.xml) and copy it in your deployment directory. + </para>
+
+ <programlisting>
+<?xml version="1.0" encoding="UTF-8"?>
+ <server>
+ <loader-repository>jboss.messaging:loader=ScopedLoaderRepository
+ <loader-repository-config>java2ParentDelegation=false</loader-repository-config>
+ </loader-repository>
+ <mbean code="org.jboss.jms.server.jmx.Queue"
+ name="jboss.messaging.destination:service=Queue,name=myQueue">
+ <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
+ </mbean>
+ </server>
+ </programlisting>
</section>
@@ -65,7 +92,7 @@
<section id="conf.changingds">
<title>Changing the database</title>
- <para>By default, the Messaging services, relying on a datastore, are \
referencing <literal>"java:/DefaultDS"</literal>. If you are deploying a datasource \
with a different jndi name, you need to update all the <literal>DataSource</literal> \
attribute in jboss-service.xml as well. + <para>By default, the Messaging \
services, relying on a datastore, are referencing \
<literal>"java:/DefaultDS"</literal> for the datasource. If you are deploying a \
datasource with a different jndi name, you need to update all the \
<literal>DataSource</literal> attribute in jboss-service.xml as well. </para>
</section>
1.3 +14 -16 jboss-jms/docs/gettingstarted/en/modules/gettingstarted.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: gettingstarted.xml
===================================================================
RCS file: /cvsroot/jboss/jboss-jms/docs/gettingstarted/en/modules/gettingstarted.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- gettingstarted.xml 31 Mar 2006 20:44:27 -0000 1.2
+++ gettingstarted.xml 31 Mar 2006 22:13:13 -0000 1.3
@@ -2,25 +2,25 @@
<title>Getting started</title>
<para>
- The most recent official release of JBoss Messaging is available as a free \
download from <ulink url="http://www.jboss.com/products/messaging">the main JBoss \
messaging downloads page</ulink>. + The official release of JBoss Messaging is \
available as a free download from <ulink \
url="http://labs.jboss.com/portal/index.html?ctrl:id=page.default.info&project=jbossmessaging">the \
JBoss Messaging project landing page.</ulink> </para>
- <section id="directorystructure">
- <title>Directory overview</title>
- <para>After you have downloaded the package, extract the archive content into \
a location of your choice.
- </para>
- <para>
- Expanding the JBoss Messaging distribution creates a JBossMessaging-[release \
number] directory which contains the scoped archive, the source code, the examples \
and other documentation.
- </para>
-
- <figure id="img.directorystructure">
- <title>A view of the JBoss Messaging installation directory</title>
- <mediaobject><imageobject><imagedata align="center" \
fileref="images/directorystructure.jpg"/></imageobject></mediaobject>
- </figure>
+ <section id="releasebundle">
+ <title>The JBoss Messaging release bundle</title>
+ <itemizedlist>
+ <listitem><emphasis role="bold">jboss-messaging-scoped.sar: </emphasis> the \
deployable JBoss service archive that contains JBoss Messaging and its \
dependencies.</listitem> +<listitem><emphasis \
role="bold">jboss-messaging-client-scoped.sar: </emphasis> the client-side library \
that need to be in the classpath of the client that opens a remote connection to the \
Messaging server.</listitem> +<listitem><emphasis role="bold">examples: </emphasis> \
a collection of examples that should run out of the box and help you validate the \
installation. Detailed instructions are provided with each example, which range from \
very simple JMS queue and topic examples to relatively sophisticated use cases in \
which EJBs and JCA JMS ConnectionFactories are involved.</listitem> \
+<listitem><emphasis role="bold">util: </emphasis> a collection of scripts and ant \
configuration files that will help you with installation, JBossMQ replacement and \
various other tasks.</listitem> +<listitem><emphasis role="bold">src: </emphasis> \
the expanded JBoss Messaging source code. Note that JBoss Messaging cannot be built \
using exclusively this source snapshot, which is provided here for reference \
only.</listitem> +<listitem><emphasis role="bold">jboss-messaging-1.0.0-src.zip: \
</emphasis> the zipped src directory. The file can be directly installed into and use \
with a debugger.</listitem> +<listitem><emphasis \
role="bold">jboss-messaging-test-results-1.0.0.zip: </emphasis> the results of the \
release functional testuite run, in XML, text and HTML format.</listitem> + \
</itemizedlist>
</section>
+
<section id="CVS">
<title>CVS Access</title>
@@ -42,6 +42,4 @@
</itemizedlist>
</section>
-
-
</chapter>
\ No newline at end of file
1.3 +9 -9 jboss-jms/docs/gettingstarted/en/modules/installation.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: installation.xml
===================================================================
RCS file: /cvsroot/jboss/jboss-jms/docs/gettingstarted/en/modules/installation.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- installation.xml 31 Mar 2006 20:44:27 -0000 1.2
+++ installation.xml 31 Mar 2006 22:13:13 -0000 1.3
@@ -2,7 +2,7 @@
<title>Installation</title>
- <para>As of today, JBoss Messaging is conflicting with the existing JBoss MQ \
server that ships with the JBoss 4.x and 5.x distributions. Therefore the provider is \
packaged as a scoped Service ARchive (.sar) <emphasis role="bold">named \
jboss-messaging-scoped.sar</emphasis> + <para>As of today, JBoss Messaging is \
conflicting with the existing JBoss MQ server that ships with the JBoss 4.x and 5.x \
distributions. Therefore the provider is packaged as a scoped Service ARchive (.sar). \
</para>
<section id="install4">
@@ -85,13 +85,13 @@
<programlisting>
- <application-policy name = "other">
+<application-policy name = "other">
<authentication>
<login-module code = \
"org.jboss.security.auth.spi.UsersRolesLoginModule" flag = \
"required">
<module-option \
name="unauthenticatedIdentity">guest</module-option> \
</login-module> </authentication>
- </application-policy>
+</application-policy>
</programlisting>
@@ -167,7 +167,7 @@
</para>
<para>The following wiki page <ulink \
url="http://wiki.jboss.org/wiki/Wiki.jsp?page=ConfigJBossMQDB"> Critique of \
Hypersonic</ulink> outlines some of the well-known issues occuring when using this \
database. </para>
- <para>During development and before going in production, you <emphasis \
role="bold">must</emphasis> use an enterprise-class database backend such as MySQL, \
Oracle or PostgreSQL. See Section x.x for details about replacing HSQL. \
+ <para>During development and before going in production, you <emphasis \
role="bold">must</emphasis> use an enterprise-class database backend such as MySQL, \
Oracle or PostgreSQL. See Section 5.4 for details about replacing HSQL. </para>
1.2 +1 -1 jboss-jms/docs/gettingstarted/en/modules/introduction.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: introduction.xml
===================================================================
RCS file: /cvsroot/jboss/jboss-jms/docs/gettingstarted/en/modules/introduction.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- introduction.xml 31 Mar 2006 10:03:38 -0000 1.1
+++ introduction.xml 31 Mar 2006 22:13:13 -0000 1.2
@@ -101,7 +101,7 @@
<title>Compatibility with JBossMQ</title>
- <para> JBossMQ is the JMS currently embedded within JBoss AS. Since JBoss \
Messaging is JMS 1.1 and JMS 1.0.2b compatible, the JMS code written against \
JBossMQ will run with JBoss Messaging without any changes. The backward compatibility \
will extend to deployment descriptors as well. + <para> JBossMQ is the \
JMS implementation currently embedded within JBossAS. Since JBoss Messaging is JMS \
1.1 and JMS 1.0.2b compatible, the JMS code written against JBossMQ will run \
with JBoss Messaging without any changes. The backward compatibility will extend to \
deployment descriptors as well </para>
</section>
1.3 +12 -32 jboss-jms/docs/gettingstarted/en/modules/runningexamples.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: runningexamples.xml
===================================================================
RCS file: /cvsroot/jboss/jboss-jms/docs/gettingstarted/en/modules/runningexamples.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- runningexamples.xml 31 Mar 2006 20:44:27 -0000 1.2
+++ runningexamples.xml 31 Mar 2006 22:13:13 -0000 1.3
@@ -380,22 +380,17 @@
<para>This example deploys a simple Message Driven Bean that processes \
messages sent to a test queue. Once it receives a message and "processes" it, the \
MDB sends an acknowledgment message to a temporary destination created by the sender \
for this purpose. The example is considered successful if the sender receives the \
acknowledgment message. </para>
- <programlisting>
- cd $JBOSS_HOME/server
- cp -r default messaging
- </programlisting>
-
<para>The MDB ejb-jar.xml descriptor
</para>
<programlisting>
<ejb-jar>
-<enterprise-beans>
-<message-driven>
-<ejb-name>MDBExample</ejb-name>
-<ejb-class>org.jboss.example.jms.mdb.MDBExample</ejb-class>
-<transaction-type>Container</transaction-type>
-</message-driven>
-</enterprise-beans>
+ <enterprise-beans>
+ <message-driven>
+ <ejb-name>MDBExample</ejb-name>
+ <ejb-class>org.jboss.example.jms.mdb.MDBExample</ejb-class>
+ <transaction-type>Container</transaction-type>
+ </message-driven>
+ </enterprise-beans>
</ejb-jar>
</programlisting>
@@ -403,10 +398,10 @@
</para>
<programlisting>
<enterprise-beans>
-<message-driven>
-<ejb-name>MDBExample</ejb-name>
-<destination-jndi-name>queue/@QUEUE_NAME@</destination-jndi-name>
-</message-driven>
+ <message-driven>
+ <ejb-name>MDBExample</ejb-name>
+ <destination-jndi-name>queue/@QUEUE_NAME@</destination-jndi-name>
+ </message-driven>
</enterprise-beans>
</programlisting>
@@ -466,7 +461,7 @@
{
// flip the string
- String result = "";
+ String result = ";
for(int i = 0; i < text.length(); i++)
{
@@ -511,19 +506,4 @@
</section>
-
-
- <para>
-
- Bonus
-
-
- Using an IDE
-
-
-
- </para>
-
-
-
</chapter>
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
jboss-cvs-commits mailing list
jboss-cvs-commits@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-cvs-commits
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic