On Wed, 18 Dec 2002 14:18, Berin Loritsch wrote:
> interface ServiceManager
> {
> Object lookup( String urn ) throws NoSuchValueException;
> void bind( String urn, Object value )
> throws AlreadyBoundException;
> }
>
> Any thoughts or inputs?
JNDI does it better and is a standard so if you want that sort of interface
then JNDI should be the way to go. In which case JNDIKit is already
implemented so may aswell use that ;) If you were to go this way then you may
aswell just have one lifecycle interface
interface Component
{
void init( Context c ) throws Exception;
void destroy();
}
And standardize on naming of entries in context. However as J2EE patterns
document already defines a namespace then that should be used as
recomendation.
If that route is taken - is it really Avalon anymore?
Things you put in "Active Use" are only relevent to request based
architectures where the container demarcs the request boundardaries. Where
this is not true then you have just unecessarily limited the types of
containers.
--
Cheers,
Peter Donald
"Man's mind stretched to a new idea never goes back to its original
dimensions." -Oliver Wendell Holmes
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
