The bottom line is the developer has options with IoC 3.14.  You can take the 
conventional route or throw it into a constructor which as Niclas shows can use 
methods to be lean rather being 200 lines long.  If the developer does that then 
essentially the two forms are easily interchangable.  I like this idea alot. 

I have been getting alot of good feed back from the community at large regarding 
PicoContainer.  Some of the ideas do on occasion appeal to me.  The notion of just 
haveing plain old java objects as services is awesome.  

I would like to see this functionality in Merlin so developers who want to do so can 
use one platform for all their IoC preferrences.

I like the idea which falls in line with Berins email.  We need to do this to provide 
for all user needs on a single service management platform.  Make everyone happy and 
the whole communty unifies behind it.

Alex

> 
> From: Niclas Hedhman <[EMAIL PROTECTED]>
> Date: 2003/11/18 Tue AM 09:59:41 EST
> To: "Avalon Developers List" <[EMAIL PROTECTED]>
> Subject: Re: [proposal] IoC type 3.14 extension to the Avalon Framework
> 
> On Tuesday 18 November 2003 22:43, Ulrich Mayring wrote:
> > And that is a problem. If you had a real example of a working
> > application, you'd find that there's a lot of code in the lifecycle
> > methods (at least that is the case with our apps). In the type3 example
> > all that stuff would have to be in the constructor.
> 
> Not having an opinion about his proposal at large (yet), your counter argument 
> is a bit bleak. Ever heard of methods ;o) ?
> 
> public class Abc
> {
>     public Abc( Configuration conf, ServiceManager man )
>         throws Exception
>     {
>         configure( conf );
>         service( man );
>     }
> }
> 
> Would that be so much different from what you are doing now?
> AND, you don't have to use what he is suggesting, right?? If you like the 
> strict cycle (like I do, still), stick with it... But if we get access to 
> more components, i.e. components written in more neutral ways, I am +1 for 
> that.
> 
> Niclas
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to