geronimo-scm mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Geronimo Wiki] Trivial Update of "Architecture/Kernel/Avalon" by PavelJanousek
Date Wed, 08 Mar 2006 13:04:56 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Geronimo Wiki" for change notification.

The following page has been changed by PavelJanousek:
http://wiki.apache.org/geronimo/Architecture/Kernel/Avalon

------------------------------------------------------------------------------
  
  = Questions =
  
- ;Q. How easily can Avalon be integrated with a ConfigurationAsRegistry to store its backend
in a naming service (like JNDI?) : A. Avalon already has a utility to read an LDAP repository
and create a Configuration object tree from that.  By default Avalon assumes a hierarchical
configuration space, and maps nicely to XML and LDAP.  It should be relatively easy to write
new adapters to read in the configuration information.  No matter what the choice, the components
have one configuration interface to read from.  Alternatively, Avalon Merlin and Avalon Fortress
support the notion of Lifecycle Extensions which allow the user to define their own lifecycle
stages and pass in the important objects at init-time or lookup-time.  For example, a JNDI
Context can be passed in as a Lifecycle Extension.
+ Q. How easily can Avalon be integrated with a ConfigurationAsRegistry to store its backend
in a naming service (like JNDI)? 
+ 
+ A. Avalon already has a utility to read an LDAP repository and create a Configuration object
tree from that.  By default Avalon assumes a hierarchical configuration space, and maps nicely
to XML and LDAP.  It should be relatively easy to write new adapters to read in the configuration
information.  No matter what the choice, the components have one configuration interface to
read from.  Alternatively, Avalon Merlin and Avalon Fortress support the notion of Lifecycle
Extensions which allow the user to define their own lifecycle stages and pass in the important
objects at init-time or lookup-time.  For example, a JNDI Context can be passed in as a Lifecycle
Extension.
  
  ;Q. ... :A. ... 
  

Mime
View raw message