User: tobias
Date: 01/03/12 03:52:37
Modified: src/docs jbossintro.xml
Log:
updated for JBoss 2.1 official release
Revision Changes Path
1.6 +48 -30 manual/src/docs/jbossintro.xml
Index: jbossintro.xml
===================================================================
RCS file: /products/cvs/ejboss/manual/src/docs/jbossintro.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- jbossintro.xml 2001/03/12 01:04:15 1.5
+++ jbossintro.xml 2001/03/12 11:52:36 1.6
@@ -3,6 +3,7 @@
<para>Author:
<author><firstname>Kevin</firstname><surname>Boone</surname></author>
<email>[EMAIL PROTECTED]</email>
+ <author><firstname>Tobias</firstname><surname>Frech</surname></author>
</para>
<section><title>Introduction</title>
@@ -26,7 +27,8 @@
<title>About JBoss</title>
<para>
-JBoss is an implementation of the EJB 1.1 specification, that is, it is a
+JBoss is an implementation of the EJB 1.1 (and parts of 2.0)
+specification, that is, it is a
server and container for Enterprise JavaBeans. In this it is similar to Sun's
`J2SDK Enterprise Edition' (J2EE), but JBoss is much more single-minded than
J2EE. JBoss provides only an EJB server; it does not include
@@ -90,7 +92,7 @@
<section><title>Installing JBoss</title>
<para>Before installing and running the server, you should check that your JDK
-installation is working. (Step-by-step instructions are available.) You will
+installation is working. You will
need the JDK binaries directory in your PATH (this is essential: see below)
not just for the user account which is doing the installation, but also for
the user account that will run the server. If you are running the server as
@@ -110,10 +112,10 @@
as appropriate.</para>
<para>JBoss is distributed as a ZIP file. You can download the binary
-distribution which contains the latest offical release (which was 2.0
-FINAL at the time of writing) or a source snapshot with the latest
-version from CVS (called PRE2.1). This documentation mainly is written
-for the 2.0
+distribution which contains the latest offical release (which was 2.1
+at the time of writing) or a source snapshot with the latest
+version from CVS. This documentation mainly is written
+for the 2.1
version. You can get all the mentioned packages from http://www.jboss.org .
</para>
@@ -132,11 +134,11 @@
<formalpara><title>Installation of binary package for Linux:</title>
<para><literallayout><command>cd /tmp/
-lynx -source http://www.jboss.org/newsite/bin/jBoss-2.0_FINAL.zip >
jBoss-2.0_FINAL.zip
+lynx -source http://www.jboss.org/newsite/bin/jboss-2.1.zip > jboss-2.1.zip
su
cd /usr/local/
-unzip /tmp/jBoss-2.0_FINAL.zip
-mv jBoss-2.0_FINAL jboss
+unzip /tmp/jboss-2.1.zip
+mv dist jboss
cd jboss
</command></literallayout>
</para></formalpara>
@@ -260,7 +262,7 @@
The remote interface in this example is very simple.
</para>
-<figure><title>Remote interface for the `interest' EJB</title>
+<figure><title>Remote interface for the `interest' EJB, file name
Interest.java</title>
<programlisting>
package com.web_tomorrow.interest;
import javax.ejb.EJBObject;
@@ -291,7 +293,7 @@
calculateCompoundInterest. The home interface is even simpler. </para>
-<figure><title>Home interface for the `interest' EJB</title>
+<figure><title>Home interface for the `interest' EJB, file name
InterestHome.java</title>
<programlisting>
package com.web_tomorrow.interest;
import java.io.Serializable;
@@ -317,7 +319,7 @@
<para>Finally, here is the Bean class. This is the only one that does any real
work in this simple example.</para>
-<figure><title>Bean class for the `interest' EJB</title>
+<figure><title>Bean class for the `interest' EJB, file name
InterestBean.java</title>
<programlisting>
package com.web_tomorrow.interest;
@@ -386,7 +388,10 @@
<para>
Substituting the correct path to the JBoss class EJB library if you haven't
-installed JBoss in /usr/local/jboss. This should create three class files:
+installed JBoss in /usr/local/jboss. Also remember to start
+compilation from your source root directory, which is right above
+<quote>com</quote> from com/web_tomorrow/interest/.
+This should create three class files:
InterestBean.class, Interest.class, and InterestHome.class.
With the classes compiled, it's time to create the deployment
descriptor.</para>
@@ -488,12 +493,12 @@
<para>If you don't provide a jboss.xml file you will find your bean under the
name "Interest".</para>
-<para>Overriding ejb-name with a real JNDI name in jboss.xml</para>
+<section><title>Overriding ejb-name with a real JNDI name in jboss.xml</title>
<para>If in deployment you would rather use the "myApp/myBean" naming pattern
you need to provide the following text in jboss.xml. </para>
-<para>jboss.xml: ()</para>
+<para>jboss.xml:</para>
<figure><title>The JBoss XML descriptor. (Optional, this file is provided by
the Bean deployer)</title>
@@ -517,13 +522,13 @@
<para>The indentation is just there for formatting and readability, it is non
important.</para>
-
-<para>So now we've got the deployment descriptor ejb-jar.xml. Again jboss will
+<para>So now we've got the deployment descriptor ejb-jar.xml. Again JBoss will
happily run just from that file and bind the object under "Interest" as
standard JNDI name. We also have the optional jboss.xml to provide another
name "interest/Interest" to overwrite the standard behaviour with JNDI. We
also have the classes. It's time to package them together.</para>
</section>
+</section>
<section>
<title>Packaging and deploying the bean</title>
@@ -575,19 +580,27 @@
<literallayout><computeroutput>
[Auto deploy] Auto deploy of file:/usr/local/jboss/deploy/interest.jar
-[Container factory] Deploying:file:/usr/local/jboss/deploy/interest.jar
+[J2EE Deployer Default] Deploy J2EE application:
+file:/usr/local/jboss/deploy/interest.jar
+[J2EE Deployer Default] Create application interest.jar
+[J2EE Deployer Default] install module interest.jar
+[Container factory]
+Deploying:file:/usr/local/jboss/tmp/deploy/Default/interest.jar
+[Verifier] Verifying
+file:/usr/local/jboss/tmp/deploy/Default/interest.jar/ejb1001.jar
[Container factory] Deploying Interest
-[Container factory] Started: Interest
-[Container factory] Bound Interest to interest/Interest
-[Container factory] Deployed application:
-file:/usr/local/jboss/deploy/interest.jar
+[Container factory] Deployed application:
+file:/usr/local/jboss/tmp/deploy/Default/interest.jar
+[J2EE Deployer Default] J2EE application:
+file:/usr/local/jboss/deploy/interest.jar is deployed.
</computeroutput></literallayout>
<para>If you see a message like this: </para>
<literallayout><computeroutput>
-[Container factory] Deploying:file:/usr/local/jboss/deploy/interest.jar
-[Container factory] Deployed application
+[Auto deploy] Auto deploy of file:/usr/local/jboss/deploy/interest.jar
+[J2EE Deployer Default] Deploy J2EE application:
file:/usr/local/jboss/deploy/interest.jar
+[Auto deploy] Deployment failed:file:/usr/local/jboss/deploy/interest.jar
</computeroutput>
</literallayout>
@@ -618,7 +631,7 @@
<para>Here is the test client:</para>
-<figure><title>Test client</title>
+<figure><title>Test client, file name InterestClient.java</title>
<programlisting>
import javax.naming.*;
import com.web_tomorrow.interest.*;
@@ -690,7 +703,11 @@
}
</programlisting>
</figure>
-
+<para>Please note that the client tries to find
+<quote>interest/Interest</quote> via JNDI. Your bean has been bound to
+this name if you supplied a proper jboss.xml file. If not, the JNDI
+name will be just <quote>Interest</quote>. For the later case adjust
+the code please.</para>
<para>It's important to understand that in reality this client will be running
on a different computer to the Bean server. For testing you will probably run
them on the same computer, but it will still be using a network connection. So
@@ -736,8 +753,8 @@
find the EJB classes which are in the directories beneath it. </para>
-<para><command>javac -classpath /usr/local/jboss/client/ejb.jar:.
-InterestClient.java</command></para>
+<para><command>javac -classpath
+/usr/local/jboss/client/ejb.jar:. InterestClient.java</command></para>
<para>This generates InterestClient.class in the current directory. </para>
@@ -780,7 +797,8 @@
<literallayout><command>
java -classpath $CLASSPATH:\
-/usr/local/jboss/client/ejb.jar:/usr/local/jboss/client/jboss-client.jar \
+/usr/local/jboss/client/jboss-client.jar:\
+/usr/local/jboss/client/jbosssx-client.jar \
InterestClient</command>
</literallayout>
@@ -808,7 +826,7 @@
space).</para>
<para>Another common problem you can see here is a "class not found exception"
-make sure you include all the jars.</para>
+make sure you include all the jars needed.</para>
<para>The Bean should produce an output on the server as well; this is to show
that the Bean has executed on the server, not the client. Look for something
