User: fleury
Date: 00/11/16 18:12:01
Modified: developers jboss-server.html
Log:
server updated
Revision Changes Path
1.4 +59 -1 newsite/developers/jboss-server.html
Index: jboss-server.html
===================================================================
RCS file: /products/cvs/ejboss/newsite/developers/jboss-server.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- jboss-server.html 2000/11/14 06:07:55 1.3
+++ jboss-server.html 2000/11/17 02:12:01 1.4
@@ -21,9 +21,67 @@
<td class="newsbody"><font
face="Myriad Web,Arial"><img height="60" width="159"
src="../pictures/powered_by_jboss_flat_sepia.gif"></font>
<p><font face="Myriad
Web,Arial">jBoss the container is an implementation of the EJB container
specification. </font></p>
<p><font face="Myriad
Web,Arial"><b>jBoss 2.0 is truly a 3rd generation container.</b> It takes the patterns
and ideas that were investigated in 1.0. Designed from the ground up to be
<b>modular</b>, jBoss introduces yet again many ground breaking features such as a
full <b>plug-in approach </b>to the container implementation. Borrowing from the
success that met with Linux 2.0 and it's modular approach to software implementation,
jBoss 2.0 is meant to be developed by distributed parties each working on a cleanly
separated part of the server. </font></p>
- <p><font face="Myriad
Web,Arial">jBoss 2.0 also standardizes on <b>JMX</b>, the Java Management eXtension
(TM) to offer standard interfaces to the management of its components as well as the
applications deployed on it. Ease of use is still the number one priority here at
jBoss and jBoss 2.0 will set a new standard.</font></td>
+
+ <p><font face="Myriad Web,Arial">jBoss 2.0 also standardizes on
<b>JMX</b>,
+ the Java Management eXtension (TM) to offer standard interfaces
+ to the management of its components as well as the applications
+ deployed on it. Ease of use is still the number one priority here
+ at jBoss and jBoss 2.0 will set a new standard.</font>
+ </td>
+ </tr>
+ <tr>
+ <td
class="newsheader"><b>Enterprise Java Beans Support</b></td>
</tr>
<tr>
+
+ <td class="newsbody"> Being both open and standards-compliant,
jBoss/Server
+ supports both EJB Session Beans and Entity Beans. EJB Session Beans
+ are responsible for implementing the business logic of your middle
+ tier application. As their name implies, they are also responsible
+ for handling the conversational session between the client side and
+ the middle tier. Sessions may be either stateless or stateful.
+<p> A stateless
+ session means that the Session Bean instance remembers no state between
+ calls from a given client object. A stateful session, on the other
+ hand, must maintain state data between separate remote method
invocations
+ by the same client. This implies that one Stateful Session Bean must
+ be allocated for each client creating it, and, therefore, requires
+ more resource and runtime overhead for the server, while a single
+ Stateless Session Bean may service multiple clients having overlapping
+ lifetimes. Entity Beans represent database entities and most often
+ a single Entity Bean maps to a single relational database table. Entity
+ Beans can be developed and deployed rapidly using Container Managed
+ Persistence (CMP) since all the object-to-relational database mapping
+ is managed by the jBoss/Server container. But if you must support
+ a complex and/or legacy database schema that does not easily map into
+ CMP, then for you the answer is Bean Managed Persistence (BMP). With
+ BMP you control the loading and saving of complex Entity Beans from
+ and to the database using fine-grained control to the SQL statement
+ level.
+ </tr>
+
+ <tr>
+ <td class="newsheader"><b>Modular Server Design</b></td>
+ </tr>
+ <tr>
+ <td class="newsbody">
+Modularly developed from the ground up, the jBoss server and container are
completely implemented using component-based plug-ins. Borrowing from the success of
Linux 2.0 and its modular approach to team-based, open source software implementation,
jBoss 2.0 is being developed by distributed team members, each working on a cleanly
separated part of the server. Our approach makes it easy for you to join our team and
contribute to the hottest open source J2EE server project around. It also ensures that
jBoss/Server will be maintained and extended for years to come.
+<p>
+The modularization effort is supported by the use of JMX, the Java Management
eXtension API. Using JMX, industry-standard interfaces help us manage both
jBoss/Server components and the applications deployed on it. Ease of use is still the
number one priority here at jBoss.org, and jBoss/Server 2.0 sets a new standard for
both modular, plug-in design and ease of server and application management.
+<p>
+This high degree of modularity benefits the application developer in several ways.
The already tight code can be further trimmed down in support of applications that
must have a very small footprint. For example, if EJB passivation is unnecessary in
your application, simply take the feature out of the server. However, if you later
decide to deploy the same application under an Application Service Provider (ASP)
model, simply enable the server's passivation feature for that Web-based deployment.
Another example is the freedom you have to drop your favorite O-R mapping tool, such
as TOPLink, right into the container.
+</tr>
+
+ <tr>
+ <td class="newsheader"><b>Features That Speed Development</b></td>
+ </tr>
+ <tr>
+ <td class="newsbody">In addition to the fact that jBoss/Server is an
EJB 1.1 compliant application server, there are some innovative features that make our
server a pleasure to use. Specifically two features make application deployment
extremely easy to perform, saving developers much time and effort. In a phrase,
jBoss/Server takes the grunt work out of EJB application development.
+<p>
+First there's dynamically, runtime-generated stub and skeleton classes. In many
commercial EJB servers the generation of these classes must be performed in an
additional step prior to deployment (e.g. using an "ebjc" tool). It goes without
saying that this extra step requires additional developer overhead, adding significant
time to each change-compile-deploy cycle. By generating stub and skeleton classes on
the fly, jBoss/Server takes at least several seconds, and perhaps minutes, off of each
deployment. As an added benefit, the method used by jBoss/Server to accomplish this
time- and effort-savings feature also saves memory and other server resources since
only a single server object supports every deployed Enterprise JavaBeans component!
+<p>
+A second time- and effort-savings feature is automatic hot deploy and redeploy.
Some of the top commercial EJB servers require you to "bounce" the server in order to
successfully deploy your application changes. However, jBoss/Server allows you to
deploy new applications and redeploy existing applications without stopping and
restarting the server. In fact, the feature is as easy as copying your newly built EJB
JAR file to the server deployment directory where jBoss/Server picks up the new file,
automatically undeploys the old JAR (if any) and deploys the new JAR within seconds.
This feature definitely provides the benefit of slicing minutes off of each
change-compile-deploy cycle.
+ <tr>
<td
class="newsheader"><b>Features</b></td>
</tr>
<tr>
