DOMConfigurator is being used inappropriately in the ESAPIWebApplicationFirewallFilter

marylinh / owasp-esapi-java

Automatically exported from code.google.com/p/owasp-esapi-java

Other

0 stars 0 forks source link

DOMConfigurator is being used inappropriately in the ESAPIWebApplicationFirewallFilter #163

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago

Please migrate this to the ESAPI logging framework.

Original issue reported on code.google.com by manico.james@gmail.com on 1 Nov 2010 at 4:21

GoogleCodeExporter commented 8 years ago

Original comment by manico.james@gmail.com on 1 Nov 2010 at 12:52

Added labels: Milestone-Release2.0

GoogleCodeExporter commented 8 years ago

Original comment by manico.james@gmail.com on 3 Nov 2010 at 9:55

GoogleCodeExporter commented 8 years ago

Release 2.1 still uses DOMConfigurator. It would be nice to get away from the 
Log4J dependency and leave implementation up to the ESAPI or Jakarta Commons 
logging framework. Is there an ETA on this change?

Original comment by justinas...@gmail.com on 26 Jan 2015 at 6:26