Peter Royal wrote:
On Thursday, February 13, 2003, at 06:54 AM, J Aaron Farr wrote:
However, why then does the FortressRoleManager create a role
definition for the
Cache? Fortress works without it. I can't find anywhere that it's used
internally, so why is it there, especially if it doesn't initialize
correctly?
Good question :) Thats one for Berin. It was added here:
http://cvs.apache.org/viewcvs.cgi/avalon-excalibur/fortress/src/java/
org/apache/excalibur/fortress/Attic/
ExcaliburRoleManager.java.diff?r1=1.2&r2=1.3&diff_format=h&hideattic=0,
but I have no idea why (the cvs commit msg is lacking).
It was added because the base RoleManager would set up all the known
Excalibur components if they were in the classpath. The configurable
RoleManager would only be used for user-defined components. It is
merely a convenience thing, and not that Cache is actually used anywhere
inside Fortress.
Perhaps even more generally, what is the purpose of any of the role
definitions
found in FortressRoleManager?
To declare common components that you might use in your container so
you don't have to put them in your roles file. Pure convenience.
-pete
Exactly.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
