This is a good goal - try things out in separate containers and then
merge back the code into the core.

The problem is that such merges often take on the form:

   "This code works well in X. So we'll just put it in the core
    as it is, and no changes are allowed."

Instead of looking at the concepts of that code, and, allowing it to
change, get merged into the core:

   "These ideas works well in X, let's see if and when and in what form 
    we can get them into the core."

I think this was what caused the last eruption.

If anything, this is what we need to work on. Learning not to lock
ourselves into our own idea just because we like it the most.

/LS

  <type>
    <info>
      <name>my-component</name>
      <version>1.2.1</version>
      <attributes>
         <attribute key="color" value="blue"/>
         <attribute key="quantity" value="35"/>
      </attributes>
    </info>

    <loggers>
      <logger name="store"/>
      <logger name="store.cache"/>
      <logger name="verifier"/>
    </loggers>

    <context type="MyContextInterface">
      <entry key="base" type="java.io.File"/>
      <entry key="mode" optional="TRUE"/>
    </context>

    <services>
      <service>
        <reference type="SimpleService" version="3.2">
        <attributes/>
      </service>
    </services>

    <dependencies>
      <dependency optional="FALSE"
        key="my-transformer"
        type="org.apache.cocoon.api.Transformer
        version="1.1">
        <attributes/>
      </dependency>
    </dependencies>
  </type>

#Meta information for org.apache.avalon.fortress.examples.components.TranslatorImpl
#Mon Mar 08 10:59:53 EST 2004
x-avalon.lifestyle=singleton
x-avalon.name=translator

org.apache.avalon.fortress.examples.components.TranslatorImpl

<?xml version="1.0"?>

<fortress-roles logger="system.roles">

  <role name="org.apache.avalon.examples.simple.Simple">
    <component shorthand="simple"
               class="org.apache.avalon.examples.simple.impl.SimpleConfigurationImpl"
               handler="org.apache.avalon.fortress.impl.handler.ThreadSafeComponentHandler"/>
  </role>

</fortress-roles>

<?xml version="1.0"?>

<blockinfo>

    <block>
        <version>1.2.3</version>
    </block>

    <services>
        <service name="com.biz.cornerstone.services.MyService"
                 version="2.1.3" />
    </services>

    <dependencies>
        <dependency>
            <role>com.biz.cornerstone.services.Authorizer</role>
            <service name="com.biz.cornerstone.service.Authorizer"
                     version="1.2"/>
        </dependency>
        <dependency>
            <!-- note that role is not specified and defaults
                 to name of service. The service version is not
                 specified and it defaults to "1.0" -->
            <service name="com.biz.cornerstone.service.RoleMapper"/>
        </dependency>
    </dependencies>

</blockinfo>

   These are passed to the components.  Please note that "context-root" was at one time
   "app.home" until it got changed--I cannot remember the circumstances of that change.

   * impl.workDir        File (directory)  temporary directory
   * context-root        File (directory)  Context directory
   * component.logger          String   Component logger name
   * component.id              String   ID used to locate the component

 
urn:avalon:partition     String            partition name
urn:avalon:name          String            component/scenerio name
urn:avalon:home          File (directory)  persistent directory
urn:avalon:temp          File (directory)  temporary directory
urn:avalon:classloader   ClassLoader       component classloader
 

 
app.name                 String            application name
block.name               String            component name
app.home                 File (directory)  persistent directory