[Esapi-user] Regarding ESAPI WAF

Kevin W. Wall kevin.w.wall at gmail.com
Mon Nov 15 23:50:27 EST 2010

On 11/15/2010 11:34 PM, Chris Schmidt wrote:
> 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?
> Arshan

+1 for burning it to the ground (i.e., removal)
Kevin W. Wall
"The most likely way for the world to be destroyed, most experts agree,
is by accident. That's where we come in; we're computer professionals.
We cause accidents."        -- Nathaniel Borenstein, co-creator of MIME

More information about the Esapi-user mailing list