Leo Sutic wrote:
> 1) The following interfaces are put in framework.service:
>
> public interface ServiceManager {
> public Object lookup (String role) throws ServiceException;
> public void release (Object service);
> public boolean hasService (String role);
> }
>
> public interface Serviceable {
> public void service (ServiceManager manager) throws ServiceException;
> }
>
> The contracts are the same as for ComponentManager and Composable,
> respectively, and the interfaces are basically those, but with
> Component -> Object.
Back on the 10 Feb, I made a similar though more detailed proposal
which for all intensive purposes is what Leo is describing above.
http://www.mail-archive.com/avalon-dev@jakarta.apache.org/msg05885.html
The 10 Feb proposal (and the related src/proposal/service CVS 1.1 version
of the same date also includes a DefaultServiceManager and the updates
to the Phoenix lifecycle helper implementation to include direct support
for Serviceable and related interfaces. I agree with Leo that it would
be really helpful to have this included within the framework now, enabling
a more complete assessment of the service management questions as part of
the Avalon 5.0 actions. So as not to leave any doubt, this is basically
the complete "Component" package with (a) the replacement of Component with
Object, (b) updates to the javadoc as required (c) package name of
org.apache.avalon.framework.service, (d) and the supporting Phoenix
lifecycle helper additions.
Any objections to a vote on this?
Cheers, Steve.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
