Re: [RT:A5] What are the _real_ concern areas?

On Thu, 19 Dec 2002 13:19, Adam Murdoch wrote:
> - A Logger is delivered by LogEnabled.enableLogging(), and is the first
> lifecycle method called.
> - A Context is delivered by Contextualizable.contextualize(), and is the
> second lifecycle method called.
> - A ServiceManager is delivered by Serviceable.service(), and is the third
> lifecycle method called.
> - Configuration is delivered by Configurable.configure(), and is the fourth
> lifecycle method called.
> - Parameters are delivered by Parameterizable.parameterize(), and is the
> fifth lifecycle method called.

Parameterizable occurs at same time as Configurable and is incompatible with 
Configurable.

> There are orders of magnitude more components than there are containers.
> Let's figure out how to make it as easy as possible to write a component.
> Once that's sorted, then we can start compromising framework for the sake
> of the container writers.  Let's not do this prematurely.

There is as many different styles of component writers

> Why is this a problem?  Why can't it be addressed in meta-info *if* it
> becomes an issue?  We're already looking at meta-info that describes what a
> component expects to be exposed via ServiceManager and Context.  Argueably
> the same will happen for config and params (if not in meta-info, then
> meta-data). 

already done.

> This is SoC.
...
> To put fragmentation of concerns more concretely:

SOC/FOC are one and the same. 

-- 
Cheers,

Peter Donald
--------------------------------
My opinions may have changed, 
but not the fact that I am right
--------------------------------