Add Logging support for SLF4J

[GoogleCodeExporter]

SLF4J is the next generation logging framework replacing commons logging and 
simplifies the complicated class loading used by commons logging(which normal 
breaks in Websphere). You can use a bridge to intercept log4j calls and 
direct these to SLF4J but feel it would be better to natively support SLF4J 
out of the box in ESAPI.

Original issue reported on code.google.com by ps.gr...@gmail.com on 27 Apr 2010 at 7:09

[GoogleCodeExporter]

I agree, this is critical. SLF4J is pretty impressive, I wanted to make it the 
default logger for ESAPI :) But I'm glad we abstracted it all out.

ps.grove, would you be interested in working on this patch?

Original comment by manico.james@gmail.com on 2 Nov 2010 at 7:44

• Added labels: Milestone-Release2.1

[GoogleCodeExporter]

Original comment by manico.james@gmail.com on 2 Nov 2010 at 8:00

• Changed state: Accepted

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Is this definitely coming out in Release 2.1?  I see this bug was filed over 2 
years ago and it seems that SLF4J is still not supported?  I am working on a 
project and we are trying to switch to Logback.  ESAPI is forcing us to have 
Log4J in the classpath.  Is there any status on this?

Original comment by mine...@gmail.com on 6 Nov 2012 at 9:02

[GoogleCodeExporter]

Is there any status on this in latest 2.1 release of esapi

Original comment by sara...@gmail.com on 21 Jan 2014 at 4:31

[GoogleCodeExporter]

This is really an enhancement request, not a defect.

Original comment by kevin.w.wall@gmail.com on 18 Sep 2014 at 7:50

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

This is critical for application that is already using SLF4J

Original comment by raymond....@gmail.com on 29 Jan 2015 at 4:07