Fortress currently kicks out a series of warning like the following when it
starts up:
WARN [fortress.system.roles ] (): Unable to load class
org.apache.avalon.excalibur.monitor.ActiveMonitor. Skipping.
WARN [fortress.system.roles ] (): Unable to load class
org.apache.avalon.excalibur.monitor.PassiveMonitor. Skipping.
WARN [fortress.system.roles ] (): Unable to load class
org.apache.excalibur.xml.xpath.XPathProcessorImpl. Skipping.
WARN [fortress.system.roles ] (): Unable to load class
org.apache.excalibur.xml.xpath.JaxenProcessorImpl. Skipping.
WARN [fortress.system.roles ] (): Unable to load class
org.apache.excalibur.xml.impl.JaxpParser. Skipping.
WARN [fortress.system.roles ] (): Unable to load class
org.apache.excalibur.xml.impl.XercesParser. Skipping.
These are not a problem as it is just informing us that some of the optional
jars are not present. The problem is that WARN level messages showing up
in the log causes my customers to call me.
I had added a patch a while ago which added a logger sub category, called
"default" to the "fortess.system.roles" category. See line 584 of
ContextManager. But the recent changes have caused these messages
to be output in the parent roles category.
Would it be possible to break them out into a different category so they
could be surpressed? Or would it be advisable to simply add the missing
jars to my application? As I am not using any of the above, it does not
seem like they should be required.
For now, I will have to set the log level of fortress.system.roles to ERROR
to work around this, but that will mean that any actual WARN messages
will not get logged.
Cheers,
Leif
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
