Logging bridge is in charge of bridging the OSGi log events toward
SLF4J but even when it does, like because an Apache Dependency Manager
callback didn't complete, it doesn't give the information on who is
the culprit and why, making debugging more difficult, this enhace the
logging.
Change-Id: I388516b3bc40d94552f49d6928b3b33c8349b687
Signed-off-by: Giovanni Meo <gmeo@cisco.com>
if (this.logger != null) {
switch (entry.getLevel()) {
case LogService.LOG_DEBUG:
if (this.logger != null) {
switch (entry.getLevel()) {
case LogService.LOG_DEBUG:
- this.logger.debug(entry.getMessage());
+ this.logger.debug("Bundle:{} Message:{} Exception:{}", entry.getBundle()
+ .getSymbolicName(), entry.getMessage(), entry.getException());
break;
case LogService.LOG_INFO:
break;
case LogService.LOG_INFO:
- this.logger.info(entry.getMessage());
+ this.logger.info("Bundle:{} Message:{} Exception:{}", entry.getBundle()
+ .getSymbolicName(), entry.getMessage(), entry.getException());
break;
case LogService.LOG_WARNING:
break;
case LogService.LOG_WARNING:
- this.logger.warn(entry.getMessage());
+ this.logger.warn("Bundle:{} Message:{} Exception:{}", entry.getBundle()
+ .getSymbolicName(), entry.getMessage(), entry.getException());
break;
case LogService.LOG_ERROR:
break;
case LogService.LOG_ERROR:
- this.logger.error(entry.getMessage());
+ this.logger.error("Bundle:{} Message:{} Exception:{}", entry.getBundle()
+ .getSymbolicName(), entry.getMessage(), entry.getException());