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 Wed, 05 Jan 2005 22:44:50 GMT
   Date: 2005-01-05T14:44:49
   Editor: TobyCabot
   Wiki: Apache Geronimo Wiki
   Page: GBeansArticle1
   URL: http://wiki.apache.org/geronimo/GBeansArticle1

   grammar tweaks (life cycle)

Change Log:

------------------------------------------------------------------------------
@@ -68,7 +68,7 @@
 
 == GBean Life Cycle ==
 
-GBean can be in any of the three states stored, loaded and running where the stored state
it is saved in a configuration store or saved in a plan. When it is loaded the kernel mapped
it to a name and knows about it. Each GBeans is a bind with a name at start up and that name
is not persistent. This can be explained by an analogy, we can think about the GBean as a
Java Class and the name as a variable name the where the compiler bind to the specific instance
of the class. In the same way the class can have more than one instance   the same GBean can
be loaded under more than one name and stored in number of places. 
+A GBean can be in any of the three states: ''stored'', ''loaded'' or ''running''.  In the
''stored'' state it is saved in a configuration store (also known as a "plan").  When it is
''loaded'' the kernel has mapped it to a name and knows about it.  Each GBean is bound with
a name at start up; that name is not persistent. This can be explained by an analogy, we can
think about the GBean as a Java Class and the name as a variable name that refers to a specific
instance of the class. In the same way that the class can have more than one instance, the
same GBean can be loaded under more than one name and stored in number of places. 
 
 == State of GBeans ==
 

Mime
View raw message