geronimo-scm mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From geronimo-...@incubator.apache.org
Subject [Apache Geronimo Wiki] Updated: FrequentlyAskedQuestions
Date Tue, 15 Jun 2004 11:38:30 GMT
   Date: 2004-06-15T04:38:30
   Editor: 195.212.97.114 <>
   Wiki: Apache Geronimo Wiki
   Page: FrequentlyAskedQuestions
   URL: http://wiki.apache.org/geronimo/FrequentlyAskedQuestions

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -82,5 +82,5 @@
 A GBean is a class or object that Geronimo the container can manage the lifecycle of. So,
for example, when you deploy parts into a container you want to start them and stop them,
and they have dependencies: Such as 'Bean A' can only start up when 'Bean B' is ready to go
because 'Bean B' provides services that 'Bean A' needs. So, GBeans are Geronimo's way of packaging
up things are that need to be managed, and can express dependencies.
 The GBeans architecture lies at the heart of Geronimo's power to enable developers to move
or work with their existing J2EE assets, whether Open Source or commercial.
 
-GBeans are designed to let you take things you have, put a GBean wrapper around them, and
use that to bridge the JSR 77 lifecycle requirements which GBeans support). You can take anything
lying around and get it to work with GBeans. In addition, the GBeans will let developers bring
other existing Open Source Java projects into the Geronimo orbit.
+GBeans are designed to let you take things you have, put a GBean wrapper around them, and
use that to bridge the JSR 77 lifecycle requirements which GBeans support). You can take anything
lying around and get it to work with GBeans. In addition, the GBeans will let developers bring
other existing Open Source Java projects into the Geronimo orbit..
  

Mime
View raw message