> As I was thinking through all of this, and recalling previous list
> discussions (Context vs. ServiceManager) I thought of something
interesting.
> When I first started working with Avalon, I was under the assumption that
> ServiceManger was itself a Container that controlled the lifecycle of
> referenced service...not so I think. If the ServiceManager only manages
> access to peer-based components with which a component is associated,
would
> it not "AssociationManager" be a more appropriate name? Its role is
clearly
> that of a "reference resolver" rather than "managing the service".
And to followup, there could be...
public interface Associable {
public void associate(AssociationManager manager)
throws AssociationException;
}
...as a replacement for the (somewhat misnomer) ServiceManager.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
