User: fleury
Date: 01/02/15 13:58:22
Modified: business jboss-server.html
Log:
updates to teh website layout,
new project updates
Revision Changes Path
1.3 +189 -122 newsite/business/jboss-server.html
Index: jboss-server.html
===================================================================
RCS file: /products/cvs/ejboss/newsite/business/jboss-server.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- jboss-server.html 2001/02/08 05:31:21 1.2
+++ jboss-server.html 2001/02/15 21:58:22 1.3
@@ -9,139 +9,206 @@
<body marginwidth="0" marginheight="0" onload="">
<table border="0" cellpadding="0" cellspacing="3">
<tr>
- <td width="600" valign="top">
- <table border="0" cellpadding="2"
cellspacing="0">
- <tr>
- <td
class="pageheader"><b>JBoss/Server</b></td>
- </tr>
- <tr>
- <td
class="newsheader"><b>JBoss/Server</b></td>
- </tr>
- <tr>
- <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>
-
+
+ <td width="600" valign="top">
+ <table border="0" cellpadding="2" cellspacing="0">
+ <tr>
+ <td class="pageheader"><b>JBoss/Server</b></td>
+ </tr>
+ <tr>
+ <td class="newsheader"><b>JBoss/Server</b></td>
+ </tr>
+ <tr>
+ <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>
+ 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>
-
+ </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>
- <td class="newsbody"><font
face="Myriad Web,Arial">We will make a feature matrix available here (under
construction)</font>
- <p><font face="Myriad
Web,Arial">JBoss 2.0</font></p>
- <ul>
- <li><font
face="Myriad Web,Arial">Full EJB 1.1 support (all beans, all persistent types and all
transactional tags supported)</font>
- <li><font
face="Myriad Web,Arial">XML compliant</font>
- <li><font
face="Myriad Web,Arial">JDK1.2.2 and up support</font>
- <li><font
face="Myriad Web,Arial">JNDI compliant</font>
- <li><font
face="Myriad Web,Arial">JTA/JTS compliant</font>
- <li><font
face="Myriad Web,Arial">JDBC compliant Container Managed Persistence</font>
- <li><font
face="Myriad Web,Arial">Most database vendors work out of the box </font>
- <li><font
face="Myriad Web,Arial">Easy-to-use standard configuration</font>
- <li><font
face="Myriad Web,Arial">Differential metadata, easy change</font>
- <li><font
face="Myriad Web,Arial">Fully modular for easy Integration</font>
- <li><font
face="Myriad Web,Arial">Integrated Pool Management</font>
- <li><font
face="Myriad Web,Arial">Integrated with CastorJDO</font>
- <li><font
face="Myriad Web,Arial">Integrated with CocoBase</font>
- <li><font
face="Myriad Web,Arial">Integrated with JBuilder</font>
- <li><font
face="Myriad Web,Arial">Integrated with Tomcat</font>
- <li><font
face="Myriad Web,Arial">Integrated with JAAS for security</font>
- <li><font
face="Myriad Web,Arial">Integrated with SOAP for invocation</font>
- <li><font
face="Myriad Web,Arial">InVM stack optimization with Tomcat</font>
- <li><font
face="Myriad Web,Arial">Optimized J2EE stack</font>
- <li><font
face="Myriad Web,Arial">State of the art EAR Deployment technology</font>
- <li><font
face="Myriad Web,Arial">Fast Cache technology</font>
- <li><font
face="Myriad Web,Arial">Resilient and fail safe keys</font>
- <li><font
face="Myriad Web,Arial">Advanced O/R mapping technology</font>
- <li><font
face="Myriad Web,Arial">Automated Table creation</font>
- <li><font
face="Myriad Web,Arial">Easy to use GUI</font>
- <li><font
face="Myriad Web,Arial">Remote Administration </font>
- <li><font
face="Myriad Web,Arial">HTTP administration</font>
- <li><font
face="Myriad Web,Arial">RMI administration</font>
- <li><font
face="Myriad Web,Arial">JMX compatible </font>
- <li><font
face="Myriad Web,Arial">Passivating Caches</font>
- <li><font
face="Myriad Web,Arial">Stable Open source technology, runs for weeks with >100,000
beans uninterrupted</font>
- <li><font
face="Myriad Web,Arial">Scalable Open Source technology, can handle 1000's of
concurent requests on 1 bean</font>
- <li><font
face="Myriad Web,Arial">Excellent support available</font>
- <li><font
face="Myriad Web,Arial">And much much more</font>
- </ul>
- </td>
- </tr>
- <tr>
- <td
class="newsheader"><b>Mailing Lists</b></td>
- </tr>
- <tr>
- <td class="newsbody"><a
href="lists.html"><font face="Myriad Web,Arial">[EMAIL PROTECTED]
</font></a>
- <p><font face="Myriad
Web,Arial">This list is dedicated to support and user discussions about jboss traffic
is medium-heavy to heavy (20-50 mails/day). Many world expert answer questions on this
list. </font></p>
- <p><a
href="lists.html"><font face="Myriad
Web,Arial">[EMAIL PROTECTED]</font></a></p>
- <p><font face="Myriad
Web,Arial">This list is dedicated to the development of jboss. The traffic is low
noise high quality and medium (20 mails/day). Some of the world's most advanced java
technology is invented here.</font></td>
- </tr>
- <tr>
- <td
class="newsheader"><b>Distribution and CVS</b></td>
- </tr>
- <tr>
- <td class="newsbody"><font
face="Myriad Web,Arial">JBoss/Server is part of the <a href="binary.html">JBoss/Server
distribution</a></font>
- <p><font face="Myriad
Web,Arial">CVS module is <a href="cvs.html">jboss</a></font></td>
- </tr>
- </table>
+ <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"><a name="features"></a><b>Features</b></td>
+ </tr>
+ <tr>
+ <td class="newsbody">
+ <p><font face="Myriad Web,Arial">JBoss 2.0</font></p>
+ <ul>
+ <li><font face="Myriad Web,Arial">Full EJB 1.1 support (all beans,
+ all persistent types and all transactional tags supported)</font>
+ <li><font face="Myriad Web,Arial">Partial EJB 2.0 support (Home
+ methods and Message Driven beans are supported)</font>
+ <li><font face="Myriad Web,Arial">XML compliant</font>
+ <li><font face="Myriad Web,Arial">JDK1.2.2 and up support</font>
+ <li><font face="Myriad Web,Arial">JNDI compliant</font>
+ <li><font face="Myriad Web,Arial">JTA/JTS compliant</font>
+ <li><font face="Myriad Web,Arial">JDBC compliant Container
+ Managed Persistence</font>
+ <li><font face="Myriad Web,Arial">Most database vendors work out
+ of the box </font>
+ <li><font face="Myriad Web,Arial">Easy-to-use standard
configuration</font>
+ <li><font face="Myriad Web,Arial">Differential metadata, easy
change</font>
+ <li><font face="Myriad Web,Arial">Fully modular for easy
Integration</font>
+ <li><font face="Myriad Web,Arial">Integrated Pool Management</font>
+ <li><font face="Myriad Web,Arial">Integrated with CastorJDO</font>
+ <li><font face="Myriad Web,Arial">Integrated with CocoBase</font>
+ <li><font face="Myriad Web,Arial">Integrated with JBuilder</font>
+ <li><font face="Myriad Web,Arial">Integrated with Tomcat</font>
+ <li><font face="Myriad Web,Arial">Integrated with JAAS for
security</font>
+ <li><font face="Myriad Web,Arial">Integrated with SOAP for
+ invocation</font>
+ <li><font face="Myriad Web,Arial">InVM stack optimization with
+ Tomcat</font>
+ <li><font face="Myriad Web,Arial">Optimized J2EE stack</font>
+ <li><font face="Myriad Web,Arial">State of the art
EAR Deployment
+ technology</font>
+ <li><font face="Myriad Web,Arial">Fast Cache technology</font>
+ <li><font face="Myriad Web,Arial">Resilient and fail safe keys</font>
+ <li><font face="Myriad Web,Arial">Advanced O/R mapping
technology</font>
+ <li><font face="Myriad Web,Arial">Automated Table creation</font>
+ <li><font face="Myriad Web,Arial">Easy to use GUI</font>
+ <li><font face="Myriad Web,Arial">Remote Administration </font>
+ <li><font face="Myriad Web,Arial">HTTP administration</font>
+ <li><font face="Myriad Web,Arial">RMI administration</font>
+ <li><font face="Myriad Web,Arial">JMX compatible </font>
+ <li><font face="Myriad Web,Arial">Passivating Caches</font>
+ <li><font face="Myriad Web,Arial">Stable Open source technology,
+ runs for weeks with >100,000 beans uninterrupted</font>
+ <li><font face="Myriad Web,Arial">Scalable Open Source technology,
+ can handle 1000's of concurent requests on 1 bean</font>
+ <li><font face="Myriad Web,Arial">Excellent support available</font>
+ <li><font face="Myriad Web,Arial">And much much more</font>
+ </ul>
+ </td>
+ </tr>
+ <tr>
+ <td class="newsheader"><b>Mailing Lists</b></td>
+ </tr>
+ <tr>
+ <td class="newsbody"><a href="lists.html"><font face="Myriad
Web,Arial">[EMAIL PROTECTED]
+ </font></a>
+ <p><font face="Myriad Web,Arial">This list is dedicated to support
+ and user discussions about jboss traffic is medium-heavy to heavy
+ (20-50 mails/day). Many world expert answer questions on this list.
+ </font></p>
+ <p><a href="lists.html"><font face="Myriad
Web,Arial">[EMAIL PROTECTED]</font></a></p>
+ <p><font face="Myriad Web,Arial">This list is dedicated to the
development
+ of jboss. The traffic is low noise high quality and medium (20
mails/day).
+ Some of the world's most advanced java technology is invented
here.</font>
+ </td>
+ </tr>
+ <tr>
+ <td class="newsheader"><b>Distribution and CVS</b></td>
+ </tr>
+ <tr>
+ <td class="newsbody"><font face="Myriad Web,Arial">JBoss/Server is part
+ of the <a href="binary.html">JBoss/Server distribution</a></font>
+ <p><font face="Myriad Web,Arial">CVS module is <a
href="cvs.html">jboss</a></font>
+ </td>
+ </tr>
+ </table>
</td>
</tr>
<tr>
