CVS: plexus-container-new/src/java/org/apache/plexus/util SelectorUtils.java,1.1,1.2

Update of /cvsroot/plexus/plexus-container-new/src/java/org/apache/plexus/util
In directory eng.werken.com:/tmp/cvs-serv16424/src/java/org/apache/plexus/util

Modified Files:
	SelectorUtils.java 
Log Message:
o The handling of the lifecycle is now the responsibility of the instance
  manager and not the component repository. The hierarchy may change a little on
  the inside but won't affect usage. When there was only one type of component
  instance this could be dealt with easily from the Component Repository but
  obviously when you get into dealing with different types of instantiation
  strategies the lifecycle must be handled in the entity where the strategy
  resides. I'm sure I'm just discovering what every other container writer
  has discovered along the way.
  
  I found this working on a webapp and I was playing with RunData using a
  poolabel and per-lookup instance manager and after the first lookup the
  component wasn't being run through the lifecycle. So that's been fixed.
  Now the instance manager inside the component manager is responsible
  for this and this will cause a little bit of the internals to be
  shuffled as the component repository still has the method to start
  the lifecycle which it probably doesn't need.




Index: SelectorUtils.java
===================================================================
RCS file: /cvsroot/plexus/plexus-container-new/src/java/org/apache/plexus/util/SelectorUtils.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- SelectorUtils.java	12 Apr 2003 18:01:44 -0000	1.1
+++ SelectorUtils.java	12 May 2003 18:57:28 -0000	1.2
@@ -669,6 +669,4 @@
         }
         return result.toString();
     }
-
 }
-