incubator-composer-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ma...@apache.org
Subject svn commit: r618243 [2/2] - in /incubator/composer/trunk/composer-site/src/site: content/ content/antipatterns/ content/help/ templates/
Date Mon, 04 Feb 2008 11:44:05 GMT
Modified: incubator/composer/trunk/composer-site/src/site/content/mock-objects.html
URL: http://svn.apache.org/viewvc/incubator/composer/trunk/composer-site/src/site/content/mock-objects.html?rev=618243&r1=618242&r2=618243&view=diff
==============================================================================
--- incubator/composer/trunk/composer-site/src/site/content/mock-objects.html (original)
+++ incubator/composer/trunk/composer-site/src/site/content/mock-objects.html Mon Feb  4 03:43:57 2008
@@ -5,7 +5,7 @@
 <title>Mock Objects</title>
 </head>
 <body>
-<p>If you have had it with codebases that drag along everything and the kitchen sink, (possibly using the <a href="singleton-antipattern.html">Singleton</a>) you must read this page. Classes that look up or instantiate heavyweight classes themselves are such beasts. As you might have experienced, they are a pain to test. (And ample proof that the authors didn't follow TDD <img src="/images/thumbs_down.gif" width="19" height="19" alt="thumbs down" />). Dependency Injection with Apache Composer and Mock Objects to the rescue!</p>
+<p>If you have had it with codebases that drag along everything and the kitchen sink, (possibly using the <a href="singleton-antipattern.html">Singleton</a>) you must read this page. Classes that look up or instantiate heavyweight classes themselves are such beasts. As you might have experienced, they are a pain to test. (And ample proof that the authors didn't follow TDD <img src="/images/thumbs_down.gif" width="19" height="19" alt="thumbs down" />). Dependency Injection with Container and Mock Objects to the rescue!</p>
 <p>Mock Objects are special objects used during testing. Mock Objects and classes that honour <a href="injection.html">Constructor Injection</a> are a <strong>perfect match</strong>, since such classes can be handed mocks during testing and &quot;the real thing&quot; when the application is run.</p>
 <p>This illustration shows how:</p>
 <table border="0">
@@ -55,7 +55,7 @@
 <p> <img src="/images/information.gif" width="16" height="16" alt="info" /> We won't go into further technical details about mocks, as there are many libraries to choose from. Check out <a href="http://www.jmock.org/">JMock</a> and <a href="http://www.easymock.org/">EasyMock</a>, or read about the ideas at <a href="http://www.mockobjects.com/">MockObjects</a> </p>
 <h3>Prime Time
 </h3>
-<p>It is left to Apache Composer to instantiate NeedsStuff. In order for it to succeed, we must also configure the container with some real BlueStuff and GreanStuff:</p>
+<p>It is left to Container to instantiate NeedsStuff. In order for it to succeed, we must also configure the container with some real BlueStuff and GreanStuff:</p>
 <div class="source"><pre>
 public class AppBootstrapper {
   public void runapp() {

Modified: incubator/composer/trunk/composer-site/src/site/content/monitors.html
URL: http://svn.apache.org/viewvc/incubator/composer/trunk/composer-site/src/site/content/monitors.html?rev=618243&r1=618242&r2=618243&view=diff
==============================================================================
--- incubator/composer/trunk/composer-site/src/site/content/monitors.html (original)
+++ incubator/composer/trunk/composer-site/src/site/content/monitors.html Mon Feb  4 03:43:57 2008
@@ -4,7 +4,7 @@
 <head>
 <title>Component Monitors</title></head>
 <body>
-<p>A ComponentMonitor if injected into DefultApache Composer allows for certain events to me monitored at a container level. We are idealogically opposed to a forced choice of loging framework. If you're hell bent on logging, chose from a  ComponentMonitor imlementation below. For now though consider what events are monitored:</p>
+<p>A ComponentMonitor if injected into DefultContainer allows for certain events to me monitored at a container level. We are idealogically opposed to a forced choice of loging framework. If you're hell bent on logging, chose from a  ComponentMonitor imlementation below. For now though consider what events are monitored:</p>
 <ul>
   <li>instantiating - refering to a component </li>
   <li>instantiated - refering to a component</li>
@@ -13,7 +13,7 @@
   <li>invoked - refering to a method on a component </li>
   <li>invocationFailed - refering to a method on a component </li>
   <li>lifecycleInvocationFailed - referring to start/stop/dispose methods on a component </li>
-  <li>noComponentFound - referring to getComponent(..) on a Apache Composer instance. </li>
+  <li>noComponentFound - referring to getComponent(..) on a Container instance. </li>
 </ul>
 <p><strong>Return Values </strong></p>
 <p><em>Instantiating</em> returns a Constructor. An implementor of ComponentMonitor can choose to return a different Constructor reference. This is one way that implementations can be replaced or decorated (AOP style) with additional/changed functionality. </p>
@@ -22,7 +22,7 @@
 <ol>
   <li>ComponentMonitor can generally be chained together. Meaning you can use them in combination. </li>
   <li>Most have NullComponentMonitor (see below) as their end stop. </li>
-  <li>Any method on ComponentMonitor is open for interpretation. That means they can throw exceptions as well as return different values, making them modify Apache Composer's behavior. </li>
+  <li>Any method on ComponentMonitor is open for interpretation. That means they can throw exceptions as well as return different values, making them modify Container's behavior. </li>
 </ol>
 <h3>Logging or text-centric varieties of ComponentMonitor </h3>
 <p>Hopefully self explanatory:</p>
@@ -33,7 +33,7 @@
   <li>WriterComponentMonitor</li>
 </ul>
 <h3>NullComponentMonitor</h3>
-<p>This is Apache Composer's default ComponentMonitor. It generally fits the NullObject pattern, but it does add behavior. Specifically if it encounters a lifecycleInvocationFailed(..) method invocation, it throws a LifecycleException in response. If you use something other than NullComponentMonitor (bear in mind the default 'end stop' for most others is also NullComponentMonitor) then you could change the way Apache Composer responds to components it cannot start, stop of dispose of. </p>
+<p>This is Container's default ComponentMonitor. It generally fits the NullObject pattern, but it does add behavior. Specifically if it encounters a lifecycleInvocationFailed(..) method invocation, it throws a LifecycleException in response. If you use something other than NullComponentMonitor (bear in mind the default 'end stop' for most others is also NullComponentMonitor) then you could change the way Container responds to components it cannot start, stop of dispose of. </p>
 <h3>LifecycleComponentMonitor</h3>
 <p>This  ComponentMonitor stores lifecycle failures and rethrows them later if rethrowLifecycleFailuresException() is called. </p>
 <h3>Future work</h3>

Modified: incubator/composer/trunk/composer-site/src/site/content/news.html
URL: http://svn.apache.org/viewvc/incubator/composer/trunk/composer-site/src/site/content/news.html?rev=618243&r1=618242&r2=618243&view=diff
==============================================================================
--- incubator/composer/trunk/composer-site/src/site/content/news.html (original)
+++ incubator/composer/trunk/composer-site/src/site/content/news.html Mon Feb  4 03:43:57 2008
@@ -6,7 +6,7 @@
 </head>
 <body>
 <p><strong>Jan 19, 2008</strong></p>
-<p>Apache Composer 2.0 released (190K jar) </p>
+<p>Container 2.0 released (190K jar) </p>
 <p>New (versus beta 2):</p>
 <ul>
   <li>Binding Annotations support (disambiguation)</li>
@@ -16,11 +16,11 @@
 <p>Changed (versus beta 2):</p>
 <ul>
   <li>Yet More Java5 generics</li>
-  <li>Build moved to JUnit 4.x and JMock 2.x (does not affect users of Apache Composer)</li>
+  <li>Build moved to JUnit 4.x and JMock 2.x (does not affect users of Container)</li>
   <li>Built-in parameter name access, as opposed jar dependency</li>
 </ul>
 <p><strong>August 26, 2007</strong></p>
-<p>Apache Composer 2.0 beta 2 released (152K jar) </p>
+<p>Container 2.0 beta 2 released (152K jar) </p>
 <p>New (versus beta 1):</p>
 <ul>
   <li>Rudimentary AOP capability for components built in</li>
@@ -38,7 +38,7 @@
   <li>Startable interface more easily overridden to own choice</li>
 </ul>
 <p><strong>July 15, 2007</strong></p>
-<p>Apache Composer 2.0 BETA-1 released (128K jar) </p>
+<p>Container 2.0 BETA-1 released (128K jar) </p>
 <p>New:</p>
 <ul>
   <li>Properties for components as they are added to containers makes for increased flexibility</li>
@@ -54,15 +54,15 @@
   <li>Fluent interface for adding of components to a container</li>
 </ul>
 <p><strong>Mar 18, 2007</strong></p>
-<p>Apache Composer 1.3 released (113K jar) </p>
+<p>Container 1.3 released (113K jar) </p>
 <p><strong>January 19, 2006</strong></p>
-<p>Apache Composer 1.2 released (112K jar) </p>
+<p>Container 1.2 released (112K jar) </p>
 <p><strong>November 4, 2004</strong></p>
-<p>Apache Composer 1.1 released (75K jar) </p>
+<p>Container 1.1 released (75K jar) </p>
 <p><strong>June 5,  2004</strong></p>
-<p>Apache Composer 1.0 released (49K jar) </p>
+<p>Container 1.0 released (49K jar) </p>
 <p><strong>June 29,  2003</strong></p>
-<p>Apache Composer 1.0 alpha (25K jar) </p>
+<p>Container 1.0 alpha (25K jar) </p>
 <p></p>
 <p>&nbsp; </p>
 <p>&nbsp;</p>

Modified: incubator/composer/trunk/composer-site/src/site/content/project.html
URL: http://svn.apache.org/viewvc/incubator/composer/trunk/composer-site/src/site/content/project.html?rev=618243&r1=618242&r2=618243&view=diff
==============================================================================
--- incubator/composer/trunk/composer-site/src/site/content/project.html (original)
+++ incubator/composer/trunk/composer-site/src/site/content/project.html Mon Feb  4 03:43:57 2008
@@ -5,11 +5,11 @@
     <title>Project</title>
 </head>
 <body>
-<p>Apache Composer is hosted at <a href="http://apache.org">The Apache Software Foundation</a>, presently in its incubator. </p>
+<p>Container is hosted at <a href="http://apache.org">The Apache Software Foundation</a>, presently in its incubator. </p>
 
 <h2>Project links</h2>
 
-<p>Source control root for Apache Composer (you will need Maven2 installed to build):</p>
+<p>Source control root for Container (you will need Maven2 installed to build):</p>
 
 <p><a
     href="https://svn.apache.org/repos/asf/incubator/composer/trunk">https://svn.apache.org/repos/asf/incubator/composer/trunk</a>
@@ -21,7 +21,7 @@
 
 <h2>License</h2>
 
-<p>Apache Composer is <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache licensed</a>.
+<p>Container is <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache licensed</a>.
 
 </body>
 </html>

Copied: incubator/composer/trunk/composer-site/src/site/content/properties-container.html (from r618229, incubator/composer/trunk/composer-site/src/site/content/PropertiesContainer.html)
URL: http://svn.apache.org/viewvc/incubator/composer/trunk/composer-site/src/site/content/properties-container.html?p2=incubator/composer/trunk/composer-site/src/site/content/properties-container.html&p1=incubator/composer/trunk/composer-site/src/site/content/PropertiesContainer.html&r1=618229&r2=618243&rev=618243&view=diff
==============================================================================
--- incubator/composer/trunk/composer-site/src/site/content/PropertiesContainer.html (original)
+++ incubator/composer/trunk/composer-site/src/site/content/properties-container.html Mon Feb  4 03:43:57 2008
@@ -2,12 +2,12 @@
 
 <html>
 <head>
-<title>PropertiesApache Composer</title>
+<title>PropertiesContainer</title>
 </head>
 <body>
 <p>
-PropertiesApache Composer is a special type of Apache Composer that is populated from the entries in a properties file. 
-<p>Here is an example of how to use PropertiesApache Composer to map properties  as configuration for a component, with parameter names as the bindings.<br />
+PropertiesContainer is a special type of Container that is populated from the entries in a properties file. 
+<p>Here is an example of how to use PropertiesContainer to map properties  as configuration for a component, with parameter names as the bindings.<br />
 <p>Consider this component:
 <div class="source">
     <pre>public class BigFatComponent {
@@ -32,9 +32,9 @@
 defaultProperties.load("my-application.properties");
         
 // default properties are taken from here
-Apache Composer propsContainer = new PropertiesApache Composer(defaultProperties);
+Container propsContainer = new PropertiesContainer(defaultProperties);
                 
-MutableApache Composer mpc = new DefaultApache Composer(propsContainer);
+MutableContainer mpc = new DefaultContainer(propsContainer);
                 
 mpc.as(Characteristics.USE_NAMES).addComponent(BigFatComponent.class);
 </pre>
@@ -53,7 +53,7 @@
           <li> java.sql.(Date|Time|Timestamp) </li>
           <li> Any type sporting accessible constructor taking single string parameter. </li>
 </ul>
-        <p>PropertiesApache Composer can be part of a tree of containers. It makes sense, of course, being more near the root of that tree.</p>
+        <p>PropertiesContainer can be part of a tree of containers. It makes sense, of course, being more near the root of that tree.</p>
 </body>
 
 

Modified: incubator/composer/trunk/composer-site/src/site/content/properties.html
URL: http://svn.apache.org/viewvc/incubator/composer/trunk/composer-site/src/site/content/properties.html?rev=618243&r1=618242&r2=618243&view=diff
==============================================================================
--- incubator/composer/trunk/composer-site/src/site/content/properties.html (original)
+++ incubator/composer/trunk/composer-site/src/site/content/properties.html Mon Feb  4 03:43:57 2008
@@ -5,15 +5,15 @@
     <title>Component Properties</title>
 </head>
 <body>
-<p>DefaultApache Composer allows for some properties to be set
+<p>DefaultContainer allows for some properties to be set
    per component at the time each is added. A convenience class called Characteristics lists the supplied properties. </p>
 
 <p>Properties can be set for a component in a method 'as' on
-   MutableApache Composer. If that is the case then the properties will
+   MutableContainer. If that is the case then the properties will
    affect the <strong>next</strong> component added only.</p>
 
 <p>They can also be set in a more persistent manner for the
-   MutableApache Composer in question, using the 'change' method. If so, they will affect all subsequent
+   MutableContainer in question, using the 'change' method. If so, they will affect all subsequent
    additions of component.</p>
 
 <p>Some examples :</p>
@@ -54,14 +54,14 @@
 
 <p>Every characteristics set for a component must be handled by a
    BehaviorFactory or InjectionFactory that recognises it. They are
-   typically chained together. DefaultApache Composer's default
+   typically chained together. DefaultContainer's default
    BehaviorFactory and InjectionFactory are AdaptiveBehaviorFactory and
    AdaptiveInjectionFactory. These can handle CDI and SDI as well as CACHE
    and HIDE_IMPL.</p>
 
-<p>If you setup DefaultApache Composer with a
+<p>If you setup DefaultContainer with a
    BehaviorFactory/InjectionFactory combination that is unaware of the
-   characteristics you subsequently use, Apache Composer will object by way of an
+   characteristics you subsequently use, Container will object by way of an
    exception as you add the component to the container. See <a href="unprocessed-properties-help.html">Unprocessed Properties</a>. </p>
 <p>Supplied properties (from org.apache.composer.core.Characteristics) -</p>
 <ul>
@@ -81,6 +81,6 @@
   <li>USE_NAMES - use the parameter names of the component's constructor (or injection method) for the binding of configuration or components.</li>
 </ul>
 <h3>Custom Properties</h3>
-<p>You can make your own properties quite easily - check out the source to <a href="http://svn.codehaus.org/containercontainer/java/2.x/trunk/container/container/src/java/org/containercontainer/Characteristics.java">Characteristics.java</a> and the classes that refer to it in Apache Composer (various implementations of ComponentFactory and ComponentAdapter). </p>
+<p>You can make your own properties quite easily - check out the source to <a href="http://svn.codehaus.org/containercontainer/java/2.x/trunk/container/container/src/java/org/containercontainer/Characteristics.java">Characteristics.java</a> and the classes that refer to it in Container (various implementations of ComponentFactory and ComponentAdapter). </p>
 </body>
 </html>

Modified: incubator/composer/trunk/composer-site/src/site/content/scopes.html
URL: http://svn.apache.org/viewvc/incubator/composer/trunk/composer-site/src/site/content/scopes.html?rev=618243&r1=618242&r2=618243&view=diff
==============================================================================
--- incubator/composer/trunk/composer-site/src/site/content/scopes.html (original)
+++ incubator/composer/trunk/composer-site/src/site/content/scopes.html Mon Feb  4 03:43:57 2008
@@ -5,8 +5,8 @@
 <title>Scoped Containers</title>
 </head>
 <body>
-<p>Apache Composer's scope hinges on parent/child container
-relationships. From a Apache Composer instance you can make a child
+<p>Container's scope hinges on parent/child container
+relationships. From a Container instance you can make a child
 container via makeChildContainer() or addChildContainer(..).</p>
 <p>These hierarchies of container can be set up with parents and
 children refering to each other, or children referring to parents only,
@@ -15,7 +15,7 @@
 lean on it for component resolution (but not without). If a parent has
 its child registered asa child, then it can manage it (start, stop,
 dispose cascade into children).</p>
-<p>Web frameworks that leverage Apache Composer typically construct a tree of containers.  For example an application level container maintains components that can be shared across the application. The application container will have child containers to maintain session level components.  These session level containers can resolve dependencies through their parent containers, but the application container will have no visibility into its children.  Additionally these child container do not have visibility into their sibling containers.  With this design, containers can easily be garbage collected at the end of their scope. </p>
+<p>Web frameworks that leverage Container typically construct a tree of containers.  For example an application level container maintains components that can be shared across the application. The application container will have child containers to maintain session level components.  These session level containers can resolve dependencies through their parent containers, but the application container will have no visibility into its children.  Additionally these child container do not have visibility into their sibling containers.  With this design, containers can easily be garbage collected at the end of their scope. </p>
 <h2>Simple Examples</h2>
 <p>Here are examples of parent/child setup:</p>
     <div class="source">
@@ -48,7 +48,7 @@
   <pre>
 parent = new DefaultContainer();
 parent.addComponent(Apple.class).addComponent(Orange.class).addComponent(Pear.class);
-child = parent.addChildContainer(new DefaultApache Composer(parent));
+child = parent.addChildContainer(new DefaultContainer(parent));
 child.addComponent(DependsOnApple.class);
 // this is OK
 parent.start();
@@ -57,7 +57,7 @@
 </div>
 <div class="source"><pre>parent = new DefaultContainer();
 parent.addComponent(Apple.class).addComponent(Orange.class).addComponent(Pear.class);
-child = new DefaultApache Composer(parent);
+child = new DefaultContainer(parent);
 child.addComponent(DependsOnApple.class);
 // this is  OK
 parent.start();

Modified: incubator/composer/trunk/composer-site/src/site/content/setter-injection.html
URL: http://svn.apache.org/viewvc/incubator/composer/trunk/composer-site/src/site/content/setter-injection.html?rev=618243&r1=618242&r2=618243&view=diff
==============================================================================
--- incubator/composer/trunk/composer-site/src/site/content/setter-injection.html (original)
+++ incubator/composer/trunk/composer-site/src/site/content/setter-injection.html Mon Feb  4 03:43:57 2008
@@ -59,7 +59,7 @@
 </div>
 <h2>Container support</h2>
 
-<p>The Spring Framework project is the best example of a container that favors setter injection. Apache Composer does
+<p>The Spring Framework project is the best example of a container that favors setter injection. Container does
    too, but we really believe that constructor injector is superior.</p>
 
 <h2>Refs + Comparison</h2>
@@ -67,11 +67,11 @@
 <p><a href="http://www.martinfowler.com/articles/injection.html#SetterInjectionWithSpring">Setter Injection</a> is a
     <a href="injection.html" title="Dependency Injection">Dependency Injection</a> variant where an object gets all
                                                                                    dependencies via setter methods.
-                                                                                   Apache Composer support this with
+                                                                                   Container support this with
     <a href="http://www.containercontainer.org/containercontainer/latest/containercontainer/apidocs/org/containercontainer/defaults/SetterInjectionComponentAdapter.html">SetterInjectionComponentAdapter</a>,
                                                                                                                                                                                          but
                                                                                                                                                                                          the
-                                                                                                                                                                                         Apache Composer
+                                                                                                                                                                                         Container
                                                                                                                                                                                          team
                                                                                                                                                                                          recommends
     <a href="constructor-injection.html" title="Constructor Injection">Constructor Injection</a>.</p>

Modified: incubator/composer/trunk/composer-site/src/site/content/sitemap.xml
URL: http://svn.apache.org/viewvc/incubator/composer/trunk/composer-site/src/site/content/sitemap.xml?rev=618243&r1=618242&r2=618243&view=diff
==============================================================================
--- incubator/composer/trunk/composer-site/src/site/content/sitemap.xml (original)
+++ incubator/composer/trunk/composer-site/src/site/content/sitemap.xml Mon Feb  4 03:43:57 2008
@@ -37,11 +37,11 @@
     </section>
     <section>
         <name>Containers</name>
-        <page>DefaultContainer.html</page>
-	    <page>CommandLineArgumentsContainer.html</page>
-		<page>PropertiesContainer.html</page>
-		<page>SystemPropertiesContainer.html</page>
-		<page>TransientContainer.html</page>
+        <page>default-container.html</page>
+	    <page>command-line-arguments-container.html</page>
+		<page>properties-container.html</page>
+		<page>system-properties-container.html</page>
+		<page>transient-container.html</page>
     </section>
     <section>
          <name>Applications</name>

Copied: incubator/composer/trunk/composer-site/src/site/content/system-properties-container.html (from r618234, incubator/composer/trunk/composer-site/src/site/content/SystemPropertiesContainer.html)
URL: http://svn.apache.org/viewvc/incubator/composer/trunk/composer-site/src/site/content/system-properties-container.html?p2=incubator/composer/trunk/composer-site/src/site/content/system-properties-container.html&p1=incubator/composer/trunk/composer-site/src/site/content/SystemPropertiesContainer.html&r1=618234&r2=618243&rev=618243&view=diff
==============================================================================
--- incubator/composer/trunk/composer-site/src/site/content/SystemPropertiesContainer.html (original)
+++ incubator/composer/trunk/composer-site/src/site/content/system-properties-container.html Mon Feb  4 03:43:57 2008
@@ -2,12 +2,12 @@
 
 <html>
 <head>
-<title>SystemPropertiesApache Composer</title>
+<title>SystemPropertiesContainer</title>
 </head>
 <body>
 <p>
-SystemPropertiesApache Composer is a special type of Apache Composer that is populated from the <a href="http://www.mindspring.com/~mgrand/java-system-properties.htm">System Properties</a> passed into the Java application when it started. 
-<p>Here is an example of how to use SystemPropertiesApache Composer to map system properties  as configuration for a component, with parameter names as the bindings.
+SystemPropertiesContainer is a special type of Container that is populated from the <a href="http://www.mindspring.com/~mgrand/java-system-properties.htm">System Properties</a> passed into the Java application when it started. 
+<p>Here is an example of how to use SystemPropertiesContainer to map system properties  as configuration for a component, with parameter names as the bindings.
 <p>Consider this component:
 
 <div class="source">
@@ -30,9 +30,9 @@
 <p>For automatic binding of system properties to parameter names of the component:</p>
 <div class="source">
   <pre>
-Apache Composer syspropsContainer = new SystemPropertiesApache Composer();
+Container syspropsContainer = new SystemPropertiesContainer();
                 
-MutableApache Composer mpc = new DefaultApache Composer(syspropsContainer);
+MutableContainer mpc = new DefaultContainer(syspropsContainer);
                 
 mpc.as(Characteristics.USE_NAMES).addComponent(BigFatComponent.class);
 </pre>
@@ -56,7 +56,7 @@
   <li> java.sql.(Date|Time|Timestamp) </li>
   <li> Any type sporting accessible constructor taking single string parameter. </li>
 </ul>
-<p>SystemPropertiesApache Composer can be part of a tree of containers. It makes sense, of course, being more near the root of that tree.</p>
+<p>SystemPropertiesContainer can be part of a tree of containers. It makes sense, of course, being more near the root of that tree.</p>
 </body>
 
 

Modified: incubator/composer/trunk/composer-site/src/site/content/team.html
URL: http://svn.apache.org/viewvc/incubator/composer/trunk/composer-site/src/site/content/team.html?rev=618243&r1=618242&r2=618243&view=diff
==============================================================================
--- incubator/composer/trunk/composer-site/src/site/content/team.html (original)
+++ incubator/composer/trunk/composer-site/src/site/content/team.html Mon Feb  4 03:43:57 2008
@@ -5,11 +5,11 @@
 <title>Team</title>
 </head>
 <body>
-<p>A project like Apache Composer is always made possible by the effort of a lot of people. Read about the developers and the contributers' names below. All of them have worked together to make Apache Composer the most respected IoC framework.</p>
+<p>A project like Container is always made possible by the effort of a lot of people. Read about the developers and the contributers' names below. All of them have worked together to make Container the most respected IoC framework.</p>
 <h2>Committers</h2>
-Apache Composer committers introduce themselves in their own words and are listed in alphabetical order.<br />
+Container committers introduce themselves in their own words and are listed in alphabetical order.<br />
 <h3>Paul Hammant</h3>
-<p>Paul is 39, has worked for ThoughtWorks  since 2002 and is co-founder of the PicoContainer project (precursor to Apache Composer). He used to freelance but is now very happy at TW. Paul practices XP on client sites and loves open source on which he is chief zealot for TW. He formerly worked at Apache on the Avalon project and remains there working on AltRMI. He loves the simplest thing as a design metaphor, hates too much XML. He loves the lowest common denominator (LCD) as a mechanism for facilitating divergent designs. To that end, he encourages multiple implementations of LCD ideas and APIs. Paul hopes to see Milli, Kilo and Mega implementations of the Pico idea. He hopes to see a myriad of interchangeable Apache Composer Components. He hopes to see standard APIs for components emerge from those implementations, but never be forced when teams cannot agree. It would be fairly easy to guess that Paul does not like big up-front design. That not withstanding the fact that 
 he used to do bucket-loads of it Paul with Aslak, wrote the first lines. Paired, under the influence of a couple of beers, and based on Joe's story of Rachel Davies' comments to his setter injector IoC work at the start of June 2003.</p>
+<p>Paul is 39, has worked for ThoughtWorks  since 2002 and is co-founder of the PicoContainer project (precursor to Container). He used to freelance but is now very happy at TW. Paul practices XP on client sites and loves open source on which he is chief zealot for TW. He formerly worked at Apache on the Avalon project and remains there working on AltRMI. He loves the simplest thing as a design metaphor, hates too much XML. He loves the lowest common denominator (LCD) as a mechanism for facilitating divergent designs. To that end, he encourages multiple implementations of LCD ideas and APIs. Paul hopes to see Milli, Kilo and Mega implementations of the Pico idea. He hopes to see a myriad of interchangeable Container Components. He hopes to see standard APIs for components emerge from those implementations, but never be forced when teams cannot agree. It would be fairly easy to guess that Paul does not like big up-front design. That not withstanding the fact that he used to d
 o bucket-loads of it Paul with Aslak, wrote the first lines. Paired, under the influence of a couple of beers, and based on Joe's story of Rachel Davies' comments to his setter injector IoC work at the start of June 2003.</p>
 <p>Paul is also well known for <a href="http://sourceforge.net/projects/eob">Enterprise Object Broker</a> and <a href="http://jesktopapps.sf.net/">Jesktop</a>, the <a href="http://openqa.org/selenium-rc/">original driven side of Selenium</a> and other stupid ideas like <a href="http://sourceforge.net/projects/thicky">Thicky</a> and related <a href="http://paulhammant.com/blog/ruby-versus-javascript-for-web3.0.html">early Web 3.0 references</a></p>
 <h3><p>Konstantin Pribluda</p></h3>
 <p>I'm 32 and live in Wiesbaden. I started programming at the age of 12 and had access to really cool systems ranging from WANG 3200 through PDP 8/11 to System-360 ( actually sovjet clones of them, but who cares? ). My first &quot;paid for&quot; work was in 1988, and from that point I financed my study freelance software development. I developed fiscal management systems, medical video archiving, internet applications for telcos and java applet games ( later was for personal fun )...</p>
@@ -21,13 +21,13 @@
 <p>My interests besides programming are my wife (who always gets too less time), reading books (a lot of fantasy and SF stuff), hearing celtic-rooted music (although I like others also lot), and - when in mood - cooking</p>
 <p>Last, but not least, beeing a Christian is a part of my life, where I have my roots.</p>
 <h4>Mauro Talevi</h4>
-<p>I first came across Paul at an XTC (eXtreme Tuesdays Club) on Agile development at the Ol' Bank of England Pub in London. Back then Apache Composer had yet to be born. We were both working with Avalon IoC and in particular the Phoenix microkernel. Ever since discussing all the limitations of the Avalon framework - in particular the dependency on an API - I knew that the way forward was the Pico way.</p>
+<p>I first came across Paul at an XTC (eXtreme Tuesdays Club) on Agile development at the Ol' Bank of England Pub in London. Back then Container had yet to be born. We were both working with Avalon IoC and in particular the Phoenix microkernel. Ever since discussing all the limitations of the Avalon framework - in particular the dependency on an API - I knew that the way forward was the Pico way.</p>
 <p>I've worked in Java and enterprise systems for several years in various business domains - ranging from space data search portal for ESA to real-time messaging at the BBC - and I've come to appreciate the beauty, elegance and power of CDI.</p>
 <h3>Michael Ward</h3>
-<p>I live in Chicago, or at least that is where all my bills are sent. As it seems to be the lingo, I was assimilated into ThoughtWorks back in 2003. I have been developing professionally since 1997 and have had the great opportunity to work and live in many great locations with some exceptionally talented individuals. I was immediately drawn to Apache Composer because of its simplicity. The API is small and does not force you to define all your configurations in XML. The projects I have worked on are easier to test, refactor, debug and extend because a natural side effect of utilizing CDI is a small and easy to comprehend code base. Mike leads the <a href="http://waffle.codehaus.org/">Waffle web framework</a> project (the easiest for Java we think). </p>
-<p>Have worked/contributed to MicroContainer, the JMX module for NanoContainer, Apache Composer.NET and NanoContainer.NET.</p>
+<p>I live in Chicago, or at least that is where all my bills are sent. As it seems to be the lingo, I was assimilated into ThoughtWorks back in 2003. I have been developing professionally since 1997 and have had the great opportunity to work and live in many great locations with some exceptionally talented individuals. I was immediately drawn to Container because of its simplicity. The API is small and does not force you to define all your configurations in XML. The projects I have worked on are easier to test, refactor, debug and extend because a natural side effect of utilizing CDI is a small and easy to comprehend code base. Mike leads the <a href="http://waffle.codehaus.org/">Waffle web framework</a> project (the easiest for Java we think). </p>
+<p>Have worked/contributed to MicroContainer, the JMX module for NanoContainer, Container.NET and NanoContainer.NET.</p>
 <h3>Michael Rimov</h3>
-<p>Michael came to the Java world after programming for about eight years in the Windows API.  He dove head first into Java J2EE frameworks by initially working with the popular heavyweight Expresso framework where he introduced unit testing to those developers. During his stint as Lead Developer, the framework's usage numbers exploded.  After about nine years working with J2EE, Michael found the joys of light weight components and Apache Composer and has been reaping the performance benefits of both ever since.  His goal is to see it NanoContainer/NanoWAR grow in the J2EE arena, while keeping Pico perfect for embedding in all applications.</p>
+<p>Michael came to the Java world after programming for about eight years in the Windows API.  He dove head first into Java J2EE frameworks by initially working with the popular heavyweight Expresso framework where he introduced unit testing to those developers. During his stint as Lead Developer, the framework's usage numbers exploded.  After about nine years working with J2EE, Michael found the joys of light weight components and Container and has been reaping the performance benefits of both ever since.  His goal is to see it NanoContainer/NanoWAR grow in the J2EE arena, while keeping Pico perfect for embedding in all applications.</p>
 <p>Michael works for Centerline Computers, Inc in Corvallis Oregon.</p>
 <h3>Jose Peleteiro</h3>
 <p>I live in Rio de Janeiro, Brazil.</p>
@@ -37,7 +37,7 @@
 <p>Emeritus committers are those committers who have contributed significantly to the development of the project, but have been inactive for a period amount of time.</p>
 <p> * Thomas Heller</p>
 <h4>Aslak Helles&oslash;y</h4>
-<p>Aslak is very accomplished in the Open Source space and co-founder of Apache Composer. He leads XDoclet, and has taken over QDox from Joe. He wrote most of the impressive MiddleGen, and has refactored Generama out of both. From an observers point of view Aslak is prolific. Aslak was assimilated into ThoughtWorks in 2003. [ Words by Paul ]</p>
+<p>Aslak is very accomplished in the Open Source space and co-founder of Container. He leads XDoclet, and has taken over QDox from Joe. He wrote most of the impressive MiddleGen, and has refactored Generama out of both. From an observers point of view Aslak is prolific. Aslak was assimilated into ThoughtWorks in 2003. [ Words by Paul ]</p>
 <p> * Mike Hogan</p>
 <p> * Stephen L. Molitor</p>
 <h4>Dan North</h4>
@@ -55,7 +55,7 @@
 <p>&nbsp;</p>
 <p>&nbsp;</p>
 <p>Contributers</p>
-<p>A lot of people have contributed ideas and code to the Apache Composer's code base. See the names in the list below in alphabetical order.</p>
+<p>A lot of people have contributed ideas and code to the Container's code base. See the names in the list below in alphabetical order.</p>
 <p> * Nicolas Averseng<br />
   * Mathias Bogaert<br />
   * Rao Chejarla<br />

Modified: incubator/composer/trunk/composer-site/src/site/content/terminology.html
URL: http://svn.apache.org/viewvc/incubator/composer/trunk/composer-site/src/site/content/terminology.html?rev=618243&r1=618242&r2=618243&view=diff
==============================================================================
--- incubator/composer/trunk/composer-site/src/site/content/terminology.html (original)
+++ incubator/composer/trunk/composer-site/src/site/content/terminology.html Mon Feb  4 03:43:57 2008
@@ -18,7 +18,7 @@
     <li>A Setter Dependency Injection (SDI) component is a JavaBean, and a JavaBean is an SDI component</li>
     <li>A Contructor Dependency Injection (CDI) Component is not a JavaBean, but is a POJO</li>
     <li>A JavaBean can be any of the three types of IoC and domain-specific all at the same time</li>
-    <li>Spring, Apache Composer, XWork and other frameworks all support both Components and Data Objects to some
+    <li>Spring, Container, XWork and other frameworks all support both Components and Data Objects to some
         extend. Avalon tries real hard to not support Data Objects, but that is nearly impossible.
     </li>
 </ul>
@@ -123,11 +123,11 @@
    specification like &quot;initialization completion&quot; support), any object with a public default
    constructor that does not require any method calls to set up its state.</p>
 
-<h3>Apache Composer-supported
+<h3>Container-supported
                                                                                                                Object
 </h3>
 
-<p>An object that can be 'natively' used in Apache Composer. Any Type-3 component.</p>
+<p>An object that can be 'natively' used in Container. Any Type-3 component.</p>
 
 <h3>XWork-supported
                                                                                                Object</h3>

Copied: incubator/composer/trunk/composer-site/src/site/content/transient-container.html (from r618229, incubator/composer/trunk/composer-site/src/site/content/TransientContainer.html)
URL: http://svn.apache.org/viewvc/incubator/composer/trunk/composer-site/src/site/content/transient-container.html?p2=incubator/composer/trunk/composer-site/src/site/content/transient-container.html&p1=incubator/composer/trunk/composer-site/src/site/content/TransientContainer.html&r1=618229&r2=618243&rev=618243&view=diff
==============================================================================
--- incubator/composer/trunk/composer-site/src/site/content/TransientContainer.html (original)
+++ incubator/composer/trunk/composer-site/src/site/content/transient-container.html Mon Feb  4 03:43:57 2008
@@ -2,15 +2,15 @@
 
 <html>
 <head>
-<title>TransientApache Composer</title>
+<title>TransientContainer</title>
 </head>
 <body>
 <p>
-TransientApache Composer is a for short term needs for object instantion, where the container is going to be de-referenced shortly after use.
+TransientContainer is a for short term needs for object instantion, where the container is going to be de-referenced shortly after use.
 <p>Here is an example of use:
 <div class="source">
 <pre>public Foo makeSuitableFoo() {
-    MutableApache Composer temp = new TransientApache Composer(someParentContainer);
+    MutableContainer temp = new TransientContainer(someParentContainer);
     temp.addComponent(somethingElseThatMightBeNeeded);  // by instance
     temp.addComponent(Foo.class, FooImpleThatNeedsTheAbove.class); // by type
     return temo.getComponent(Foo.class);

Modified: incubator/composer/trunk/composer-site/src/site/content/transparency.html
URL: http://svn.apache.org/viewvc/incubator/composer/trunk/composer-site/src/site/content/transparency.html?rev=618243&r1=618242&r2=618243&view=diff
==============================================================================
--- incubator/composer/trunk/composer-site/src/site/content/transparency.html (original)
+++ incubator/composer/trunk/composer-site/src/site/content/transparency.html Mon Feb  4 03:43:57 2008
@@ -5,15 +5,15 @@
 <title>Transparency</title>
 </head>
 <body>
-<p>Transparency, for Apache Composer, means that components do not have to implement any interface or abstraction in order to be components. Moreover, components do not have to adhere to any naming conventions or bundle any meta-data in order to qualify as components.  </p>
-<p>Constructor Injection is what we recommend, so the minimum definition of a component is a simple class that takes its dependencies in its constructor. For Setter Injection, it is a class with dependencies delivered via simple setters. Your components may be interface / impl separated, but we are not forcing that for interop with Apache Composer.</p>
-<p>If you live with this ideal, you may be able to use the components you design for Apache Composer with other frameworks or containers. I.e. you are not locked in. We suggest you choose other technologies that are similarly light on API and framework, and could be characterised as transparent. Good examples are XStream, Sitemesh and anything that deals with POJOs.</p>
+<p>Transparency, for Container, means that components do not have to implement any interface or abstraction in order to be components. Moreover, components do not have to adhere to any naming conventions or bundle any meta-data in order to qualify as components.  </p>
+<p>Constructor Injection is what we recommend, so the minimum definition of a component is a simple class that takes its dependencies in its constructor. For Setter Injection, it is a class with dependencies delivered via simple setters. Your components may be interface / impl separated, but we are not forcing that for interop with Container.</p>
+<p>If you live with this ideal, you may be able to use the components you design for Container with other frameworks or containers. I.e. you are not locked in. We suggest you choose other technologies that are similarly light on API and framework, and could be characterised as transparent. Good examples are XStream, Sitemesh and anything that deals with POJOs.</p>
 <p>There are some exceptions, to this goal of ours.</p>
 <h2>Lifecycle</h2>
 <p>Java does not have a Startable interface, nor does it have a Disposable (.Net has IDisposable), so we made our own. You can use ours or your own in a similar design. If you use your own, you may want to extend StartableLifecycleStrategy and override a couple of methods. That's if you need lifecycle at all.</p>
 <p>If a Startable inerface goes into J2SE, then it will probably be supported.</p>
 <h2>Annotations</h2>
-<p>We also support @Inject as an annotation for methods and fields. This is a variation of Setter Injection. The annotations are part of our codebase. Again, you can use your own, or others if you override one of the two classes from Apache Composer's codebase <strong>AnnotatedFieldInjection</strong> and <strong>AnnotatedMethodInjection</strong>.</p>
+<p>We also support @Inject as an annotation for methods and fields. This is a variation of Setter Injection. The annotations are part of our codebase. Again, you can use your own, or others if you override one of the two classes from Container's codebase <strong>AnnotatedFieldInjection</strong> and <strong>AnnotatedMethodInjection</strong>.</p>
 <p>Annotations are a break with transparency, so we don't recomend them - stick to vanilla Constructor Injection if you can.</p>
 <p>If a simple @Inject annotation goes into J2SE, then it will probably be supported. </p>
 <p></p>

Modified: incubator/composer/trunk/composer-site/src/site/content/web-frameworks.html
URL: http://svn.apache.org/viewvc/incubator/composer/trunk/composer-site/src/site/content/web-frameworks.html?rev=618243&r1=618242&r2=618243&view=diff
==============================================================================
--- incubator/composer/trunk/composer-site/src/site/content/web-frameworks.html (original)
+++ incubator/composer/trunk/composer-site/src/site/content/web-frameworks.html Mon Feb  4 03:43:57 2008
@@ -9,14 +9,14 @@
 <p>There are only about a million Java web-frameworks for Java. There
 more recent and sophisticated ones try to do Dependency Injection for
 'actions' or 'controllers'. </p>
-<p>If you want to use Apache Composer for a web framework, then you're
+<p>If you want to use Container for a web framework, then you're
 likely to end up with three container levels. The root container would
 be common to all and known as the <strong>application scoped</strong> container. Next is a <strong>session-scoped</strong> one, with the app one marked as its parent. Lastly a <strong>request scoped</strong>
 one, with the session one marked as its parent. There are two
 not-so-subtle varations on how they would be used. One, we poineered
-with Apache Composer 1.x in 2003, the other inroduced with Apache Composer
+with Container 1.x in 2003, the other inroduced with Container
 2.x in 2007.</p>
-<h3>Apache Composer and web frameworks - the old way.</h3>
+<h3>Container and web frameworks - the old way.</h3>
 <p>You make one instance of the app container. For each new HTTP
 Session you make a new session level container, and put it into the
 session itself - refer HttpSession.setAttribute(key,val). For each
@@ -28,7 +28,7 @@
 instantiated. 2) the serialization of the session (by Tomcat etc) might
 cause more things to be serialized than you intend - i.e. the session
 container refers to the application container.</p>
-<h3>Apache Composer and web frameworks - the new way.</h3>
+<h3>Container and web frameworks - the new way.</h3>
 <p>You make one instance of the app, session and request container on
 servlet load. For the Application one, you choose Caching as the
 behavior factory. For the session and request level ones, you choose
@@ -37,21 +37,21 @@
 <div class="source">
   <pre>public class MyTinyApacheComposerServlet extends HttpServlet {
 
-    private DefaultApache Composer requestContainer;
+    private DefaultContainer requestContainer;
 
     private HttpSessionStoring sessionStoring;
     private HttpSessionStoring requestStoring;
 
     public void init(ServletConfig cfg) throws ServletException {
 
-        Apache Composer appContainer = new DefaultApache Composer(new Caching()); // app scoped components are cached for all users/sessions
+        Container appContainer = new DefaultContainer(new Caching()); // app scoped components are cached for all users/sessions
 
         Storing storingBehavior1 = new Storing();
-        Apache Composer sessionContainer = new DefaultApache Composer(storingBehavior1, appContainer);
+        Container sessionContainer = new DefaultContainer(storingBehavior1, appContainer);
         sessionStoringAdapter = new HttpSessionStoringAdapter(storingBehavior1, "sessionStore");
 
         Storing storingBehavior2 = new Storing();
-        requestContainer = new DefaultApache Composer(storingBehavior2, sessionContainer);
+        requestContainer = new DefaultContainer(storingBehavior2, sessionContainer);
         requestStoringAdapter = new HttpSessionStoringAdapter(storingBehavior2, "requestStore");
 
         // populate app, session and request scoped containers.

Modified: incubator/composer/trunk/composer-site/src/site/templates/skin.html
URL: http://svn.apache.org/viewvc/incubator/composer/trunk/composer-site/src/site/templates/skin.html?rev=618243&r1=618242&r2=618243&view=diff
==============================================================================
--- incubator/composer/trunk/composer-site/src/site/templates/skin.html (original)
+++ incubator/composer/trunk/composer-site/src/site/templates/skin.html Mon Feb  4 03:43:57 2008
@@ -36,7 +36,7 @@
 </div>
 </div>
 <div id="breadcrumbs">
-<div class="left">Last Published: Jan 19 2008 (Apache Composer 2.0 released)</div>
+<div class="left">Last Published: </div>
 <div class="clear">
 
 </div>
@@ -76,7 +76,7 @@
 <div class="clear">
 </div>
 <div id="footer">
-<div class="right">&#169; 2003-2007 Apache Composer Committers</div>
+<div class="right">&#169; 2008 Apache Software Foundation</div>
 <div class="clear">
 </div>
 </div>



Mime
View raw message