[Opensource] Removing separate Schema Logging config files?

[Michael Rimov]

Hey All,

I've talked on the forum a bit about what we have to do with Logging to 
make it load with context reloading, and so it's been on my mind a bit. 
:)  One of the errors I'm often getting is dealing with commons-logging, 
and others because we have multiple logging files in the config directory 
that LogManager attempts to merge.

However, this is getting us into trouble in some ways:

	 -NO other logging system does this and therefore, if there's version 
conflicts, and other issues, logging configuration can often go right out 
the door.

	-Although the logging API's are pretty stable, the internal configuration 
mechanism isn't.  This can get Expresso in trouble with different versions 
of log4j, or commons-logging.

I was then thinking that since we have a default behavior for a root.  If 
we don't try to read multiple logging hierarchies and merge them together, 
we could get virtually the same functionality.  If an admin wants to 
customize logging for a particular branch, then the admin can add the 
particular category hierarchy difference, and they're done... so I'm not 
seeing any particular large losses of functionality.

[On a side note, I AM keeping separate struts-config type files since it 
would be SORELY missed for the pluggable components if we only had one 
config file.]

If you guys rely on it, let me know as it's more a 'design convenience' to 
have the multiple logging files gone.

Thanks,
						-Mike