geronimo-scm mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From s..@geronimo.apache.org
Subject [Apache Geronimo Wiki] Updated: GBeansArticle1
Date Tue, 21 Dec 2004 04:16:54 GMT
   Date: 2004-12-20T20:16:54
   Editor: SrinathPerera <hemapani@opensource.lk>
   Wiki: Apache Geronimo Wiki
   Page: GBeansArticle1
   URL: http://wiki.apache.org/geronimo/GBeansArticle1

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -15,12 +15,13 @@
  1. Relationships among the GBeans can be defined with them
  1. GBeans can contains logic that defines how the GBeans react to the events that occurred
 
-	Almost Everything in Geronimo is a GBean, Containers, Connectors, adapters, application
so on. GBeans generated a Mesh of component as Explained by the following figure. 
+Almost Everything in Geronimo is a GBean, Containers, Connectors, adapters, application so
on. GBeans generated a Mesh of component as Explained by the following figure. 
 
+http://apache.org/~hemapani/images/geronimo-gbean-archi.png
 
-	J2EE Container comprised of two types of Citizens, the first class citizens like Web Container,
EJB Containers who provides the core services, And the second class citizens which are the
applications deployed in the first class citizens like EJBs and Servlets.
-	The architecture of the Geronimo can be explained in terms of GBeans behaviors. All the
time the Geronimo is set of running GBeans, and each First class Citizen is a set of GBeans
that are related and they are loaded via the plans which are essentially a XML serialization
of GBeans. When the plans are loaded and started the GBeans that included in the plans will
be started and in simple words the EJB Containers or the Web Container will be started. 
-	The applications that run in a J2EE Container are explained by the Deployment Descriptors
and the Java Classes that are packed as a j2ee application archive. Geronimo Deployer parses
those archives that explains the J2EE application and constructs GBeans out of them. When
those constructed GBeans are started the j2ee application is deployed and available inside
the J2EE Container. Those GBeans can be serialized and stored and as a result once an application
is converted to GBean and added to the Geronimo it will be available even after the server
is restarted. 
+J2EE Container comprised of two types of Citizens, the first class citizens like Web Container,
EJB Containers who provides the core services, And the second class citizens which are the
applications deployed in the first class citizens like EJBs and Servlets.
+The architecture of the Geronimo can be explained in terms of GBeans behaviors. All the time
the Geronimo is set of running GBeans, and each First class Citizen is a set of GBeans that
are related and they are loaded via the plans which are essentially a XML serialization of
GBeans. When the plans are loaded and started the GBeans that included in the plans will be
started and in simple words the EJB Containers or the Web Container will be started. 
+The applications that run in a J2EE Container are explained by the Deployment Descriptors
and the Java Classes that are packed as a j2ee application archive. Geronimo Deployer parses
those archives that explains the J2EE application and constructs GBeans out of them. When
those constructed GBeans are started the j2ee application is deployed and available inside
the J2EE Container. Those GBeans can be serialized and stored and as a result once an application
is converted to GBean and added to the Geronimo it will be available even after the server
is restarted. 
 
 == GBeans in a Conceptual point of View ==
 

Mime
View raw message