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: GBeans
Date Wed, 08 Sep 2004 15:53:30 GMT
   Date: 2004-09-08T08:53:30
   Editor: EkiBaskoro <eki.baskoro@sonet.net.au>
   Wiki: Apache Geronimo Wiki
   Page: GBeans
   URL: http://wiki.apache.org/geronimo/GBeans

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -1,21 +1,23 @@
-= GBeans =
+'''Content'''
+[[TableOfContents]]
+
+= Overview =
 
 A GBeanMBean is a J2EE Management Managed Object, and is standard base for Geronimo services.
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. 
 
 This wraps one or more target POJOs and exposes the attributes and operations according to
a supplied
-GBeanInfo instance.  The GBeanMBean also supports caching of attribute values and invocation
results
+[wiki:/GBeanInfo GBeanInfo] instance.  The GBeanMBean also supports caching of attribute
values and invocation results
 which can reduce the number of calls to a target.
 
  * Gbeans are way of providing managements services to Geronimo
  * It is implemented on top of the JMX right now but supposes to be independent of JMX. User
should be able to use them without knowledge of the JMX. And it can be make independent of
GBeans .
  * The GBean can be converted into the MBean using the GBeanMBean and use the JMX to give
the services
 
-== how to find Sample GBeans ==
+== How to find sample GBeans ==
 
-**search for all the implementetors of the GBeanLifecycle is a good way to **find example**
of the GBeans
-and I found the jetty module and the GBeanTest class quite helpful
+**search for all the implementetors of the [wiki:/GBeanLifecycle GBeanLifecycle] is a good
way to **find example** of the GBeans and I found the jetty module and the GBean``Test class
quite helpful
 
 
 == Creating a GBean like follows ==
@@ -24,7 +26,7 @@
 
 
 == Let us Write a GBean ==
- * A GBean may implement the org.apache.geronimo.gbean.GBeanLifecycle interface. If it implements
this interface, then it will receive life-cycle call-backs from the IoC framework.
+ * A GBean may implement the org.apache.geronimo.gbean.[wiki:/GBeanLifecycle GBeanLifecycle]
interface. If it implements this interface, then it will receive life-cycle call-backs from
the IoC framework.
  * They can have attributes with getters and setters, There are attributes that are final
and I think they are standard .. (What is the list of them) e.g. name, Kernel (they can use
to get hold of the system info, have a look at the sample GBeans.) There are ordinary attributes
.. have getters and setters
 
  * GBeans can have methods ..

Mime
View raw message