From owen.k.b...@gmail.com on July 14, 2010 14:23:52

Due to the fact that people implementing ESAPI will be centralizing a lot of important information through ESAPI.properties and validation.properties, there should be a way to update that information.
Things such as white-list validation regexes, parameter names, upload requirements and limits, and mapping to classes should all have the ability to be updated.

Possible implementations include an executor that checks on an interval whether or not there have been changes to the properties file, then reloads based on those changes, meaning if:
-- ESAPI.HTTPUtilities=org.owasp.esapi.reference.DefaultHTTPUtilities
was changed to
-- ESAPI.HTTPUtilities=com.whatever.PersonalizedHTTPUtilities,
then
-- ESAPI.setHttpUtilties(PersonalizedHttpUtilities.getInstance());
would be called.

I haven't completely fleshed out this idea yet, so any general ideas would be helpful. What version of the product are you using? On what operating system? ESAPI.properties r1442

Original issue: http://code.google.com/p/owasp-esapi-java/issues/detail?id=131