[Esapi-user] Regarding ESAPI WAF

Chris Schmidt chrisisbeef at gmail.com
Mon Nov 15 23:34:58 EST 2010

I am forwarding this message along for Arshan


Devs and users,
For the final 2.0 release we wanted to more tightly integrate the WAF into
the rest of ESAPI. This means that the WAF will use the ESAPI logger instead
of log4j, its exceptions will extend ESAPI exceptions, etc. Does anyone
object to these old API being removed instead of deprecated? The reason we'd
like to remove entirely as opposed to deprecate is to remove dependencies on
things like log4j which would otherwise hang around only to satisfy the
deprecated methods.
Looking for your vote on this - remove or deprecate?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.owasp.org/pipermail/esapi-user/attachments/20101115/25777dd9/attachment.html 

More information about the Esapi-user mailing list