[Esapi-user] Two ConfigurationException classes

Kevin W. Wall kevin.w.wall at gmail.com
Sun Feb 28 23:47:19 EST 2010


I just noticed, we have *two* ConfigurationException classes in ESAPI.

There's this:
java.lang.Object
  extended by java.lang.Throwable
      extended by java.lang.Exception
          extended by org.owasp.esapi.waf.ConfigurationException

used by WAF, and this:
java.lang.Object
  extended by java.lang.Throwable
      extended by java.lang.Exception
          extended by java.lang.RuntimeException
              extended by org.owasp.esapi.errors.ConfigurationException

used by almost everything else.

Can WAF live with the org.owasp.esapi.errors.ConfigurationException
class, which is a RuntimeException?  If not, could we possibly rename
it (perhaps WAFConfigurationException)?

I think having two exception classes is only going to confuse the
end users.

Thoughts?
-kevin
-- 
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