seamless integration of commons-logging, log4j and websphere

Reason Logging with log4j and commons logging is painful in websphere because of several issues: * classloading PARENT_FIRST/LAST may result in not finding commons-logging or log4j * IBM packages commons-logging without a log4jLogFactory. * the SERVICE-ID method for finding log4j is not well known * IBM documentation on this is confusing * Log4j watchdog (for hot reload of updated log4j settings) starts a background thread that is not stopped when an application is stopped or undeployed. LogBridge is a small project that solves all of these. Features logging works, regardless of classloading policy log4j.properties can be hot reloaded, without threading problems. Can be turned off by setting log4j-reload-interval=0 in logging.properties Sadly no support yet for log4j.xml / other logging frameworks underneath commons-logging. Usage Put the jarfile (downloa