User: fleury
Date: 01/02/07 21:31:44
Modified: manual adv_config.html architecture.html clients.html
config.html deploying.html developing.html
dtds.html ejx.html examples.html extending.html
future.html index.html install.html intro.html
jms.html license.html managing.html references.html
start_stop.html support.html third_party.html
trouble.html unix_start.html warning.html
Log:
jBoss -> JBoss
Revision Changes Path
1.6 +30 -30 newsite/manual/adv_config.html
Index: adv_config.html
===================================================================
RCS file: /products/cvs/ejboss/newsite/manual/adv_config.html,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- adv_config.html 2001/01/08 05:32:13 1.5
+++ adv_config.html 2001/02/08 05:31:40 1.6
@@ -1,10 +1,10 @@
<html>
<head>
- <title>jBoss 2.0: Advanced Configuration</title>
+ <title>JBoss 2.0: Advanced Configuration</title>
<link REL ="stylesheet" TYPE="text/css" HREF="manual.css" TITLE="Style" />
</head>
<body>
- <h1 ALIGN="CENTER">jBoss 2.0: Advanced Configuration</h1>
+ <h1 ALIGN="CENTER">JBoss 2.0: Advanced Configuration</h1>
<p>This section describes the configuration changes you might need
to make to support your application. It is still not
comprehensive, though. The final authority on what's possible
@@ -15,7 +15,7 @@
data sources for your EJBs. You must create a data source for
CMP entity beans, and it is the recommended way to interact with
a database for BMP entity beans and session beans.</p>
- <p>jBoss data sources provide database connection pooling. This
+ <p>JBoss data sources provide database connection pooling. This
means that when your application closes a connection, it is not
<em>really</em> closed, just returned to the "ready" state. The
next time your application requests a database connection, it may
@@ -25,11 +25,11 @@
period of time, the savings can be significant. However, there
are some new issues raised such as the fact that a database
connection that is left unused in the pool for a long period of
- time may timeout. The jBoss pools have a number of configuration
+ time may timeout. The JBoss pools have a number of configuration
parameters to address issues like this.</p>
<h3><a NAME="supported">Supported Databases</a></h3>
- <p>jBoss supports any database with a JDBC driver. We recommend
+ <p>JBoss supports any database with a JDBC driver. We recommend
pure java drivers (type 3 or type 4), and specifically suggest
you <em>do not</em> use the JDBC-ODBC bridge (type 1).</p>
@@ -41,13 +41,13 @@
Oracle 8, Sybase, DB2, and InterBase. Additional contributed
mappings include PointBase, SOLID, mySQL, MS SQL Server, and
DB2/400. If you would like to support CMP for another DBMS, or
- have a working mapping to share, please contact the jBoss
+ have a working mapping to share, please contact the JBoss
<a HREF="http://www.jboss.org/mailing.htm">Mailing List</a>.</p>
<h3><a NAME="installing">Installing JDBC Drivers</a></h3>
<p>To install a JDBC driver, it must be distributed as one or more
ZIP or JAR files. You should copy those files to the
- <strong>lib/ext</strong> directory under your jBoss installation
+ <strong>lib/ext</strong> directory under your JBoss installation
directory. In addition, you need to change one line in the file
<code>jboss.properties</code> located in the <strong>conf</strong>
directory. Find the property named <code>jdbc.drivers</code>, and
@@ -57,7 +57,7 @@
<pre>
jdbc.drivers=oracle.jdbc.driver.OracleDriver,com.sybase.jdbc2.jdbc.SybDriver
</pre>
- <p>The next time you start jBoss, you should see output like the
+ <p>The next time you start JBoss, you should see output like the
following listing each driver that was loaded. If instead you
see an error for the driver (also shown below), make sure that
you installed the required ZIPs and/or JARs to the
@@ -102,12 +102,12 @@
do a very good job yet (some Oracle implementations, in
particular, neglect important event notifications).</p>
<p>You must determine whether your driver supports the JDBC 2.0
- Optional Package in order to configure jBoss appropriately. If it
- does not, jBoss will simulate it so that your EJBs will operate
+ Optional Package in order to configure JBoss appropriately. If it
+ does not, JBoss will simulate it so that your EJBs will operate
appropriately, but there are two important restrictions:</p>
<ol>
<li>If you request more than one connection from a DataSource in
- the context of the same transaction, jBoss will return the same
+ the context of the same transaction, JBoss will return the same
connection every time. This is so changes made by one bean will
be visible to other beans operating in the same
transaction.</li>
@@ -137,7 +137,7 @@
<li>If your driver supports the JDBC 2.0 Optional Package, you
should use the class name of the vendor's XADataSource
implementation for the second argument. Otherwise, use the
- jBoss class name shown.</li>
+ JBoss class name shown.</li>
</ul>
<pre>
<MLET CODE="org.jboss.jdbc.XADataSourceLoader"
ARCHIVE="jboss.jar,<b>vendor.jar</b>" CODEBASE="../lib/ext/">
@@ -152,7 +152,7 @@
be covered in detail next. The block you need to add is shown
below. You only need to add lines for the parameters you want to
override - anything you want to leave as the default you can omit.
- jBoss will add all those lines in when it runs, so you can see the
+ JBoss will add all those lines in when it runs, so you can see the
default values. The example below is a simple configuration with
only the JDBC URL, user name, and password. The one thing you
need to change besides the parameter names and values is the pool
@@ -167,7 +167,7 @@
<h4><a NAME="params">Connection Pool Parameters</a></h4>
<p>Here is the list of possible parameters for each pool's entry
- in <code>jboss.jcml</code>. Again, after you run jBoss once with
+ in <code>jboss.jcml</code>. Again, after you run JBoss once with
your new pool, it will add entries for all of these to
<code>jboss.jcml</code>, using the default values for anything you
didn't specify.</p>
@@ -229,7 +229,7 @@
</tr>
<tr>
<td>LoggingEnabled</td>
- <td>Whether the pool should record activity to the jBoss log.
+ <td>Whether the pool should record activity to the JBoss log.
This includes events like connections being checked out and
returned. It is generally only useful for troubleshooting
purposes (to find a connection leak, etc.).</td>
@@ -717,7 +717,7 @@
<h2><a NAME="security">Security</a></h2>
- <p>You can set users and roles in the jBoss server, and then use
+ <p>You can set users and roles in the JBoss server, and then use
them to control access to your beans. Currently, the only way
to configure users and roles is to set up a table in a database,
though there will be additional security implementations in a
@@ -728,10 +728,10 @@
<h2><a NAME="logging">Logging</a></h2>
- <p>jBoss has a configurable logging system. You can adjust both
+ <p>JBoss has a configurable logging system. You can adjust both
the content that is logged and the destination of the log
output. Currently there are 3 logging implementations
- included in jBoss - you can log to the console, to a file, or
+ included in JBoss - you can log to the console, to a file, or
to a Swing GUI. The logging system can easily support additional
log destinations, such as a database or message queue. By
default, console and file logging are enabled.</p>
@@ -890,8 +890,8 @@
<h2><a NAME="jms">Configuring JMS</a></h2>
<p><i>This section is forthcoming.</i></p>
- <h2><a NAME="multiple">Running Multiple jBoss Servers on One Machine</a></h2>
- <p>It is possible to run jBoss more than once on the same machine.
+ <h2><a NAME="multiple">Running Multiple JBoss Servers on One Machine</a></h2>
+ <p>It is possible to run JBoss more than once on the same machine.
There are two way to do this: running two instances out of the
same installation directory, and setting up separate installation
directories. In either case, you will need to change all the default
@@ -901,7 +901,7 @@
server. Follow the instructions below to change the default
ports.<p>
- <p>If you run jBoss more than once from the same directory
+ <p>If you run JBoss more than once from the same directory
structure, you will need to use a second set of configuration
files (see <a HREF="config.html#files">Configuration Files</a>).
You will also need to remove all the
@@ -916,19 +916,19 @@
<pre>
<ARG TYPE="java.lang.String" VALUE="<b>../otherDeployDir/</b>">
</pre>
- <p>If you run jBoss more than once from separate directories,
+ <p>If you run JBoss more than once from separate directories,
you can choose to remove the <code><RMIObjectPort></code>
tags as above, or just change the port for all additional
servers. You must change it one way or another, because
only one VM can use the same port.</p>
<h2><a NAME="ports">Changing Defalt Port Assignments</a></h2>
- <p>jBoss uses four ports, by default. The JNDI server listens on
+ <p>JBoss uses four ports, by default. The JNDI server listens on
port 1099 for JNDI requests, the management interface listens on
port 8082 for JMX requests, the RMI server listens on port
1083 for RMI class requests, and the RMI objects listen on port
4444. If you change any of the ports, you must restart the
- jBoss server for the changes to take effect.</p>
+ JBoss server for the changes to take effect.</p>
<p>To change the JNDI port, edit the file
<code>jnp.properties</code> in the <strong>conf</strong>
directory. Change the line <code>jnp.port</code> to the port you
@@ -965,9 +965,9 @@
configuration. If you remove the tag altogether, the objects
will each use a different port (just picking one that's
available). You can also override this port setting in
- custom container configurations declared in the jBoss
+ custom container configurations declared in the JBoss
Deployment Descriptor (see <a HREF="deploying.html#jboss">The
- jBoss Deployment Descriptor</a>) - but you cannot force it
+ JBoss Deployment Descriptor</a>) - but you cannot force it
to use anonymous ports, just select a different port to share.
Your clients should use the new port automatically.</p>
@@ -983,7 +983,7 @@
contact with the server.</p>
<h2><a NAME="custom">Custom MBeans</a></h2>
- <p>If you want to add services to the jBoss server, the best way
+ <p>If you want to add services to the JBoss server, the best way
to do that is to write your own JMX MBeans. Then they can be
loaded in <code>jboss.conf</code> and configured in
<code>jboss.jcml</code> like the existing MBeans. The best way
@@ -1009,7 +1009,7 @@
in <code>jboss.dependencies</code>.</p>
<h2><a NAME="third">Third-Party Products</a></h2>
- <p>jBoss already integrates with a number of third-party products
+ <p>JBoss already integrates with a number of third-party products
(see <a HREF="third_party.html">Third-Party Software</a>). If you
are using a product that is not yet supported, your integration
strategy will depend on the nature of the product. But again,
@@ -1019,8 +1019,8 @@
specify configuration information in an XML file for each EJB JAR,
depending on whether the configuration should be at the bean level
or at the server level.</p>
- <p>If you integrate a new product with jBoss, please let us know on
- the jBoss <a HREF="http://www.jboss.org/mailing.htm">Mailing
+ <p>If you integrate a new product with JBoss, please let us know on
+ the JBoss <a HREF="http://www.jboss.org/mailing.htm">Mailing
List</a>.</p>
</body>
</html>
1.2 +2 -2 newsite/manual/architecture.html
Index: architecture.html
===================================================================
RCS file: /products/cvs/ejboss/newsite/manual/architecture.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- architecture.html 2000/11/12 20:32:05 1.1
+++ architecture.html 2001/02/08 05:31:40 1.2
@@ -1,9 +1,9 @@
<html>
<head>
- <title>jBoss 2.0: Architecture</title>
+ <title>JBoss 2.0: Architecture</title>
<link REL ="stylesheet" TYPE="text/css" HREF="manual.css" TITLE="Style" />
</head>
<body>
- <h1 ALIGN="CENTER">jBoss 2.0: Architecture</h1>
+ <h1 ALIGN="CENTER">JBoss 2.0: Architecture</h1>
</body>
</html>
1.2 +28 -28 newsite/manual/clients.html
Index: clients.html
===================================================================
RCS file: /products/cvs/ejboss/newsite/manual/clients.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- clients.html 2000/11/12 20:32:06 1.1
+++ clients.html 2001/02/08 05:31:40 1.2
@@ -1,14 +1,14 @@
<html>
<head>
- <title>jBoss 2.0: jBoss Clients</title>
+ <title>JBoss 2.0: JBoss Clients</title>
<link REL ="stylesheet" TYPE="text/css" HREF="manual.css" TITLE="Style" />
</head>
<body>
- <h1 ALIGN="CENTER">jBoss 2.0: jBoss Clients</h1>
- <p>Virtually any type of Java client can be a jBoss client. There
+ <h1 ALIGN="CENTER">JBoss 2.0: JBoss Clients</h1>
+ <p>Virtually any type of Java client can be a JBoss client. There
are several requirements for an EJB client:</p>
<ul>
- <li>The client must have the jBoss client JARs and certain J2EE
+ <li>The client must have the JBoss client JARs and certain J2EE
specification JARs available (unless you use the advanced
dynamic classloading techniques)</li>
<li>You must provide JNDI settings to contact the server</li>
@@ -17,11 +17,11 @@
etc.</li>
</ul>
<p>These requirements are the same across all types of clients,
- though each may differ in implementation (how to distribute jBoss
+ though each may differ in implementation (how to distribute JBoss
client JARs, for example).</p>
<h2><a NAME="jdk">Supported Java Versions</a></h2>
- <p>jBoss supports Java 2 (currently, JDK 1.2.2-1.3.0). There has
+ <p>JBoss supports Java 2 (currently, JDK 1.2.2-1.3.0). There has
been speculation that it may work under Java 1.x, but this is
not currently a supported platform. If your server is configured
for 1.3, then all clients must use 1.3. If your server is
@@ -65,7 +65,7 @@
per lookup. If the client uses EJBs or other resource on more
than one JNDI server at the same time, however, this is the way
you'll have to do it.</p>
- <p>Here are the required properties for jBoss:</p>
+ <p>Here are the required properties for JBoss:</p>
<table BORDER="1">
<tr><th>property</th><th>value</th></tr>
<tr>
@@ -123,7 +123,7 @@
a custom JAR without the EJB implementations, deployment
descriptors, etc.</p>
<table BORDER="1">
- <tr><th>JAR Name</th><th>Contents</th><th>jBoss-Specific</th></tr>
+ <tr><th>JAR Name</th><th>Contents</th><th>JBoss-Specific</th></tr>
<tr>
<td>jnp-client.jar</td>
<td>JNDI Client Implementation</td>
@@ -131,7 +131,7 @@
</tr>
<tr>
<td>jboss-client.jar</td>
- <td>jBoss client code</td>
+ <td>JBoss client code</td>
<td>Yes</td>
</tr>
<tr>
@@ -164,19 +164,19 @@
via the Java Plug-In. In either case, you will most likely
need to sign your Applet to grant it the network, file, and/or
system property permissions it requires to configure JNDI and
- communicate with the jBoss server. It may be possible to use
+ communicate with the JBoss server. It may be possible to use
an unsigned applet, but we have not tried it.</p>
<h3><a NAME="browser">Browser Native</a></h2>
<p>Current browsers support some or all of JDK 1.1. Since that
- is not a supported client environment for jBoss, you should
+ is not a supported client environment for JBoss, you should
use the plug-in if at all possible. If you do decide to try
to use the native JVM, be aware that the security
configuration differs by browser, and a browser may or may not
support the permissions required.</p>
<h3><a NAME="plug-in">Java Plug-In</a></h2>
- <p>The Java Plug-In is the recommended method of running jBoss
+ <p>The Java Plug-In is the recommended method of running JBoss
applet clients. You should sign your applet in order to
grant it the required security permissions. For signing
applets for the plug-in, you should seriously consider using
@@ -202,17 +202,17 @@
<h2><a NAME="servlet">Servlet & JSP Clients</a></h2>
<p>Servlets and JSPs may use EJBs. There are two ways to install
- a Servlet engine with jBoss. However, there is one common
- requirement: Make sure that you install the jBoss libraries
+ a Servlet engine with JBoss. However, there is one common
+ requirement: Make sure that you install the JBoss libraries
and your EJB interface classes at the same level in your
- Servlet engine. For example, do not install the jBoss
+ Servlet engine. For example, do not install the JBoss
libraries as global libraries, but the EJB classes as local to
a specific web app or servlet context. You can either install
all at the server level, or all at the web app/context level,
and we recommend the latter.</p>
<p>The rest of this topic degenerates rapidly into technical
details. We would encourage you to use a Servlet engine that
- is already supported in jBoss, such as Tomcat. In that case,
+ is already supported in JBoss, such as Tomcat. In that case,
the configuration information presented in the
<a HREF="third_party.html">Third-Party Software</a> section
will resolve all the issues described below.</p>
@@ -220,19 +220,19 @@
<h3><a NAME="techie">Servlet Engine Integration: Technical Details</a></h2>
<p>As for the specific Servlet engine installation options, the
first option is to install the Servlet engine completely
- separately from jBoss, even if they run on the same machine.
+ separately from JBoss, even if they run on the same machine.
The performance is typically worse for this environment, but
it is easier to configure since the servlets can be treated as
any other client. Additionally, this may provide better
- stability and/or security, since the Servlet engine and jBoss
+ stability and/or security, since the Servlet engine and JBoss
communicate only over the network. The main issue to be
aware of in this case are the security settings on your
servlets - make sure they have network access to communicate
- with the jBoss server.</p>
- <p>The other way is to run jBoss and the Servlet engine in the
+ with the JBoss server.</p>
+ <p>The other way is to run JBoss and the Servlet engine in the
same JVM. This provides greater performance since it can avoid
networking operations, but is more difficult to configure, and
- errors in the Servlet engine or jBoss could potentially
+ errors in the Servlet engine or JBoss could potentially
incapacitate both. In this case, you will have to make sure to
configure the ClassLoader for your servlets appropriately. Many
Servlet engines use a number of ClassLoaders, and it may be the
@@ -248,15 +248,15 @@
you use the same ClassLoader for servlets and EJBs, you can
replace all network calls with VM local calls, and reduce the
need for serialization. This may be difficult to achieve,
- however, since either jBoss must dig into the Servlet engine and
+ however, since either JBoss must dig into the Servlet engine and
grab the appropriate ClassLoader for an EJB JAR, or vice
versa.</p>
<h2><a NAME="corba">CORBA Clients</a></h2>
- <p>jBoss does not currently support IIOP, so you will not be able
+ <p>JBoss does not currently support IIOP, so you will not be able
to interact directly with EJBs via CORBA. However, you could
certainly create a CORBA service that used the normal JNDI
- mechanisms to communicate with EJBs on jBoss, and then make
+ mechanisms to communicate with EJBs on JBoss, and then make
that service available to CORBA clients.</p>
<h2><a NAME="ejb">EJB Clients</a></h2>
@@ -265,8 +265,8 @@
in your EJB 1.1 deployment descriptor (see the
<a HREF="deploying.html#ejb11">EJB 1.1 Deployment Descriptor</a>),
and the point it to the correct home interface for the referenced
- EJB in the jBoss deployment descriptor (see the
- <a HREF="deploying.html#jboss">jBoss Deployment Descriptor</a>).
+ EJB in the JBoss deployment descriptor (see the
+ <a HREF="deploying.html#jboss">JBoss Deployment Descriptor</a>).
Then you just look up the other EJB home using the
<code>java:comp/env</code> namespace, and go from there.</p>
<p>Of course, you will still need the home and remote interfaces for
@@ -275,9 +275,9 @@
either add the classes for the referenced EJB to the JAR of the
referencing EJB, or if they are deployed together you can add a
classpath entry to the manifest file for the referencing EJB's JAR.
- And finally, if the referenced EJB is not in a jBoss server, you
+ And finally, if the referenced EJB is not in a JBoss server, you
may need additional JNDI configuration, and you may need client
- JARs for the other server to be available to jBoss. This is not
+ JARs for the other server to be available to JBoss. This is not
likely to work if the servers support different versions of the
EJB specification.</p>
</body>
1.2 +9 -9 newsite/manual/config.html
Index: config.html
===================================================================
RCS file: /products/cvs/ejboss/newsite/manual/config.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- config.html 2000/11/12 20:32:07 1.1
+++ config.html 2001/02/08 05:31:40 1.2
@@ -1,11 +1,11 @@
<html>
<head>
- <title>jBoss 2.0: Basic Configuration</title>
+ <title>JBoss 2.0: Basic Configuration</title>
<link REL ="stylesheet" TYPE="text/css" HREF="manual.css" TITLE="Style" />
</head>
<body>
- <h1 ALIGN="CENTER">jBoss 2.0: Basic Configuration</h1>
- <p>jBoss ships preconfigured, so there's nothing you need to do to
+ <h1 ALIGN="CENTER">JBoss 2.0: Basic Configuration</h1>
+ <p>JBoss ships preconfigured, so there's nothing you need to do to
get it up and running with the test beans. However, you will
likely need to make minor configuration changes to support your
specific applications. This section gives an overview of the
@@ -17,7 +17,7 @@
<h2><a NAME="dirs">Important Directories</a></h2>
<p>The directory names given here are all relative to the directory
- you installed jBoss into.</p>
+ you installed JBoss into.</p>
<h3><a NAME="exes">Executables</a></h3>
<p>Executables are located in the <strong>bin</strong> directory.
@@ -40,7 +40,7 @@
need to be available to all EJBs; there are alternatives for
libraries that should be available to individual EJB JARs
(see <a HREF="deploying.html#manifest">The Manifest File</a> in
- the <a HREF="deploying.html">Deploying EJBs in jBoss</a>
+ the <a HREF="deploying.html">Deploying EJBs in JBoss</a>
section).</p>
<h3><a NAME="ejbs">EJBs</a></h3>
@@ -58,7 +58,7 @@
<code>jndi.jar</code> as well.</p>
<h2><a NAME="files">Configuration Files</a></h2>
- <p>There are a number of configuration files for jBoss. The
+ <p>There are a number of configuration files for JBoss. The
contents of each are give here, though you should refer to
the <a HREF="adv_config.html">Advanced Configuration</a> section
and the <a HREF="dtds.html">DTDs</a> section of the Appendix for
@@ -70,7 +70,7 @@
<code>myconfig.conf</code>, <code>myconfig.jcml</code>, ...
To start jboss with a different set of configuration files,
add the base name of the configuration file set to the command
- or script you use to start jBoss (for example,
+ or script you use to start JBoss (for example,
"<code>run.sh myconfig</code>").</p>
<table BORDER="1">
<tr><th>File Name</th><th>Purpose</th></tr>
@@ -110,7 +110,7 @@
</tr>
<tr>
<td>server.policy</td>
- <td>The default security policy for the jBoss server.
+ <td>The default security policy for the JBoss server.
Currently, this is set to allow all permissions. In a future
release it will be locked down more.</td>
</tr>
@@ -118,7 +118,7 @@
<h2><a NAME="remote">Clients on Remote Machines</a></h2>
<p>The default configuration assumes client will run on the same
- machine as the jBoss server. While often appropriate for servlet
+ machine as the JBoss server. While often appropriate for servlet
and JSP clients, you need to make minor changes to support remote
clients.</p>
<ol>
1.2 +21 -21 newsite/manual/deploying.html
Index: deploying.html
===================================================================
RCS file: /products/cvs/ejboss/newsite/manual/deploying.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- deploying.html 2000/11/12 20:32:08 1.1
+++ deploying.html 2001/02/08 05:31:40 1.2
@@ -1,11 +1,11 @@
<html>
<head>
- <title>jBoss 2.0: Deploying EJBs in jBoss</title>
+ <title>JBoss 2.0: Deploying EJBs in JBoss</title>
<link REL ="stylesheet" TYPE="text/css" HREF="manual.css" TITLE="Style" />
</head>
<body>
- <h1 ALIGN="CENTER">jBoss 2.0: Deploying EJBs in jBoss</h1>
- <p>In order to make an EJB available through jBoss, you need to
+ <h1 ALIGN="CENTER">JBoss 2.0: Deploying EJBs in JBoss</h1>
+ <p>In order to make an EJB available through JBoss, you need to
package it into a JAR file, and then put that JAR file in the
<strong>deploy</strong> directory. This section has the details
on what needs to go into the JAR file, how to prepare it, what to
@@ -53,10 +53,10 @@
was often a serialized Java class, with other vendor-specific
files or classes. In the EJB 1.1 specification, the EJB
deployment descriptor is an XML file. Any vendor-specific
- extensions may use any format, but in the case of jBoss, they are
- also XML files. So to deploy in jBoss, you need the one standard
+ extensions may use any format, but in the case of JBoss, they are
+ also XML files. So to deploy in JBoss, you need the one standard
EJB 1.1 deployment descriptor, and then up to two other
- jBoss-specific XML deployment descriptors, depending on the
+ JBoss-specific XML deployment descriptors, depending on the
type of EJB and the features it will use.</p>
<p>The three possible deployment descriptors are described next.
If you need specific details, you can refer to the
@@ -75,14 +75,14 @@
information should be the same no matter what EJB server you
deploy in.</p>
- <h4><a NAME="jboss">The jBoss Deployment Descriptor</a></h4>
- <p>The jBoss Deployment Descriptor (<code>jboss.xml</code>) is
+ <h4><a NAME="jboss">The JBoss Deployment Descriptor</a></h4>
+ <p>The JBoss Deployment Descriptor (<code>jboss.xml</code>) is
optional. There are default settings, and you only need to
include this file if you want to override the defaults. Further,
you only need to include any sections within this file that
differ from the defaults, so you do not need a new complete
configuration file for every JAR.</p>
- <p>The jBoss deployment descriptor handle the following
+ <p>The JBoss deployment descriptor handle the following
settings:</p>
<ul>
<li>The JNDI name for the EJBs in the JAR</li>
@@ -129,7 +129,7 @@
<h4><a NAME="jaws">The JAWS Deployment Descriptor</a></h4>
<p>The JAWS Deployment Descriptor (<code>jaws.xml</code>) is used
- by the default jBoss Container-Managed Persistence engine. So
+ by the default JBoss Container-Managed Persistence engine. So
this file is only used for CMP Entity Beans. Again, there are
default settings, and you only need to include this file if you
want to override the defaults. Further, you only need to include
@@ -158,7 +158,7 @@
for each CMP Entity Bean that uses JAWS.</p>
<h4><a NAME="ejx">Editing Deployment Descriptors with EJX</a></h4>
- <p>jBoss includes a graphical tool to edit deployment descriptors,
+ <p>JBoss includes a graphical tool to edit deployment descriptors,
called EJX (Enterprise Java XML-editor). You can edit all three
types of deployment descriptors with EJX. EJX can either read
and write XML files on disk, or read and write XML files in an
@@ -195,12 +195,12 @@
accomplish that.</p>
<h2><a NAME="deploying">Deploying Your EJB JAR</a></h2>
- <p>Deploying an EJB JAR in jBoss is simple. Once you have packaged
+ <p>Deploying an EJB JAR in JBoss is simple. Once you have packaged
the classes and deployment descriptors in a JAR, copy that JAR to
- the <strong>deploy</strong> directory. If jBoss is running, it
+ the <strong>deploy</strong> directory. If JBoss is running, it
will deploy the JAR automatically. If not, it will deploy the
JAR the next time you start it. You can use the management
- interface (see <a HREF="managing.html">Managing a Live jBoss
+ interface (see <a HREF="managing.html">Managing a Live JBoss
Server</a>) to manually deploy JARs from different locations, but
copying the JARs to the deploy directory is the recommended way to
deploy. No matter how you deploy, all the EJBs in an EJB JAR are
@@ -216,8 +216,8 @@
<a HREF="trouble.html">Troubleshooting</a> section.</p>
<h3><a NAME="files">Strange File Names</a></h3>
- <p>You may notice that the jBoss server refers to an EJB JAR by a
- cryptic name. The reason is the jBoss does not want to lock files
+ <p>You may notice that the JBoss server refers to an EJB JAR by a
+ cryptic name. The reason is the JBoss does not want to lock files
in the deployment directory and prevent you from updating them, so
it makes copies in a temporary directory with cryptic names. This
is not the cause of a deployment failure.</p>
@@ -254,14 +254,14 @@
<a HREF="#ejb11">The EJB 1.1 Deployment Descriptor</a>). Also,
note that you must define the target data source or EJB in the
<code>jboss.xml</code> file (see
- <a HREF="#jboss">The jBoss Deployment Descriptor</a>).</p>
+ <a HREF="#jboss">The JBoss Deployment Descriptor</a>).</p>
<h2><a NAME="undeploy">Undeploying EJBs</a></h2>
<p>To undeploy an EJB, delete the EJB JAR file in the
<strong>deploy</strong> directory. You can also undeploy JARs
using the management interface, and that is the only option if
you manually deployed a JAR in a different location (see
- <a HREF="managing.html">Managing a Live jBoss Server</a>).</p>
+ <a HREF="managing.html">Managing a Live JBoss Server</a>).</p>
<h2><a NAME="redeploy">Redeploying Existing EJBs</a></h2>
<p>To redeploy an EJB, copy a new EJB JAR file to the
@@ -270,13 +270,13 @@
versions deployed. You can also undeploy JARs using the
management interface, and that is the only option if you manually
deployed a JAR in a different location (see
- <a HREF="managing.html">Managing a Live jBoss Server</a>).</p>
+ <a HREF="managing.html">Managing a Live JBoss Server</a>).</p>
<h2><a NAME="hot">Hot Deployment</a></h2>
- <p>jBoss always hot deploys and EJB JARs copied into the
+ <p>JBoss always hot deploys and EJB JARs copied into the
<strong>deploy</strong> directory, so there are not special
procedures for hot deployment. If you want a strictly manual
deploy and undeploy process, use the management interface (see
- <a HREF="managing.html">Managing a Live jBoss Server</a>).</p>
+ <a HREF="managing.html">Managing a Live JBoss Server</a>).</p>
</body>
</html>
1.2 +21 -21 newsite/manual/developing.html
Index: developing.html
===================================================================
RCS file: /products/cvs/ejboss/newsite/manual/developing.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- developing.html 2000/11/12 20:32:09 1.1
+++ developing.html 2001/02/08 05:31:40 1.2
@@ -1,11 +1,11 @@
<html>
<head>
- <title>jBoss 2.0: Writing EJBs</title>
+ <title>JBoss 2.0: Writing EJBs</title>
<link REL ="stylesheet" TYPE="text/css" HREF="manual.css" TITLE="Style" />
</head>
<body>
- <h1 ALIGN="CENTER">jBoss 2.0: Writing EJBs</h1>
- <p>This section is not specific to jBoss. Since EJB is an open
+ <h1 ALIGN="CENTER">JBoss 2.0: Writing EJBs</h1>
+ <p>This section is not specific to JBoss. Since EJB is an open
specification, the process of writing EJBs is the same across
all servers that support the same revision of the spec. If you're
familiar with EJBs, this will basically be review, just hitting
@@ -21,11 +21,11 @@
<a HREF="http://java.sun.com/products/ejb/docs.html">EJB 1.1
Specification</a>.</p>
- <h2><a NAME="ejb11">jBoss 2.0 Supports EJB 1.1</a></h2>
+ <h2><a NAME="ejb11">JBoss 2.0 Supports EJB 1.1</a></h2>
<p>The first revision of the EJB spec to be widely implemented was
EJB 1.0. However, the current revision is EJB 1.1, and that is
- what jBoss 2.0 supports. At this time, the EJB 2.0 spec has
- reached the public draft stage, so it is likely that jBoss 3.x
+ what JBoss 2.0 supports. At this time, the EJB 2.0 spec has
+ reached the public draft stage, so it is likely that JBoss 3.x
will support the EJB 2.0 specification. If you'd like to review
the EJB 1.1 specification it is
<a HREF="http://java.sun.com/products/ejb/docs.html">available
@@ -34,23 +34,23 @@
<h2><a NAME="entity">Entity Beans</a></h2>
<p>Entity Bean support is required in the EJB 1.1 specification, and
- jBoss fully supports entity beans. Entity beans can be broken
+ JBoss fully supports entity beans. Entity beans can be broken
down into two types, depending on the persistance mechanism they
use. Container-managed persistance (CMP) beans rely on the server
to handle all persistance - saving, loading, looking for specific
instances, etc. Bean-managed persistance (BMP) beans handle
- persistence on their own - you must code it all. jBoss supports
+ persistence on their own - you must code it all. JBoss supports
both types of entity beans.</p>
<h3><a NAME="cmp">CMP Entity Beans</a></h3>
<p>If you use CMP entity beans, the persistance of you beans is
- controlled in jBoss by a CMP Persistance Manager. The default
- CMP Persistance Manager in jBoss is known as JAWS. There are
+ controlled in JBoss by a CMP Persistance Manager. The default
+ CMP Persistance Manager in JBoss is known as JAWS. There are
also several third-party persistance managers that you can use
- with jBoss (see <a HREF="third_party.html">Third-Party
+ with JBoss (see <a HREF="third_party.html">Third-Party
Software</a>), but there is no difference until you actually
deploy your beans (see <a HREF="deploying.html">Deploying EJBs in
- jBoss</a>).</p>
+ JBoss</a>).</p>
<p>The common requirements for CMP beans are that all the persistant
fields be public and non-static. If you want them to map directly
into database types, be sure to use Java types that JDBC is aware
@@ -184,14 +184,14 @@
Enumerations for finders that return multiple results.</p>
<h2><a NAME="session">Session Beans</a></h2>
- <p>jBoss supports both Stateful and Stateless session beans.
+ <p>JBoss supports both Stateful and Stateless session beans.
Stateful beans will associate one bean with one client until
the client releases it, while stateless beans may be shared
- among a number of clients. jBoss creates a pool of beans to
+ among a number of clients. JBoss creates a pool of beans to
share between clients, to reduce the memory usage of the server
as a whole. To change the pooling characteristics of a session
bean, you need to change the deployment descriptor (see
- <a HREF="deploying.html#jboss">The jBoss Deployment
+ <a HREF="deploying.html#jboss">The JBoss Deployment
Descriptor</a>).</p>
<h2><a NAME="env">Using Environment Settings</a></h2>
@@ -225,7 +225,7 @@
Descriptor</a>). They are also stored under the
<code>java:comp/env</code> namespace. The EJB specification
recommends that you begin the name of your data source with
- "<code>jdbc/</code>", but that is not required. jBoss will
+ "<code>jdbc/</code>", but that is not required. JBoss will
<em>not</em> automatically add the <code>jdbc/</code> prefix; you
must include it in the name of your Data Source if you want it to
be there.</p>
@@ -273,7 +273,7 @@
<a HREF="deploying.html#ejb11">The EJB 1.1 Deployment
Descriptor</a>). The EJB specification recommends that you begin
the name of your EJB reference with "<code>ejb/</code>", but that
- is not required. jBoss will <em>not</em> automatically add the
+ is not required. JBoss will <em>not</em> automatically add the
<code>ejb/</code> prefix; you must include it in the name of your
EJB reference if you want it to be there.</p>
<p>For example, let's say you want the current EJB to use another
@@ -289,18 +289,18 @@
<h2><a NAME="trans">Transactions</a></h2>
<p>There are three approaches to transactions. In any of these
- cases, jBoss will handle propogating the current transaction to
+ cases, JBoss will handle propogating the current transaction to
other beans or data sources you use, subject to their
transaction configuration. The different between the three
approaches is what is responsible for creating transactions,
and then committing or rolling back when the work has
finished.</p>
<p>The first option is container-managed transaction demarcation.
- In this case, you can let jBoss handle everything. You specify
+ In this case, you can let JBoss handle everything. You specify
the transaction settings for each bean method in the deployment
descriptor (see
<a HREF="deploying.html#ejb11">The EJB 1.1 Deployment
- Descriptor</a>). In this case jBoss handles creating, committing,
+ Descriptor</a>). In this case JBoss handles creating, committing,
and rolling back transactions.</p>
<p>The other two options, bean-demarcated transactions and
client-demarcated transactions, are closeley related. In these
@@ -317,7 +317,7 @@
applicable to EJBs. An EJB can use the
<code>getUserTransaction()</code> method of its
<code>EJBContext</code>.</p>
- <p><i><b>Note:</b> The current jBoss beta does not allow JNDI
+ <p><i><b>Note:</b> The current JBoss beta does not allow JNDI
access, so client-demarcated transactions are not
possible.</i></p>
</body>
1.2 +2 -2 newsite/manual/dtds.html
Index: dtds.html
===================================================================
RCS file: /products/cvs/ejboss/newsite/manual/dtds.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- dtds.html 2000/11/12 20:32:09 1.1
+++ dtds.html 2001/02/08 05:31:40 1.2
@@ -1,9 +1,9 @@
<html>
<head>
- <title>jBoss 2.0: DTDs</title>
+ <title>JBoss 2.0: DTDs</title>
<link REL ="stylesheet" TYPE="text/css" HREF="manual.css" TITLE="Style" />
</head>
<body>
- <h1 ALIGN="CENTER">jBoss 2.0: DTDs</h1>
+ <h1 ALIGN="CENTER">JBoss 2.0: DTDs</h1>
</body>
</html>
1.2 +2 -2 newsite/manual/ejx.html
Index: ejx.html
===================================================================
RCS file: /products/cvs/ejboss/newsite/manual/ejx.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- ejx.html 2000/11/12 20:32:09 1.1
+++ ejx.html 2001/02/08 05:31:40 1.2
@@ -1,9 +1,9 @@
<html>
<head>
- <title>jBoss 2.0: EJX Walkthrough</title>
+ <title>JBoss 2.0: EJX Walkthrough</title>
<link REL ="stylesheet" TYPE="text/css" HREF="manual.css" TITLE="Style" />
</head>
<body>
- <h1 ALIGN="CENTER">jBoss 2.0: EJX Walkthrough</h1>
+ <h1 ALIGN="CENTER">JBoss 2.0: EJX Walkthrough</h1>
</body>
</html>
1.2 +53 -53 newsite/manual/examples.html
Index: examples.html
===================================================================
RCS file: /products/cvs/ejboss/newsite/manual/examples.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- examples.html 2000/11/12 20:32:11 1.1
+++ examples.html 2001/02/08 05:31:40 1.2
@@ -1,15 +1,15 @@
<html>
<head>
- <title>jBoss 2.0: Examples</title>
+ <title>JBoss 2.0: Examples</title>
<link REL ="stylesheet" TYPE="text/css" HREF="manual.css" TITLE="Style" />
</head>
<body>
- <h1 ALIGN="CENTER">jBoss 2.0: Examples</h1>
+ <h1 ALIGN="CENTER">JBoss 2.0: Examples</h1>
<h2><a NAME="petstore">J2EE Blueprints: Pet Store</a></h2>
<p>One common example is the Pet Store web app that Sun created
as part of the "J2EE Blueprints" package. It assumes you're
- using the J2EE RI server, but it can be adapted to jBoss and
+ using the J2EE RI server, but it can be adapted to JBoss and
Tomcat. The changes are not trivial, but are certainly
possible. These directions are for UNIX, but if you can
convert a shell script to a batch file then you'll be fine on
@@ -21,19 +21,19 @@
<ol>
<li><a HREF="#petstore1">Download the Pet Store</a></li>
<li><a HREF="#petstore2">Download ANT</a></li>
- <li><a HREF="#petstore3">Get The jBoss Petstore Package</a></li>
+ <li><a HREF="#petstore3">Get The JBoss Petstore Package</a></li>
<li><a HREF="#petstore4">Resolve the Catalog DB Situation</a></li>
<li><a HREF="#petstore5">Resolve the Account Situation</a></li>
<li><a HREF="#petstore6">Resolve the JNDI Situation</a></li>
<li><a HREF="#petstore6.5">Resolve the Logoff Situation</a></li>
<li><a HREF="#petstore7">Prepare the Database</a></li>
- <li><a HREF="#petstore8">Add DB Pool to jBoss</a></li>
+ <li><a HREF="#petstore8">Add DB Pool to JBoss</a></li>
<li><a HREF="#petstore9">Correct the Server Name</a></li>
- <li><a HREF="#petstore10">Add the jBoss-specific EJB directives</a></li>
+ <li><a HREF="#petstore10">Add the JBoss-specific EJB directives</a></li>
<li><a HREF="#petstore11">Build and Deploy</a></li>
<li><a HREF="#petstore12">Add User Accounts to Tomcat</a></li>
<li><a HREF="#petstore13">Add EJB Libraries to Tomcat</a></li>
- <li><a HREF="#petstore14">Start jBoss</a></li>
+ <li><a HREF="#petstore14">Start JBoss</a></li>
<li><a HREF="#petstore15">Start Tomcat</a></li>
<li><a HREF="#petstore16">Run the Pet Store</a></li>
</ol>
@@ -51,15 +51,15 @@
the build.sh script (you will need an XML parser in your
classpath).</p>
- <h3><a NAME="petstore3">Get The jBoss Petstore Package</a></h3>
+ <h3><a NAME="petstore3">Get The JBoss Petstore Package</a></h3>
<p>You can make a bunch of changes yourself, but to save you some
time we wrapped some of them together. Download the
- <a HREF="jboss-petstore.tgz">jBoss Petstore Package</a>. You
+ <a HREF="jboss-petstore.tgz">JBoss Petstore Package</a>. You
can open it with tar on UNIX or WinZip on Windows. Unpack it
into the main petstore directory created above - it will create
the src/jboss directory within the pet store. This directory
has updated ANT build scripts, updated shell scripts, and
- Tomcat and jBoss configuration files. There are a number of
+ Tomcat and JBoss configuration files. There are a number of
changes you need to make to the files in here to customize
them to your environment:</p>
<p>You need to edit the <b>build.sh</b> file and
@@ -73,21 +73,21 @@
variable should point to where you downloaded ANT above.</p>
<p><i><b>Note:</b> You should not use the j2ee.jar distributed with
the J2EE Reference Implementation - use the individual packages
- available from Tomcat or jBoss or Sun's web site!</i></p>
+ available from Tomcat or JBoss or Sun's web site!</i></p>
<p>You need to edit the <b>build.xml</b> file and
put in the correct directories for the <code>jboss</code> and
<code>tomcat</code> properties pointing to your jboss
install directory and Tomcat install directory.</p>
<p>You need to edit the <b>jndi.properties</b> file and put
- the correct hostname for your jBoss server in the
+ the correct hostname for your JBoss server in the
<code>java.naming.provider.url</code> property.</p>
<h3><a NAME="petstore4">Resolve the Catalog DB Situation</a></h3>
<p>The default implementation of the Catalog object performs all
the data access from the JSP helper class and ignores the EJB.
- If you are running jBoss and Tomcat separately, this does not
+ If you are running JBoss and Tomcat separately, this does not
work (the DB pools are only available to the EJBs). It may
- work if you are running jBoss and Tomcat fully integrated, but
+ work if you are running JBoss and Tomcat fully integrated, but
it is still a questionable design choice.</p>
<p>Because of the way Sun partitioned their code, it is quite
easy to move the DB calls to the EJB. Just copy the code out of
@@ -100,7 +100,7 @@
<p>The default implementation of the Account object assumes that
the authentication information will be shared between the
servlet and EJB containers, but this is not the case between
- jBoss and Tomcat. You must make a small change in the
+ JBoss and Tomcat. You must make a small change in the
ShoppingClientController interface - add a
<code>getAccount(String userid)</code> method along with the
parameterless method. Then implement it in the
@@ -115,7 +115,7 @@
<p>The default JNDI lookups (in
<code>com.sun.estore.util.EJBUtil</code>) assume that the JNDI
names for beans will be the same regardless of whether the
- caller is a JSP or EJB. This is not the case for jBoss and
+ caller is a JSP or EJB. This is not the case for JBoss and
Tomcat - the EJB lookups are the same (for example,
<code>java:comp/env/ejb/catalog</code>), but the JSP lookups
are different (for example, <code>TheCatalog</code>). The
@@ -171,7 +171,7 @@
you may need to comment out the <code>drop table</code>
statements at the top for it to run the first time). If you
like, you can also use the PostgreSQL script contained in the
- jBoss Petstore package, but then you'll need to copy the
+ JBoss Petstore package, but then you'll need to copy the
<code>OrderDAOPostgreSQL.java</code> file to the
<code>src/com/sun/estore/order/ejb</code> directory, and update
the <code>OrderDAO.getDAO()</code> method to instantiate a new
@@ -182,14 +182,14 @@
or schema (the terminology varies) and then run the appropriate
script to populate it. Make sure your DB is running.</p>
- <h3><a NAME="petstore8">Add DB Pool to jBoss</a></h3>
- <p>The jBoss Petstore Package includes the files
+ <h3><a NAME="petstore8">Add DB Pool to JBoss</a></h3>
+ <p>The JBoss Petstore Package includes the files
<code>jboss.conf</code>, <code>jboss.jcml</code>, and
<code>jboss.properties</code>. The default configuration has
an Oracle DB pool and a PostgreSQL DB Pool. You should
update or replace these with a single DB pool that points
to your database. You will need to put your DB driver JAR
- in the <code>lib/ext</code> directory of your jBoss
+ in the <code>lib/ext</code> directory of your JBoss
installation, and then edit these three files according to
the procedures in the <a HREF="adv_config.html#datasources">Data
Sources</a> section.</p>
@@ -198,12 +198,12 @@
<p>If you look at the file <code>src/docroot/footer.jsp</code>
in the pet store directory, it has a line that prints
"<code>Running on</code>" and then tries to fetch the
- server name. This call doesn't work in Tomcat or jBoss,
- so just replace it with a hardcoded "<code>Tomcat+jBoss</code>"
+ server name. This call doesn't work in Tomcat or JBoss,
+ so just replace it with a hardcoded "<code>Tomcat+JBoss</code>"
or whatever you prefer.</p>
- <h3><a NAME="petstore10">Add jBoss-Specific EJB Directives</a></h3>
- <p>The jBoss Petstore Package includes the file
+ <h3><a NAME="petstore10">Add JBoss-Specific EJB Directives</a></h3>
+ <p>The JBoss Petstore Package includes the file
<code>estore-jboss.xml</code> which will become the
<code>jboss.xml</code> file in your EJB JAR. You should change
the <code>res-jndi-name</code> tag near the top to use the
@@ -211,9 +211,9 @@
"PostgresDB".</p>
<h3><a NAME="petstore11">Build and Deploy</a></h3>
- <p>Run the <code>build.sh</code> script in the jBoss Petstore
+ <p>Run the <code>build.sh</code> script in the JBoss Petstore
Package to build the pet store EJB-JAR and deploy the pet
- store to jBoss and Tomcat. It will create a context called
+ store to JBoss and Tomcat. It will create a context called
<code>estore</code> in Tomcat.</p>
<h3><a NAME="petstore12">Add User Accounts to Tomcat</a></h3>
@@ -232,14 +232,14 @@
<p>You need to add a number of libraries to the Tomcat pet store
web app. These should go in the tomcat directory under
<code>webapps/estore/WEB-INF/lib</code>. The JARs you need
- are distributred with jBoss (in the <code>clients</code>
+ are distributred with JBoss (in the <code>clients</code>
directory): <code>ejb.jar</code>, <code>jboss-client</code>,
<code>jnp-client.jar</code>, <code>jdbc2_0-stdext.jar</code>,
and <code>jta-spec1_0_1.jar</code>. If you're running in
JDK <= 1.2.2, you also need <code>jndi.jar</code>.</p>
- <h3><a NAME="petstore14">Start jBoss</a></h3>
- <p>When you start jBoss, you should see it deploy the Pet Store
+ <h3><a NAME="petstore14">Start JBoss</a></h3>
+ <p>When you start JBoss, you should see it deploy the Pet Store
EJBs.</p>
<h3><a NAME="petstore15">Start Tomcat</a></h3>
@@ -264,8 +264,8 @@
<p>A common EJB-only example comes from the book
<a HREF="http://www.oreilly.com/catalog/entjbeans2/">Enterprise
JavaBeans, 2nd Edition</a> (Chapter 4). The examples need some
- slight changes to run within jBoss, and you can download the
- <a HREF="../rmh_jboss.zip">jBoss Version</a> if you just want to
+ slight changes to run within JBoss, and you can download the
+ <a HREF="../rmh_jboss.zip">JBoss Version</a> if you just want to
cut to the chase. But if you'd like to get a better
understanding of the differences, here are the steps you'll need
to follow to update the examples. These directions are for UNIX,
@@ -275,11 +275,11 @@
<li><A HREF="#rmh1">Download the Example Code</a></li>
<li><A HREF="#rmh2">Set the Environment</a></li>
<li><A HREF="#rmh3">Make the EJB Code Change</a></li>
- <li><A HREF="#rmh4">Create a jBoss Deployment Descriptor</a></li>
+ <li><A HREF="#rmh4">Create a JBoss Deployment Descriptor</a></li>
<li><A HREF="#rmh5">Compile and Deploy the EJB Code</a></li>
<li><A HREF="#rmh6">Make the Client Code Changes</a></li>
<li><A HREF="#rmh7">Compile the Clients</a></li>
- <li><A HREF="#rmh8">Start jBoss</a></li>
+ <li><A HREF="#rmh8">Start JBoss</a></li>
<li><A HREF="#rmh9">Configure JNDI for the Clients</a></li>
<li><A HREF="#rmh10">Run the Clients</a></li>
<li><A HREF="#rmh11">Example Notes</a></li>
@@ -291,20 +291,20 @@
<a
href="http://www.oreilly.com/catalog/entjbeans2/chapter/examples.zip">O'Reilly's
site</a>. Unpack it anywhere you like.</p>
<h3><a NAME="rmh2">Set the Environment</a></h3>
- <p>You will need the jBoss libraries to compile and run the
+ <p>You will need the JBoss libraries to compile and run the
examples. The scripts below locate that using the
<code>JBOSS_HOME</code> environment variable. So you need to
- set the environment variable to point to your jBoss
+ set the environment variable to point to your JBoss
installation. For example:</p>
<pre>
export JBOSS_HOME=$HOME/jboss
</pre>
<h3><a NAME="rmh3">Make the EJB Code Change</a></h3>
- <p>The beans are almost okay for jBoss, but you do need to make
+ <p>The beans are almost okay for JBoss, but you do need to make
one minor change: the reference made by
<code>TravelAgentBean</code> to <code>CabinBean</code>. In
- jBoss, an EJB must refer to other EJBs using the
+ JBoss, an EJB must refer to other EJBs using the
<code>java:comp/env</code> namespace. Edit
<code>com/titan/travelagent/TravelAgentBean.java</code>, and
replace
@@ -312,9 +312,9 @@
with
<pre>Object obj = jndiContext.lookup("<b>java:comp/env/</b>ejb/CabinHome");</pre>
- <h3><a NAME="rmh4">Create a jBoss Deployment Descriptor</a></h3>
+ <h3><a NAME="rmh4">Create a JBoss Deployment Descriptor</a></h3>
<p>In order to link the EJB reference above to a valid EJB, you
- need to create a jBoss Deployment Descriptor (a
+ need to create a JBoss Deployment Descriptor (a
<code>jboss.xml</code> file). You should create the file
<code>com/titan/travelagent/jboss.xml</code> with the following
contents:</p>
@@ -337,7 +337,7 @@
<h3><a NAME="rmh5">Compile and Deploy the EJB Code</a></h3>
<p>You can use the following script to compile all the EJBs,
package them with the deployment descriptors, and deploy
- them to jBoss:</p>
+ them to JBoss:</p>
<pre>
#!/bin/sh
@@ -359,7 +359,7 @@
com/titan/travelagent/jboss.xml \
META-INF/
-# jBoss needs the Home, Remote and primary key (PK) classes
+# JBoss needs the Home, Remote and primary key (PK) classes
# of the Cabin in travelagent.jar so that TravelAgent*.class
# can access the Cabin bean
@@ -413,18 +413,18 @@
com/titan/travelagent/Client*.java
</pre>
- <h3><a NAME="rmh8">Start jBoss</a></h3>
- <p>When you start jBoss, you should see the example EJBs
+ <h3><a NAME="rmh8">Start JBoss</a></h3>
+ <p>When you start JBoss, you should see the example EJBs
deployed.</p>
<h3><a NAME="rmh9">Configure JNDI for the Clients</a></h3>
<p>You need to make the clients aware of how to look up the
- jBoss server. This is done in the run script below by
+ JBoss server. This is done in the run script below by
adding the <code>jboss/conf</code> directory to the
classpath, since that directory has a
<code>jndi.properties</code> file. You could also copy
that file to another location and add that location to
- the classpath. Make sure the jBoss server hostname in
+ the classpath. Make sure the JBoss server hostname in
the property "<code>java.naming.provider.url</code>" is
correct in your <code>jndi.properties</code>.</p>
@@ -448,9 +448,9 @@
client to run, and it sets the classpath and runs the
client. For example:</p>
<pre>
-./jBossRunClient.sh com.titan.cabin.Client_1
-./jBossRunClient.sh com.titan.cabin.Client_2
-./jBossRunClient.sh com.titan.travelagent.Client_1
+./JBossRunClient.sh com.titan.cabin.Client_1
+./JBossRunClient.sh com.titan.cabin.Client_2
+./JBossRunClient.sh com.titan.travelagent.Client_1
</pre>
<h3><a NAME="rmh11">Example Notes</a></h3>
@@ -467,8 +467,8 @@
</ul>
<hr>
- <h2><a NAME="jbosstest">jBoss Test Beans</a></h2>
- <p>There is a test suite available for jBoss, which consists
+ <h2><a NAME="jbosstest">JBoss Test Beans</a></h2>
+ <p>There is a test suite available for JBoss, which consists
of a number of EJBs that tests all facets of the server,
and the clients that go with them. Currently, the test
beans are only available from CVS. In order to build and
@@ -476,7 +476,7 @@
<ol>
<li>Get the test beans from CVS. You can get directions for
checking things out of CVS if you go to the
- <a HREF="http://www.jboss.org/">jBoss Home Page</a> and
+ <a HREF="http://www.jboss.org/">JBoss Home Page</a> and
follow the link on the left to CVS. Once you have your
CVSHOME configured and you have logged in, check out the
<code>jbosstest</code> module.</li>
@@ -484,10 +484,10 @@
<code>jbosstest/src/build</code> directory and run
<code>build.sh</code> (UNIX) or <code>build.bat</code>
(Windows).</li>
- <li>Copy the EJB JARs to jBoss. Copy
+ <li>Copy the EJB JARs to JBoss. Copy
<code>jbosstest/dist/deploy/*.jar</code> to
<code>jboss/dist/deploy</code>.</li>
- <li>Start jBoss.</li>
+ <li>Start JBoss.</li>
<li>Run the clients scripts in
<code>jbosstest/dist/bin</code> to run the tests.</li>
</ol>
1.2 +2 -2 newsite/manual/extending.html
Index: extending.html
===================================================================
RCS file: /products/cvs/ejboss/newsite/manual/extending.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- extending.html 2000/11/12 20:32:11 1.1
+++ extending.html 2001/02/08 05:31:41 1.2
@@ -1,9 +1,9 @@
<html>
<head>
- <title>jBoss 2.0: Extending jBoss</title>
+ <title>JBoss 2.0: Extending JBoss</title>
<link REL ="stylesheet" TYPE="text/css" HREF="manual.css" TITLE="Style" />
</head>
<body>
- <h1 ALIGN="CENTER">jBoss 2.0: Extending jBoss</h1>
+ <h1 ALIGN="CENTER">JBoss 2.0: Extending JBoss</h1>
</body>
</html>
1.2 +2 -2 newsite/manual/future.html
Index: future.html
===================================================================
RCS file: /products/cvs/ejboss/newsite/manual/future.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- future.html 2000/11/12 20:32:11 1.1
+++ future.html 2001/02/08 05:31:41 1.2
@@ -1,9 +1,9 @@
<html>
<head>
- <title>jBoss 2.0: What The Future Holds</title>
+ <title>JBoss 2.0: What The Future Holds</title>
<link REL ="stylesheet" TYPE="text/css" HREF="manual.css" TITLE="Style" />
</head>
<body>
- <h1 ALIGN="CENTER">jBoss 2.0: What The Future Holds</h1>
+ <h1 ALIGN="CENTER">JBoss 2.0: What The Future Holds</h1>
</body>
</html>
1.2 +20 -20 newsite/manual/index.html
Index: index.html
===================================================================
RCS file: /products/cvs/ejboss/newsite/manual/index.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- index.html 2000/11/12 20:32:12 1.1
+++ index.html 2001/02/08 05:31:41 1.2
@@ -1,10 +1,10 @@
<html>
<head>
- <title>jBoss 2.0 Manual</title>
+ <title>JBoss 2.0 Manual</title>
<link REL ="stylesheet" TYPE="text/css" HREF="manual.css" TITLE="Style" />
</head>
<body>
- <h1 ALIGN="CENTER">jBoss 2.0 Manual</h1>
+ <h1 ALIGN="CENTER">JBoss 2.0 Manual</h1>
<p CLASS="tc1"><a CLASS="plain" HREF="warning.html">WARNING - PRELIMINARY
DOCUMENTATION</a></p>
<p CLASS="tc2"><a CLASS="plain" HREF="warning.html#todos">Documentation
TODOs</a></p>
@@ -13,17 +13,17 @@
<p CLASS="tc2"><a CLASS="plain" HREF="intro.html#j2ee">About J2EE</a></p>
<p CLASS="tc3"><a CLASS="plain" HREF="intro.html#inj2ee">What's in
J2EE</a></p>
<p CLASS="tc3"><a CLASS="plain" HREF="intro.html#j2eemore">Further
Documentation</a></p>
- <p CLASS="tc2"><a CLASS="plain" HREF="intro.html#jboss">About jBoss</a></p>
- <p CLASS="tc3"><a CLASS="plain" HREF="intro.html#provides">What jBoss
Provides</a></p>
- <p CLASS="tc3"><a CLASS="plain" HREF="intro.html#arch">jBoss Architecture
Overview</a></p>
+ <p CLASS="tc2"><a CLASS="plain" HREF="intro.html#jboss">About JBoss</a></p>
+ <p CLASS="tc3"><a CLASS="plain" HREF="intro.html#provides">What JBoss
Provides</a></p>
+ <p CLASS="tc3"><a CLASS="plain" HREF="intro.html#arch">JBoss Architecture
Overview</a></p>
<p CLASS="tc3"><a CLASS="plain" HREF="intro.html#complete">Complete J2EE
Solutions</a></p>
- <p CLASS="tc2"><a CLASS="plain" HREF="intro.html#team">The jBoss
Team</a></p>
+ <p CLASS="tc2"><a CLASS="plain" HREF="intro.html#team">The JBoss
Team</a></p>
<p CLASS="tc1"><a CLASS="plain" HREF="install.html">Installation</a></p>
<p CLASS="tc2"><a CLASS="plain" HREF="install.html#versions">Supported Java
Versions</a></p>
<p CLASS="tc2"><a CLASS="plain" HREF="install.html#windows">Windows</a></p>
<p CLASS="tc3"><a CLASS="plain" HREF="install.html#service">Installing as
an NT Service</a></p>
<p CLASS="tc2"><a CLASS="plain" HREF="install.html#unix">UNIX</a></p>
- <p CLASS="tc3"><a CLASS="plain" HREF="install.html#startup">Starting
jBoss with the Server</a></p>
+ <p CLASS="tc3"><a CLASS="plain" HREF="install.html#startup">Starting
JBoss with the Server</a></p>
<p CLASS="tc2"><a CLASS="plain" HREF="install.html#mac">Macintosh</a></p>
<p CLASS="tc2"><a CLASS="plain" HREF="install.html#other">Other
Platforms</a></p>
<p CLASS="tc1"><a CLASS="plain" HREF="config.html">Basic Configuration</a></p>
@@ -56,18 +56,18 @@
<p CLASS="tc4"><a CLASS="plain" HREF="adv_config.html#severity">By
Severity</a></p>
<p CLASS="tc4"><a CLASS="plain" HREF="adv_config.html#source">By
Source</a></p>
<p CLASS="tc2"><a CLASS="plain" HREF="adv_config.html#jms">JMS</a></p>
- <p CLASS="tc2"><a CLASS="plain" HREF="adv_config.html#multiple">Running
Multiple jBoss Servers on One Machine</a></p>
+ <p CLASS="tc2"><a CLASS="plain" HREF="adv_config.html#multiple">Running
Multiple JBoss Servers on One Machine</a></p>
<p CLASS="tc2"><a CLASS="plain" HREF="adv_config.html#ports">Changing
Default Port Assignments</a></p>
<p CLASS="tc2"><a CLASS="plain" HREF="adv_config.html#dynamic">Dynamic
Classloading for Clients</a></p>
<p CLASS="tc2"><a CLASS="plain" HREF="adv_config.html#custom">Custom
MBeans</a></p>
<p CLASS="tc2"><a CLASS="plain" HREF="adv_config.html#third">Third-Party
Products</a></p>
- <p CLASS="tc1"><a CLASS="plain" HREF="start_stop.html">Starting &
Stopping jBoss</a></p>
+ <p CLASS="tc1"><a CLASS="plain" HREF="start_stop.html">Starting &
Stopping JBoss</a></p>
<p CLASS="tc2"><a CLASS="plain" HREF="start_stop.html#start">Starting from
the Command Line</a></p>
<p CLASS="tc2"><a CLASS="plain" HREF="start_stop.html#console">Stopping
from the Console</a></p>
<p CLASS="tc2"><a CLASS="plain" HREF="start_stop.html#script">Stopping with
the Shutdown Script</a></p>
<p CLASS="tc2"><a CLASS="plain" HREF="start_stop.html#jmx">Stopping via the
Management Interface</a></p>
<p CLASS="tc1"><a CLASS="plain" HREF="developing.html">Writing EJBs</a></p>
- <p CLASS="tc2"><a CLASS="plain" HREF="developing.html#ejb11">jBoss Supports
EJB 1.1</a></p>
+ <p CLASS="tc2"><a CLASS="plain" HREF="developing.html#ejb11">JBoss Supports
EJB 1.1</a></p>
<p CLASS="tc2"><a CLASS="plain" HREF="developing.html#entity">Entity
Beans</a></p>
<p CLASS="tc3"><a CLASS="plain" HREF="developing.html#cmp">CMP Entity
Beans</a></p>
<p CLASS="tc4"><a CLASS="plain" HREF="developing.html#cmppk">Primary
Keys for CMP Beans</a></p>
@@ -80,12 +80,12 @@
<p CLASS="tc2"><a CLASS="plain" HREF="developing.html#data">Using Data
Sources</a></p>
<p CLASS="tc2"><a CLASS="plain" HREF="developing.html#ejbs">Using Other
EJBs</a></p>
<p CLASS="tc2"><a CLASS="plain"
HREF="developing.html#trans">Transactions</a></p>
- <p CLASS="tc1"><a CLASS="plain" HREF="deploying.html">Deploying EJBs in
jBoss</a></p>
+ <p CLASS="tc1"><a CLASS="plain" HREF="deploying.html">Deploying EJBs in
JBoss</a></p>
<p CLASS="tc2"><a CLASS="plain" HREF="deploying.html#preparing">Preparing
Your EJB JAR</a></p>
<p CLASS="tc3"><a CLASS="plain" HREF="deploying.html#classes">Required
Classes</a></p>
<p CLASS="tc3"><a CLASS="plain"
HREF="deploying.html#descriptors">Deployment Descriptors</a></p>
<p CLASS="tc4"><a CLASS="plain" HREF="deploying.html#ejb11">The EJB 1.1
Deployment Descriptor</a></p>
- <p CLASS="tc4"><a CLASS="plain" HREF="deploying.html#jboss">The jBoss
Deployment Descriptor</a></p>
+ <p CLASS="tc4"><a CLASS="plain" HREF="deploying.html#jboss">The JBoss
Deployment Descriptor</a></p>
<p CLASS="tc4"><a CLASS="plain" HREF="deploying.html#jaws">The JAWS
Deployment Descriptor</a></p>
<p CLASS="tc4"><a CLASS="plain" HREF="deploying.html#ejx">Editing
Deployment Descriptors with EJX</a></p>
<p CLASS="tc4"><a CLASS="plain" HREF="deploying.html#byhand">Editing
Deployment Descriptors By Hand</a></p>
@@ -98,14 +98,14 @@
<p CLASS="tc2"><a CLASS="plain" HREF="deploying.html#undeploy">Undeploying
EJBs</a></p>
<p CLASS="tc2"><a CLASS="plain" HREF="deploying.html#redeploy">Redeploying
Existing EJBs</a></p>
<p CLASS="tc2"><a CLASS="plain" HREF="deploying.html#hot">Hot
Deployment</a></p>
- <p CLASS="tc1"><a CLASS="plain" HREF="jms.html">JMS in jBoss</a></p>
+ <p CLASS="tc1"><a CLASS="plain" HREF="jms.html">JMS in JBoss</a></p>
<p CLASS="tc2"><a CLASS="plain" HREF="jms.html#about">About SpyderMQ</a></p>
<p CLASS="tc2"><a CLASS="plain" HREF="jms.html#install">Installing
SpyderMQ</a></p>
<p CLASS="tc2"><a CLASS="plain" HREF="jms.html#using">Using SpyderMQ</a></p>
- <p CLASS="tc1"><a CLASS="plain" HREF="managing.html">Managing a Live jBoss
Server</a></p>
+ <p CLASS="tc1"><a CLASS="plain" HREF="managing.html">Managing a Live JBoss
Server</a></p>
<p CLASS="tc2">Web Administration</p>
<p CLASS="tc2">JMX Client Administration</p>
- <p CLASS="tc1"><a CLASS="plain" HREF="clients.html">jBoss Clients</a></p>
+ <p CLASS="tc1"><a CLASS="plain" HREF="clients.html">JBoss Clients</a></p>
<p CLASS="tc2"><a CLASS="plain" HREF="clients.html#jdk">Supported Java
Versions</a></p>
<p CLASS="tc2"><a CLASS="plain" HREF="clients.html#jndi">Using JNDI</a></p>
<p CLASS="tc3"><a CLASS="plain" HREF="clients.html#remote">Connecting to
a Remote Server</a></p>
@@ -137,7 +137,7 @@
<p CLASS="tc3">JBuilder</p>
<p CLASS="tc3">VisualAge</p>
<p CLASS="tc3">Forte</p>
- <p CLASS="tc1"><a CLASS="plain" HREF="extending.html">Extending jBoss</a></p>
+ <p CLASS="tc1"><a CLASS="plain" HREF="extending.html">Extending JBoss</a></p>
<p CLASS="tc2">Licensing</p>
<p CLASS="tc2">What You Can (Conveniently) Extend</p>
<p CLASS="tc2">What You Can (Conveniently) Replace</p>
@@ -145,7 +145,7 @@
<p CLASS="tc1"><a CLASS="plain" HREF="examples.html">Examples</a></p>
<p CLASS="tc2"><a CLASS="plain" HREF="examples.html#petstore">J2EE
Blueprints: Pet Store</a></p>
<p CLASS="tc2"><a CLASS="plain" HREF="examples.html#rmh">From <U>Enterprise
JavaBeans</U> (Monson-Haefel)</a></p>
- <p CLASS="tc2"><a CLASS="plain" HREF="examples.html#jbosstest">jBoss Test
Beans</a></p>
+ <p CLASS="tc2"><a CLASS="plain" HREF="examples.html#jbosstest">JBoss Test
Beans</a></p>
<p CLASS="tc1"><a CLASS="plain" HREF="trouble.html">Troubleshooting</a></p>
<p CLASS="tc2">Identifying Your Problem</p>
<p CLASS="tc2">Verification Problems</p>
@@ -163,7 +163,7 @@
<p CLASS="tc1">Appendix</p>
<p CLASS="tc2"><a CLASS="plain" HREF="ejx.html">EJX Walkthrough</a></p>
<p CLASS="tc2"><a CLASS="plain" HREF="dtds.html">DTDs</a></p>
- <p CLASS="tc3">For the jBoss Server</p>
+ <p CLASS="tc3">For the JBoss Server</p>
<p CLASS="tc4">jboss.conf</p>
<p CLASS="tc4">jboss.jcml</p>
<p CLASS="tc4">jboss.dependencies</p>
@@ -176,7 +176,7 @@
<p CLASS="tc3">3rd Party Software</p>
<p CLASS="tc3">What It Means</p>
<p CLASS="tc2"><a CLASS="plain" HREF="unix_startup.html">UNIX Startup
Scripts</a></p>
- <p CLASS="tc2"><a CLASS="plain" HREF="architecture.html">jBoss
Architecture</a></p>
+ <p CLASS="tc2"><a CLASS="plain" HREF="architecture.html">JBoss
Architecture</a></p>
<p CLASS="tc3">JMX</p>
<p CLASS="tc3">Container Factory</p>
<p CLASS="tc3">Automatic Deployment</p>
@@ -189,6 +189,6 @@
<p CLASS="tc4">Stateful Session</p>
<p CLASS="tc4">Stateless Session</p>
<p CLASS="tc3">Interceptors</p>
- <p CLASS="tc2"><a CLASS="plain" HREF="references.html">jBoss in
Production</a></p>
+ <p CLASS="tc2"><a CLASS="plain" HREF="references.html">JBoss in
Production</a></p>
</body>
</html>
1.2 +19 -19 newsite/manual/install.html
Index: install.html
===================================================================
RCS file: /products/cvs/ejboss/newsite/manual/install.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- install.html 2000/11/12 20:32:12 1.1
+++ install.html 2001/02/08 05:31:41 1.2
@@ -1,36 +1,36 @@
<html>
<head>
- <title>jBoss 2.0: Installation</title>
+ <title>JBoss 2.0: Installation</title>
<link REL ="stylesheet" TYPE="text/css" HREF="manual.css" TITLE="Style" />
</head>
<body>
- <h1 ALIGN="CENTER">jBoss 2.0: Installation</h1>
+ <h1 ALIGN="CENTER">JBoss 2.0: Installation</h1>
<h2><a NAME="versions">Supported Java Versions</a></h2>
- <p>jBoss requires Java 2. In particular, if you're using Sun's
+ <p>JBoss requires Java 2. In particular, if you're using Sun's
JDK, you need 1.2.2 or greater. The default configuration
supports JDK 1.3 only.</p>
- <p>If you want to run jBoss under JDK 1.2.2, you must presently
+ <p>If you want to run JBoss under JDK 1.2.2, you must presently
override the default container invoker setting in the jboss.xml
file for each of your EJB JARs
- (see <a HREF="deploying.html#jboss">The jBoss Deployment
+ (see <a HREF="deploying.html#jboss">The JBoss Deployment
Descriptor</a>). In a future release, you will be able to change
the default container invoker setting instead.</p>
<p>The only feature that will not work under JDK 1.2 is the
- graceful server shutdown from the jBoss console. Under JDK 1.3,
+ graceful server shutdown from the JBoss console. Under JDK 1.3,
if you hit Ctrl-C at the console, the server will shut down
properly. Under 1.2, it will shut down abruptly, without
closing DB connections, erasing temp files, etc.). You can
still shut the server down gracefully via the management
- interface (see <a HREF="managing.html">Managing a Live jBoss
+ interface (see <a HREF="managing.html">Managing a Live JBoss
Server</a>), but that is a more complex process.</p>
<h2><a NAME="windows">Installing on Windows</a></h2>
<p>You can use either the ZIP package or Installer package to
install on Windows.</p>
- <p>If you use the ZIP package, create a jBoss directory (the path
+ <p>If you use the ZIP package, create a JBoss directory (the path
should not have spaces in any of the directory names) and unzip
- the jBoss package into the directory you created.</p>
+ the JBoss package into the directory you created.</p>
<p>If you use the Installer package, you need to have a JVM on your
machine before you run it. Once you have a JVM, start the
installer and:</p>
@@ -42,7 +42,7 @@
in the names of any of the directories in the path.</li>
<li>Choose whether to install shortcuts.</li>
</ol>
- <p>After that, jBoss will install.</p>
+ <p>After that, JBoss will install.</p>
<h3><a NAME="service">Installing as an NT Service</a></h3>
<p>Directions Forthcoming</p>
@@ -50,9 +50,9 @@
<h2><a NAME="unix">Installing on UNIX</a></h2>
<p>You can use either the ZIP package or Installer package to
install on UNIX.</p>
- <p>If you use the ZIP package, create a jBoss directory (the path
+ <p>If you use the ZIP package, create a JBoss directory (the path
should not have spaces in any of the directory names) and unzip
- the jBoss package into the directory you created.</p>
+ the JBoss package into the directory you created.</p>
<p>If you use the Installer package, you need to have a JVM on your
machine before you run it. Once you have a JVM, start the
installer and:</p>
@@ -63,24 +63,24 @@
<li>Select an installation directory. There should not be spaces
in the names of any of the directories in the path.</li>
</ol>
- <p>After that, jBoss will install.</p>
+ <p>After that, JBoss will install.</p>
- <h3><a NAME="startup">Starting jBoss with the Server</a></h3>
- <p>You can set up scripts for UNIX that will start jBoss when
+ <h3><a NAME="startup">Starting JBoss with the Server</a></h3>
+ <p>You can set up scripts for UNIX that will start JBoss when
the server starts up and shut is down when the server shuts down.
There are instructions in the Appendix (see
<a HREF="unix_start.html">UNIX Startup Scripts</a>).</p>
<h2><a NAME="mac">Macintosh</a></h2>
<p>The current Mac OS does not support Java 2, so you can't run
- jBoss on it. Mac OS X will include Java 2 support, but we have
- not yet tested jBoss with the OS X beta. If you have, please
- let us know on the jBoss
+ JBoss on it. Mac OS X will include Java 2 support, but we have
+ not yet tested JBoss with the OS X beta. If you have, please
+ let us know on the JBoss
<a HREF="http://www.jboss.org/mailing.htm">Mailing List</a>.</p>
<h2><a NAME="other">Other Platforms</a></h2>
<p>Any operating system that supports Java 2 should be able to run
- jBoss. If you have run it on another OS, please let us know. If
+ JBoss. If you have run it on another OS, please let us know. If
for some reason you can't access the ZIP file on a platform, we
will work with you to provide the appropriate archive type.</p>
</body>
1.2 +35 -35 newsite/manual/intro.html
Index: intro.html
===================================================================
RCS file: /products/cvs/ejboss/newsite/manual/intro.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- intro.html 2000/11/12 20:32:13 1.1
+++ intro.html 2001/02/08 05:31:41 1.2
@@ -1,11 +1,11 @@
<html>
<head>
- <title>jBoss 2.0: Introduction</title>
+ <title>JBoss 2.0: Introduction</title>
<link REL ="stylesheet" TYPE="text/css" HREF="manual.css" TITLE="Style" />
</head>
<body>
- <h1 ALIGN="CENTER">jBoss 2.0: Introduction</h1>
- <p>Welcome to jBoss, the Open Source EJB Application Server!</p>
+ <h1 ALIGN="CENTER">JBoss 2.0: Introduction</h1>
+ <p>Welcome to JBoss, the Open Source EJB Application Server!</p>
<h2><a NAME="oss">About Open Source</a></h2>
<p>The Open Source model relies on giving a public access to the
@@ -16,26 +16,26 @@
thousands of high-level developers generates simple, robust,
reliable and bug-free applications quicker and easier than any
closed team could achieve.</p>
- <p>jBoss is free to download and use. There are no fees for use
+ <p>JBoss is free to download and use. There are no fees for use
in development, for use in production, for redistribution, for use
on any particular operating system, etc. The source code is
available for download as well.</p>
<p>Subject to the terms of the GPL License (see
<a HREF="license.html">License</a> in the Appendix), you are
- welcome to modify the source code for jBoss to do as you see fit.
+ welcome to modify the source code for JBoss to do as you see fit.
In general, you must make your changes available to the community
under the GPL License as well. We encourage you to make any fixes
or enhancements you see fit, and let us know by describing your
- changes to the jBoss
+ changes to the JBoss
<a HREF="http://www.jboss.org/mailing.htm">Mailing List</a>.
- If you want to integrate jBoss with packages or libraries that are
+ If you want to integrate JBoss with packages or libraries that are
not themselves open-source, or you have other concerns, see the
guidelines under
- <a HREF="BROKENLINK">Extending jBoss: Licensing</a>.<p>
- <p><strong>Please Note:</strong> Any EJBs you write for jBoss
+ <a HREF="BROKENLINK">Extending JBoss: Licensing</a>.<p>
+ <p><strong>Please Note:</strong> Any EJBs you write for JBoss
<u>are not required to be open-source, or licensed under the
GPL</u>. If you adhere to the well-defined EJB interface, you
- are not extending jBoss, you are writing an application for an
+ are not extending JBoss, you are writing an application for an
application server.</p>
<h2><a NAME="j2ee">About J2EE</a></h2>
@@ -76,46 +76,46 @@
<li><A HREF="http://java.sun.com/j2ee/docs.html">J2EE Documentation</a></li>
</ul>
- <h2><a NAME="jboss">About jBoss</a> (<a
HREF="http://www.jboss.org/">www.jboss.org</a>)</h2>
- <p>jBoss is an EJB application server. It does not implement the
+ <h2><a NAME="jboss">About JBoss</a> (<a
HREF="http://www.jboss.org/">www.jboss.org</a>)</h2>
+ <p>JBoss is an EJB application server. It does not implement the
entire J2EE package. Instead, it implements an important subset
- of J2EE in a flexible and modular way. You may use jBoss alone,
+ of J2EE in a flexible and modular way. You may use JBoss alone,
or you may use it in conjuntion with other products to provide a
complete J2EE environment (see
<a HREF="third_party.html">Third-Party Software</a>).
- <h3><A NAME="provides">What jBoss Provides</a></h3>
+ <h3><A NAME="provides">What JBoss Provides</a></h3>
<dl>
<dt>EJB</dt>
- <dd>You can deploy and run EJB 1.1 beans in jBoss.</dd>
+ <dd>You can deploy and run EJB 1.1 beans in JBoss.</dd>
<dt>JNDI</dt>
- <dd>jBoss provides an implementation of JNDI so all your
+ <dd>JBoss provides an implementation of JNDI so all your
components can look each other up and work together. Clients,
- servlets, and other components outside jBoss can use this to
+ servlets, and other components outside JBoss can use this to
access EJBs, and it is used extensively within the EJBs
themselves (to access resources, etc.).</dd>
<dt>JMS</dt>
- <dd>jBoss provides an implementation of JMS.</dd>
+ <dd>JBoss provides an implementation of JMS.</dd>
<dt>JDBC</dt>
- <dd>jBoss does not provide JDBC drivers - you must get those
- from your DB provider or elsewhere. However, jBoss does
+ <dd>JBoss does not provide JDBC drivers - you must get those
+ from your DB provider or elsewhere. However, JBoss does
provide advanced JDBC features such as connection pooling,
statement caching, two-phase-commit transaction management,
and JNDI accessibility of data sources.</dd>
<dt>JTA</dt>
- <dd>jBoss provides a JTA implementation and can manage
+ <dd>JBoss provides a JTA implementation and can manage
transaction across any number of beans and resources.
Container-managed transactions are fully supported, so
you need only specify transaction information in your
EJB deployment descriptors.</dd>
</dl>
- <h3><a NAME="arch">jBoss Architecture Overview</a></h3>
- <p>The jBoss architecture is component-based and dynamic, to
+ <h3><a NAME="arch">JBoss Architecture Overview</a></h3>
+ <p>The JBoss architecture is component-based and dynamic, to
allow easy extensions and custom configuration. The server
itself is based on the Java Management Extensions (JMX). This
allows components to be loaded and initialized based on simple
@@ -130,31 +130,31 @@
or applications can use different features and techniques.</p>
<p>All together, this makes a very flexible architecture that is
easy to manage and extend. If you are interested in more detail,
- refer to <a HREF="architecture.html">jBoss Architecture</a> in the
+ refer to <a HREF="architecture.html">JBoss Architecture</a> in the
Appendix.</p>
<h3><a NAME="complete">Complete J2EE Solutions</a></h3>
<p>According to the list above, for a complete J2EE solution you
need Servlets, JSPs, JavaMail, JavaBeans Activation Framework,
- RMI-IIOP, and JDBC driver(s). jBoss works with a number of
+ RMI-IIOP, and JDBC driver(s). JBoss works with a number of
third-party programs which can provide these capabilities, but
we do not recommend or specify a particular combination. You
can evaluate your options for each, both open-source and
proprietary, and put together a package that contains the most
appropriate tools for your needs.</p>
- <p>We believe the advanced modular achitecture of jBoss makes it
+ <p>We believe the advanced modular achitecture of JBoss makes it
easy to integrate with other software. If you would like to
- use jBoss with a package that is not on our list of
+ use JBoss with a package that is not on our list of
<a HREF="third_party.html">Third-Party Software</a>, post a
messsage to the <A HREF="http://www.jboss.org/mailing.htm">Mailing
List</a> and we will work with you.</p>
- <h2><a NAME="team">The jBoss Team</a></h2>
- <p>As an open-source project, jBoss 2.0 is the product of numerous
- contributors. Though the full list is on the jBoss web page,
- special recognition goes to the member of the jBoss Board. The
- board is the formal management of jBoss, and bore the primary
- responsibility for bringing jBoss 2.0 to you. The board is:</p>
+ <h2><a NAME="team">The JBoss Team</a></h2>
+ <p>As an open-source project, JBoss 2.0 is the product of numerous
+ contributors. Though the full list is on the JBoss web page,
+ special recognition goes to the member of the JBoss Board. The
+ board is the formal management of JBoss, and bore the primary
+ responsibility for bringing JBoss 2.0 to you. The board is:</p>
<ul>
<li>Marc Fleury, USA</li>
<li>Juha Lindfors, Finland</li>
@@ -162,10 +162,10 @@
<li>Rickard Oberg, Sweden</li>
<li>Dan O'Connor, USA</li>
</ul>
- <p>If you are interested in becoming a member of the jBoss team,
+ <p>If you are interested in becoming a member of the JBoss team,
we welcome you. For starters, you should join the
<a HREF="http://www.jboss.org/mailing.htm">Mailing Lists</a> for
both users and developers. Drop us a line with any fixes,
- improvements, or ideas you have. Be a part of jBoss 3.0!</p>
+ improvements, or ideas you have. Be a part of JBoss 3.0!</p>
</body>
</html>
1.2 +7 -7 newsite/manual/jms.html
Index: jms.html
===================================================================
RCS file: /products/cvs/ejboss/newsite/manual/jms.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- jms.html 2000/11/12 20:32:14 1.1
+++ jms.html 2001/02/08 05:31:41 1.2
@@ -1,18 +1,18 @@
<html>
<head>
- <title>jBoss 2.0: JMS in jBoss</title>
+ <title>JBoss 2.0: JMS in JBoss</title>
<link REL ="stylesheet" TYPE="text/css" HREF="manual.css" TITLE="Style" />
</head>
<body>
- <h1 ALIGN="CENTER">jBoss 2.0: JMS in jBoss</h1>
- <p>The implementation of JMS that ships with jBoss is SpyderMQ.</p>
+ <h1 ALIGN="CENTER">JBoss 2.0: JMS in JBoss</h1>
+ <p>The implementation of JMS that ships with JBoss is SpyderMQ.</p>
<h2><a NAME="about">About SpyderMQ</a></h2>
<p><i>This section is forthcoming</i></p>
<h2><a NAME="install">Installing SpyderMQ</a></h2>
- <p>SpyderMQ is included with the jBoss distribution. To active it
- in your jBoss server, you must include it in your
+ <p>SpyderMQ is included with the JBoss distribution. To active it
+ in your JBoss server, you must include it in your
<code>jboss.conf</code> file. Look for a section like this:</p>
<pre>
<!--
@@ -39,10 +39,10 @@
</pre>
<p>Additionally, as noted in the comment, you must set the
<code>SPYDERMQ_HOME</code> environment variable. The best place
- to do this is usually the script that starts jBoss -
+ to do this is usually the script that starts JBoss -
<code>run.bat</code> (Windows) or <code>run.sh</code> (UNIX) in
the <strong>bin</strong> directory. There is a default
- <code>spyderMQ.properties</code> file in the jBoss
+ <code>spyderMQ.properties</code> file in the JBoss
<strong>conf</strong> directory, but you may want to customize
that or replace it with a customized version.</p>
1.2 +2 -2 newsite/manual/license.html
Index: license.html
===================================================================
RCS file: /products/cvs/ejboss/newsite/manual/license.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- license.html 2000/11/12 20:32:14 1.1
+++ license.html 2001/02/08 05:31:41 1.2
@@ -1,9 +1,9 @@
<html>
<head>
- <title>jBoss 2.0: License</title>
+ <title>JBoss 2.0: License</title>
<link REL ="stylesheet" TYPE="text/css" HREF="manual.css" TITLE="Style" />
</head>
<body>
- <h1 ALIGN="CENTER">jBoss 2.0: License</h1>
+ <h1 ALIGN="CENTER">JBoss 2.0: License</h1>
</body>
</html>
1.2 +7 -7 newsite/manual/managing.html
Index: managing.html
===================================================================
RCS file: /products/cvs/ejboss/newsite/manual/managing.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- managing.html 2000/11/12 20:32:14 1.1
+++ managing.html 2001/02/08 05:31:41 1.2
@@ -1,27 +1,27 @@
<html>
<head>
- <title>jBoss 2.0: Managing a Live jBoss Server</title>
+ <title>JBoss 2.0: Managing a Live JBoss Server</title>
<link REL ="stylesheet" TYPE="text/css" HREF="manual.css" TITLE="Style" />
</head>
<body>
- <h1 ALIGN="CENTER">jBoss 2.0: Managing a Live jBoss Server</h1>
- <p>jBoss is built on a Java Management Extensions (JMX)
+ <h1 ALIGN="CENTER">JBoss 2.0: Managing a Live JBoss Server</h1>
+ <p>JBoss is built on a Java Management Extensions (JMX)
infrastructure, so you can use any JMX tools available to manage
- jBoss. Since the JMX specification is so new, that doesn't give
+ JBoss. Since the JMX specification is so new, that doesn't give
you a lot of choice today, but we expect that to change in the
near future. This section describes the tools that are available
today.</p>
<h2><a NAME="web">Web Administration</a></h2>
- <p>jBoss comes with a Web interface for managing the server. By
+ <p>JBoss comes with a Web interface for managing the server. By
default, this listens on port 8082, though you can change that
if necessary (see <a HREF="adv_config.html#ports">Changing
Default Port Assigments</a> in the
<a HREF="adv_config.html">Advanced Configuration</a> section).
- To get an idea of the options, start jBoss and point your
+ To get an idea of the options, start JBoss and point your
browser to the web management port (using a URL like
<a HREF="http://localhost:8082/">http://localhost:8082/</a>).</p>
- <p>The main page gives you a list of services that make up the jBoss
+ <p>The main page gives you a list of services that make up the JBoss
server.
</body>
1.2 +2 -2 newsite/manual/references.html
Index: references.html
===================================================================
RCS file: /products/cvs/ejboss/newsite/manual/references.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- references.html 2000/11/12 20:32:14 1.1
+++ references.html 2001/02/08 05:31:41 1.2
@@ -1,9 +1,9 @@
<html>
<head>
- <title>jBoss 2.0: jBoss in Production</title>
+ <title>JBoss 2.0: JBoss in Production</title>
<link REL ="stylesheet" TYPE="text/css" HREF="manual.css" TITLE="Style" />
</head>
<body>
- <h1 ALIGN="CENTER">jBoss 2.0: jBoss in Production</h1>
+ <h1 ALIGN="CENTER">JBoss 2.0: JBoss in Production</h1>
</body>
</html>
1.2 +10 -10 newsite/manual/start_stop.html
Index: start_stop.html
===================================================================
RCS file: /products/cvs/ejboss/newsite/manual/start_stop.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- start_stop.html 2000/11/12 20:32:14 1.1
+++ start_stop.html 2001/02/08 05:31:41 1.2
@@ -1,13 +1,13 @@
<html>
<head>
- <title>jBoss 2.0: Starting & Stopping jBoss</title>
+ <title>JBoss 2.0: Starting & Stopping JBoss</title>
<link REL ="stylesheet" TYPE="text/css" HREF="manual.css" TITLE="Style" />
</head>
<body>
- <h1 ALIGN="CENTER">jBoss 2.0: Starting & Stopping jBoss</h1>
+ <h1 ALIGN="CENTER">JBoss 2.0: Starting & Stopping JBoss</h1>
<h2><a NAME="start">Starting from the Command Line</a></h2>
- <p>To start jBoss from the command line, use the
+ <p>To start JBoss from the command line, use the
<code>run.bat</code> script on Windows or the
<code>run.sh</code> script on UNIX. The script needs to be run
from the <strong>bin</strong> directory, so if you set up a
@@ -17,28 +17,28 @@
runs the startup script.</p>
<h2><a NAME="console">Stopping from the Console</a></h2>
- <p>If you have a console window for jBoss, you can stop it by
+ <p>If you have a console window for JBoss, you can stop it by
hitting <code>Ctrl-C</code> in the console window. If you ran
- jBoss under JDK 1.3 or greater, jBoss will shut down gracefully
+ JBoss under JDK 1.3 or greater, JBoss will shut down gracefully
when you hit <code>Ctrl-C</code>. Otherwise, it will terminate
abruptly, and you should use a different method to ensure a
graceful shutdown.</p>
<h2><a NAME="script">Stopping with the Shutdown Script</a></h2>
- <p>To stop jBoss without using the console method, you can use
+ <p>To stop JBoss without using the console method, you can use
the <code>shutdown.bat</code> script on Windows or the
<code>shutdown.sh</code> script on UNIX. This will shut
- jBoss down gracefully. If you have multiple jBoss instances
+ JBoss down gracefully. If you have multiple JBoss instances
on you machine, you should create separate shutdown scripts
that include separate <code>jndi.properties</code> files on the
classpath.</p>
<p><i><b>Note:</b> The shutdown script is not yet in the current
- jBoss builds!</i></p>
+ JBoss builds!</i></p>
<h2><a NAME="jmx">Stopping via the Management Interface</a></h2>
<p>You can also shut down all the server components using the
- jBoss management interface. See the
- <a HREF="managing.html">Managing a Live jBoss Server</a> section
+ JBoss management interface. See the
+ <a HREF="managing.html">Managing a Live JBoss Server</a> section
for more information.</p>
</body>
</html>
1.2 +2 -2 newsite/manual/support.html
Index: support.html
===================================================================
RCS file: /products/cvs/ejboss/newsite/manual/support.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- support.html 2000/11/12 20:32:14 1.1
+++ support.html 2001/02/08 05:31:41 1.2
@@ -1,9 +1,9 @@
<html>
<head>
- <title>jBoss 2.0: Support</title>
+ <title>JBoss 2.0: Support</title>
<link REL ="stylesheet" TYPE="text/css" HREF="manual.css" TITLE="Style" />
</head>
<body>
- <h1 ALIGN="CENTER">jBoss 2.0: Support</h1>
+ <h1 ALIGN="CENTER">JBoss 2.0: Support</h1>
</body>
</html>
1.3 +32 -32 newsite/manual/third_party.html
Index: third_party.html
===================================================================
RCS file: /products/cvs/ejboss/newsite/manual/third_party.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- third_party.html 2000/12/06 01:00:08 1.2
+++ third_party.html 2001/02/08 05:31:42 1.3
@@ -1,31 +1,31 @@
<html>
<head>
- <title>jBoss 2.0: Third-Party Software</title>
+ <title>JBoss 2.0: Third-Party Software</title>
<link REL ="stylesheet" TYPE="text/css" HREF="manual.css" TITLE="Style" />
</head>
<body>
- <h1 ALIGN="CENTER">jBoss 2.0: Third-Party Software</h1>
- <p>jBoss is designed to be modular and configurable, and thus should
+ <h1 ALIGN="CENTER">JBoss 2.0: Third-Party Software</h1>
+ <p>JBoss is designed to be modular and configurable, and thus should
integrate easily with a number of third-party packages. Here we
discuss some of the ones we already have configuration information
- for. If you'd like to integrate jBoss with something that is not
+ for. If you'd like to integrate JBoss with something that is not
listed here, or you already have and would like to share, please
- let us know on the jBoss
+ let us know on the JBoss
<a HREF="http://www.jboss.org/mailing.htm">Mailing List</a>.
<h2><a NAME="vm">About JVM Integration</a></h2>
- <p>In general, there are two ways to integrate jBoss with another
- package. The first is to integrate within the jBoss JVM.
+ <p>In general, there are two ways to integrate JBoss with another
+ package. The first is to integrate within the JBoss JVM.
Examples of this would include using a different Persistence
Manager or Transaction Manager, where it essentially runs as
- part of jBoss. The other way is to run outside the jBoss
+ part of JBoss. The other way is to run outside the JBoss
JVM. An example of this might be a management console that
- communicates with jBoss over the network. Some software can
+ communicates with JBoss over the network. Some software can
work either way: a servlet container, for example, may run in
the JVM for better performance or outside the JVM for better
flexibility.</p>
<p>Each approach has a most common trouble spot for integration.
- The problem with integration within the JVM is that jBoss uses
+ The problem with integration within the JVM is that JBoss uses
a number of ClassLoaders, and you must make sure that the other
package uses the correct ClassLoader at any given time - the
best way to do this is to use the JDK 1.2 API call
@@ -33,11 +33,11 @@
As for out-of-JVM integration, the most common problem is getting
the JNDI and RMI settings right for communicating over the
network (see <a HREF="clients.html#remote">Connecting To A
- Remote Server</a> in the <a HREF="clients.html">jBoss Clients</a>
+ Remote Server</a> in the <a HREF="clients.html">JBoss Clients</a>
section).</p>
<h2><a NAME="j2ee">J2EE</a></h2>
- <p>The most common need for J2EE is to integrate jBoss with a
+ <p>The most common need for J2EE is to integrate JBoss with a
servlet and JSP container. This alone does not yet provide a
full J2EE environment though - you also need JavaMail and JMS
integration, among other things. Here are the procedures for
@@ -48,20 +48,20 @@
container. You can integrate in the same VM or outside: full
integration gives the best performance but the least
flexibility, and it hardest to implement. In any of these
- cases, you can choose to locate your jBoss code at the top
+ cases, you can choose to locate your JBoss code at the top
level of Tomcat, or for individual web apps - but you cannot mix
- the two (for example, by putting jBoss JARs at the top level but
+ the two (for example, by putting JBoss JARs at the top level but
your EJB interfaces at the web app level). We strongly
- recommend locating all jBoss and EJB code at the web app level,
+ recommend locating all JBoss and EJB code at the web app level,
so that is how the directions are oriented.</p>
<h4><a NAME="tomcat-separate">Different JVMs</a></h4>
- <p>The easiest way to configure Tomcat and jBoss is to run them
+ <p>The easiest way to configure Tomcat and JBoss is to run them
completely separately. In this case, you just need to provide
- the jBoss and EJB client files for Tomcat:</p>
+ the JBoss and EJB client files for Tomcat:</p>
<dl>
- <dt>jBoss Libraries</dt>
- <dd>The following jBoss libraries should be copied to
+ <dt>JBoss Libraries</dt>
+ <dd>The following JBoss libraries should be copied to
<b>web app/WEB-INF/lib</b>: <code>jboss-client.jar</code>,
<code>jnp-client.jar</code>, <code>ejb.jar</code>,
<code>jta-spec1_0_1.jar</code>, and (for JDK <= 1.2.2 only)
@@ -83,14 +83,14 @@
</dl>
<h4><a NAME="tomcat-invm">Same JVM, Different ClassLoader</a></h4>
- <p>The next step of integration is to run Tomcat and jBoss in the
+ <p>The next step of integration is to run Tomcat and JBoss in the
same JVM, bet let them use their default ClassLoaders. This is
still quite easy to configure, and gives better performance
than the separate setup, but not as good as the fully integrated
configuration.</p>
- <p>You may still install Tomcat and jBoss in any way you like -
+ <p>You may still install Tomcat and JBoss in any way you like -
they do not need to be installed in the same location. You
- should place your jBoss client libraries and EJB client code
+ should place your JBoss client libraries and EJB client code
in your web app as above (for the non-integrated install).
However, you must perform the following additional steps to
enable the integrated configuration:</p>
@@ -126,7 +126,7 @@
must add a RequestInterceptor to the default Tomcat
configuration. This is global across all web apps, and is
generally a good idea when you're running in JDK 1.2 or
- greater, but it required for proper behavior with jBoss. The
+ greater, but it required for proper behavior with JBoss. The
configuration file you need to change is <b>server.xml</b>
and it is located in the <b>conf</b> directory under the
Tomcat install directory (jakarta-tomcat for the binary).
@@ -140,10 +140,10 @@
debug="0" />
</pre>
</dd>
- <dt>Enable Tomcat in jBoss</dt>
- <dd>To start Tomcat when you start jBoss, you need to edit
+ <dt>Enable Tomcat in JBoss</dt>
+ <dd>To start Tomcat when you start JBoss, you need to edit
the <b>jboss.conf</b> file located in the <b>conf</b>
- directory under your jBoss install directory. You need to uncomment
+ directory under your JBoss install directory. You need to uncomment
following entry:
<pre>
<MLET CODE = "org.jboss.tomcat.TomcatService" ARCHIVE="jboss.jar"
CODEBASE="../lib/ext/">
@@ -152,21 +152,21 @@
</dd>
</dl>
- <p>After that, when you start jBoss it will start Tomcat too,
- and when you shut down jBoss it will shut down Tomcat. If you
+ <p>After that, when you start JBoss it will start Tomcat too,
+ and when you shut down JBoss it will shut down Tomcat. If you
have any problems, make sure that all the environment variables
above are set correctly in your startup script.</p>
<h4><a NAME="tomcat-cl">Same JVM, Same ClassLoader</a></h4>
<p>This is the best-performing option. Again, you should first
- locate all the jBoss and EJB code as above (for the
+ locate all the JBoss and EJB code as above (for the
non-integrated install). Then perform the follow additional
steps to enable the fully integrated configuration:</p>
- <dt>Enable EmbeddedTomcat in jBoss</dt>
- <dd>To start EmbeddedTomcat when you start jBoss, again you need to edit
+ <dt>Enable EmbeddedTomcat in JBoss</dt>
+ <dd>To start EmbeddedTomcat when you start JBoss, again you need to edit
<dd>the <b>jboss.conf</b> file located in the <b>conf</b>
- <dd>directory under your jBoss install directory. You need to
+ <dd>directory under your JBoss install directory. You need to
<dd>uncomment the following entry:
<pre>
1.2 +2 -2 newsite/manual/trouble.html
Index: trouble.html
===================================================================
RCS file: /products/cvs/ejboss/newsite/manual/trouble.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- trouble.html 2000/11/12 20:32:15 1.1
+++ trouble.html 2001/02/08 05:31:42 1.2
@@ -1,9 +1,9 @@
<html>
<head>
- <title>jBoss 2.0: Troubleshooting</title>
+ <title>JBoss 2.0: Troubleshooting</title>
<link REL ="stylesheet" TYPE="text/css" HREF="manual.css" TITLE="Style" />
</head>
<body>
- <h1 ALIGN="CENTER">jBoss 2.0: Troubleshooting</h1>
+ <h1 ALIGN="CENTER">JBoss 2.0: Troubleshooting</h1>
</body>
</html>
1.2 +5 -5 newsite/manual/unix_start.html
Index: unix_start.html
===================================================================
RCS file: /products/cvs/ejboss/newsite/manual/unix_start.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- unix_start.html 2000/11/12 20:32:15 1.1
+++ unix_start.html 2001/02/08 05:31:42 1.2
@@ -1,11 +1,11 @@
<html>
<head>
- <title>jBoss 2.0: UNIX Startup Script</title>
+ <title>JBoss 2.0: UNIX Startup Script</title>
<link REL ="stylesheet" TYPE="text/css" HREF="manual.css" TITLE="Style" />
</head>
<body>
- <h1 ALIGN="CENTER">jBoss 2.0: UNIX Startup Script</h1>
- <p>You can use this script to start jBoss when your server starts,
+ <h1 ALIGN="CENTER">JBoss 2.0: UNIX Startup Script</h1>
+ <p>You can use this script to start JBoss when your server starts,
and shut it down gracefully when the server shuts down. It was
written and tested on Red Hat Linux, but should operate on other
similar UNIX platforms.</p>
@@ -20,11 +20,11 @@
stop" when the appropriate runlevel is entered, while if you start
the name with it with S## it will call "script start". In either
case, all the scripts to be started or stopped are called in the
- order of the ## in the symlink name, so you obviously want jBoss
+ order of the ## in the symlink name, so you obviously want JBoss
to start after and shut down before any networking services, at
least.</p>
<p>Here is the code for the script. Note that you can execute the
- jBoss startup script as a user other than root (see the commented
+ JBoss startup script as a user other than root (see the commented
out line under "start").</p>
<pre>
</pre>
1.2 +14 -14 newsite/manual/warning.html
Index: warning.html
===================================================================
RCS file: /products/cvs/ejboss/newsite/manual/warning.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- warning.html 2000/11/12 20:32:16 1.1
+++ warning.html 2001/02/08 05:31:42 1.2
@@ -1,14 +1,14 @@
<html>
<head>
- <title>jBoss 2.0: PRELIMINARY DOCUMENTATION</title>
+ <title>JBoss 2.0: PRELIMINARY DOCUMENTATION</title>
<link REL ="stylesheet" TYPE="text/css" HREF="manual.css" TITLE="Style" />
</head>
<body>
- <h1 ALIGN="CENTER">jBoss 2.0: PRELIMINARY DOCUMENTATION</h1>
+ <h1 ALIGN="CENTER">JBoss 2.0: PRELIMINARY DOCUMENTATION</h1>
<p>This manual is a work in progress. There are certainly entire
sections missing, but more importantly, not all of the information
has been verified. If you are having problems or think you've
- spotted a mistake, please post your concerns to the jBoss
+ spotted a mistake, please post your concerns to the JBoss
<a HREF="http://www.jboss.org/mailing.htm">Mailing List</a>.</p>
<p CLASS="tc2"><a NAME="todos">Documentation TODOs</a></h2>
@@ -53,11 +53,11 @@
confirmation, need to try.</li>
</ul>
</li>
- <li>Starting & Stopping jBoss
+ <li>Starting & Stopping JBoss
<ul>
<li>Need to create the shutdown script.</li>
<li>Need to figure out and clarify whether you can actually
- shut down jBoss via the management interface, or only
+ shut down JBoss via the management interface, or only
stop the EJBs/services leaving the original (now useless)
process running.</li>
</ul>
@@ -68,24 +68,24 @@
<li>Confirm Transaction content.</li>
</ul>
</li>
- <li>Deploying EJBs in jBoss
+ <li>Deploying EJBs in JBoss
<ul>
<li>Need detail on non-JDBC resource managers</li>
</ul>
</li>
- <li>JMS in jBoss
+ <li>JMS in JBoss
<ul>
<li>What would you use JMS for?</li>
<li>How do you access JMS? Through JNDI?</li>
- <li>Is SpyderMQ part of the default jBoss distribution?</li>
+ <li>Is SpyderMQ part of the default JBoss distribution?</li>
</ul>
</li>
- <li>Managing a Live jBoss Server
+ <li>Managing a Live JBoss Server
<ul>
<li>This section must be written</li>
</ul>
</li>
- <li>jBoss Clients
+ <li>JBoss Clients
<ul>
<li>Confirm host:port syntax of jndi.properties for
non-default JNP port settings</li>
@@ -94,7 +94,7 @@
</li>
<li>Third-Party Software
<ul>
- <li>Get procedures for total Tomcat+jBoss integration
+ <li>Get procedures for total Tomcat+JBoss integration
(ContextInterceptor must be written!)</li>
<li>Get procedures for Resin integration</li>
<li>Get procedures for Ozone integration</li>
@@ -106,7 +106,7 @@
<li>Get procedures for Forte integration</li>
</ul>
</li>
- <li>Extending jBoss
+ <li>Extending JBoss
<ul>
<li>This section must be written</li>
</ul>
@@ -148,12 +148,12 @@
<li>Need to test and include an actual script</li>
</ul>
</li>
- <li>jBoss Architecture
+ <li>JBoss Architecture
<ul>
<li>This section must be written</li>
</ul>
</li>
- <li>jBoss in Production
+ <li>JBoss in Production
<ul>
<li>This section must be written</li>
</ul>
