What would be heaven to me:
public class SomeServiceImpl implements SomeService, Configurable, Startable
{
public SomeServiceImpl( Logger logger, AnotherService dependency )
{
}
public void setOtherService( OtherService service )
{
// this is optional dependency
}
public void configure( Configuration )
{
}
...
}
So we have a mix now. And I don't want to compose component handlers to
achieve such a dream. If the container is very strict to avalon lifecycle
phases and Aspects/Concerns could implement all these others IoC "types"
(agghh!) then no need for component handlers. It will be only one, managed
by the container.
But hey, we have to face something: we need meta info. Its a very delicate
issue. I'm not sure I'm strong enough :-)
Anyway lets eat our own dog food and do something SoC. The meta should be
used by the container, but it doesn't need to know from where it came from
(xml, attributes, serialized form, whatever!!!)
What do you think?
-----Mensagem original-----
De: Leo Sutic [mailto:[EMAIL PROTECTED]
Enviada em: quinta-feira, 11 de mar�o de 2004 16:02
Para: 'Avalon Developers List'
Assunto: RE: More "academic" ideas [Was: [VOTE] New sandbox project]
> -----Original Message-----
> From: Hamilton Verissimo de Oliveira (Engenharia - SPO)
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
