(comments inline) --- Vjeran Marcinko <[EMAIL PROTECTED]> wrote: > Hi there. [snip] > Have you found a way to delete/configure these roles that are set by default > during fortress boot ? These are loaded before my roles definition in .xconf > file ... > Here is a snip - > > DEBUG 2003-02-10 09:54:28.281 [com.alte] (): Logger for category > com.alterbox.alterchat.system.roles not defined in configuration. New Logger > created and returned > DEBUG 2003-02-10 09:54:28.515 [com.alte] (): addRole role: name='cache', > role='org.apache.excalibur.cache.Cache', > class='org.apache.excalibur.cache.impl.DefaultCache', > handler='org.apache.excalibur.fortress.handler.ThreadSafeComponentHandler' > WARN 2003-02-10 09:54:28.515 [com.alte] (): Unable to load class > org.apache.excalibur.cache.impl.DefaultCache. Skipping. > DEBUG 2003-02-10 09:54:28.515 [com.alte] (): addRole role: > name='lru-cache', role='org.apache.excalibur.cache.Cache', > class='org.apache.excalibur.cache.impl.LRUCache', > handler='org.apache.excalibur.fortress.handler.ThreadSafeComponentHandler' > WARN 2003-02-10 09:54:28.546 [com.alte] (): Unable to load class > org.apache.excalibur.cache.impl.LRUCache. Skipping. >
These roles are set in: org.apache.avalon.fortress.impl.role.FortressRoleManager in the initialize() method. It is set by default in: org.apache.avalon.fortress.impl.AbstractContainer in the createDefaultRoleManager() method which is in turn called during AbstractContainer's service() method. You should be able to override this by defining your own RoleManager (with role org.apache.avalon.fortress.RoleManger.ROLE) in your *.roles and *.xconf file. The AbstractContainer should pick up your own RoleManager instead of the default. You will probably want to just extend org.apache.avalon.fortress.impl.role.AbstractRoleManager to do this. Otherwise, if you'd like to keep the default RoleManager but just get rid of the warnings, you can add the needed libraries to your classpath. Look at the FortressRoleManager for more details. If you do this, the RoleManager will set up several roles for you which you can then use in your own components/applications. > And have you tried to use jdk1.4 logger with fortress ? I would prefer to use > that one since I use 1.4 jdk all the time and it's logger likewise in my > other non-avalon apps, but it seems that everything is mostly made for LogKit > package. I cannot see some LogManager for jdk14 logger, and there is just > Jdk14Logger wrapper which is not that useful for some reasons ...:-( Or > maybe I'm missing something here ... > > Cheers, > Vjeran I'm not familiar with how to do this since I just use the default logger generally. I do believe there is a way to get LogKit to use jdk1.4 but I'm not certain. There were recently some very good emails sent out summarizing the "state of logging" in avalon. You might want to check the mail archives. jaaron __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
