-------- Original Message -------- Subject: Re: [C2] ComponentManager/Selector Rearchitecture Date: Thu, 22 Mar 2001 08:22:08 -0500 From: Berin Loritsch <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] References: <[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Peter Donald wrote: > > At 11:45 21/3/01 -0500, Berin Loritsch wrote: > >public interface RoleManager > >{ > > /** > > * Gets the Role for the shorthand name. > > */ > > String getRoleForName(String name); > > > > /** > > * Get default implementation class for role > > */ > > String getDefaultClassNameForRole(String role); > >} > > > >These aren't terse, but are eminently clear as to their > >function. In that sense, they are self documenting. > >The scope of the RoleManager is very narrow. It only exists > >as a helper to the ComponentManager. > > Much better - I didn't really understand what you were trying to do ;) > > Want me to copy this to org.apache.avalon.component.RoleManager ??? I may > leave you to write the javadoc at the top though as I am not sure I > completely understand it ;) Sure. But the interface is only part of the picture. What is the standard mechanism to get the RoleManager to the ComponentManager? This is the catch. Cocoon has a static class with static methods--clearly this won't work. What we need is a way of automatically instantiating the RoleManager with the values prepopulated. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
