User: gropi
Date: 01/10/01 01:57:09
Modified: src/xdocs jbossintro.xml
Log:
Some more comments on the JNDI service.
Revision Changes Path
1.3 +18 -14 manual/src/xdocs/jbossintro.xml
Index: jbossintro.xml
===================================================================
RCS file: /cvsroot/jboss/manual/src/xdocs/jbossintro.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- jbossintro.xml 2001/10/01 07:21:50 1.2
+++ jbossintro.xml 2001/10/01 08:57:09 1.3
@@ -12,6 +12,7 @@
<firstname>Tobias</firstname>
<surname>Frech</surname>
</author>
+ <email>[EMAIL PROTECTED]</email>
</para>
<para>
<author>
@@ -37,7 +38,7 @@
<title>About JBoss</title>
<para>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 the JBoss core server provides only an
EJB server.
+'J2SDK Enterprise Edition' (J2EE), but the JBoss core server provides only an EJB
server.
The JBoss core does not include a web container for servlets/JSP pages, although
there are
bundles available that include either Tomcat or Jetty.
@@ -56,7 +57,7 @@
already loaded, JBoss automatically unloads it, then loads the new
version. Contrast this with the rigmarole that other J2EE server makes us go
through...
JBoss is distributed under the LGPL, which means that it's free, even for commercial
-work, and is likely to remain that way. You get no support, of course. </para>
+work, and the LGPL ensures that it remains that way. Id you need support, look at
the JBoss website for the various forums. If you want to pay for the support then
contact the <ulink url = "http://www.jboss.org/JBG/support.jsp";>JBossGroup
LLC</ulink>.</para>
<para>This chapter helps get you started using JBoss
by describing step-by-step how a simple EJB can be created, deployed and
tested on the JBoss server. </para>
@@ -76,8 +77,8 @@
<title>Installing Ant</title>
<para>You need Ant to compile and run the example presented in the
JBoss documentation. Ant is
the standard build tool used by most open source Java projects and is widely being
used in commercial
-settings as well. You need Ant version 1.3 or latter. You can download the 1.3
binaries for Ant from <ulink url =
"http://jakarta.apache.org/builds/jakarta-ant/release/v1.3/bin/";>HERE</ulink>. If you
have problems finding
-binaries at that location try the Ant home page which is located <ulink url =
"http://jakarta.apache.org/ant/index.html";>HERE</ulink>.</para>
+settings as well. You need Ant version 1.3 or latter. You can download the 1.3
binaries for Ant from <ulink url =
"http://jakarta.apache.org/builds/jakarta-ant/release/v1.3/bin/";>this link to the
Apache/Jakarta website</ulink>. If you have problems finding
+binaries at that location try the Ant home page which is located <ulink url =
"http://jakarta.apache.org/ant/index.html";>on the Apache/Jakarta
website</ulink>.</para>
<para>Once you have the Ant distribution unarchive it to create a
jakarta-ant-1.3 directory. The Ant documentation
is located in the docs/manual directory. You should start with the
docs/manual/index.html file and browse through its
contents if you want to use Ant. You won't need to know anything about Ant build
scripts in order to compile and run
@@ -209,16 +210,15 @@
need to specify a CLASSPATH environment variable if you don't normally have
to.</para>
<para>The next step will be to download, install and test the JBoss
server. At
-the time of writing the most recent version of JBoss is 2.2.2.
+the time of updating this the most recent version of JBoss is 2.4.1.
It doesn't matter where you install JBoss. There is no requirement for root access
to
-run JBoss as none of the default ports are below the 1024 privaledged port range.
+run JBoss as none of the default ports are below the 1024 priveledged port range.
You will need to define a JBOSS_DIST environment variable that points to the
installation
location of the JBoss installation directory. This is required to build and run all
of the documentation
examples you will download later.</para>
<para>JBoss is distributed as a ZIP file. You can download the binary
-distribution which contains the latest offical release (which was 2.2.2
-at the time of writing) or a source snapshot with the latest
-version from CVS. This documentation mainly is written for the 2.2.2 version.</para>
+distribution which contains the latest offical release or a source snapshot with
the latest
+version from CVS. This documentation mainly was written for the 2.2.2 version and
contains some hints for the 2.4 and the unstable CVS version where needed. If you
discover anything that should be added or is outdated please make sure to contact the
jboss-docs mailing list which you can locate via the JBoss website.</para>
<section>
<title>Installation of binary package</title>
<para>Download the binary package from <ulink url =
"http://sourceforge.net/projects/jboss/";>
http://sourceforge.net/projects/jboss/</ulink> under the Latest File Releases section.
Place it in a temporary directory and use the
@@ -227,10 +227,13 @@
<para>Make sure, that this user has the JDK binaries in his
command path and that he has write access to the
JBoss directory (needed for log files and deployment).
You are now ready to change to the bin directory, and run the JBoss server: </para>
- <literallayout>On Unix/Linux:<command>cd JBOSS_DIST/bin
-/bin/sh run.sh</command>On Win32:<command>cd JBOSS_DIST\bin
+<literallayout>On Unix/Linux:
+<command>cd JBOSS_DIST/bin
+sh run.sh</command>
+On Win32:<command>
+cd JBOSS_DIST\bin
run.bat</command>
- </literallayout>
+</literallayout>
<para>A proper installation should start without any error
messages or exceptions being thrown. It will
produce several pages of output on startup. The console output should look
something like the following
at the start and end for JBoss-2.2.2 on Linux:<literallayout>
@@ -258,7 +261,7 @@
<title>Downloading the Documentation Example Source</title>
<para>The source code for all examples in the JBoss documentation are
available as a
single archive which can be downloaded documentation-example.zip or
documentation-example.tar.gz
-from files section on: <ulink url =
"http://www.jboss.org/doco_files/";>www.jboss.org</ulink>. You should
+from files section on <ulink url =
"http://www.jboss.org/doco_files/";>www.jboss.org</ulink>. You should
download the archive format of your choice and unpack the archive into an empty
directory. This will
create a directory structure like that shown in <xref linkend =
"intro.examples.structure"/>
</para>
@@ -297,10 +300,11 @@
packages. In the example, the classes are in the package
org.jboss.docs.interest, so they need to be in the directory
org/jboss/docs/interest/
which is what you will find in the examples distribution.</para>
- <para>You the ejb-jar archive is created there must be a directory
called META-INF
+ <para>Before the jar archive with all the classes is created there
must be a directory called META-INF
to store the deployment descriptor (always called ejb-jar.xml) and -- optionally --
another XML file
to tell the server about application specific server infomormation. With JBoss,
this file must be called
jboss.xml.</para>
+<para>The jar file you created is then deployed on the JBoss server. On the client
side you need a jndi.properties file that tells your client where to initially find
the JNDI naming service. From this service the client will look up the Interest bean
and get back the remote interface of the bean. He can now use this interface to access
the functions provided by the Enterprise Java Bean a.k.a EJB.</para>
</section>
<section>
<title>Review the EJB Classes</title>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
