> From: Marcus Crafter [mailto:[EMAIL PROTECTED]]
>
> When are the following Re* methods actually intended to
> be invoked
> on implementing Components:
>
> o Recontextualizable
> o Recomposable
> o Reconfigure/Reparameterizable
>
> I can imagine a change in the .roles/.xconf files causing
> components to be reconfigured and given a new component manager
> reference, but perhaps that's wrong (?).
Really, the only Re* interfaces that I think really should be used
are the Reconfigurable/Reparameterizable ones. Fortress (and I think
Merlin as well) can easily remap role/implementations at runtime so
there is no real need to pass in a new Component/ServiceManager.
Technically speaking, the same can be said of Recontextualizable.
However, practicality may mandate that configuration, parameterization,
and contextualization require official objects.
The Recomposable/Reserviceable interfaces probably should be altered to
something along these lines:
interface Recomposable
{
void remap();
}
Which would be a signal from the container that the role/implementations
have been changed--and the component can update its references
accordingly.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
