[Esapi-user] Using ESAPI for security in our Web Application

Jeffrey Walton noloader at gmail.com
Mon Dec 10 03:55:46 UTC 2012

On Sun, Dec 9, 2012 at 10:37 PM, Kevin W. Wall <kevin.w.wall at gmail.com> wrote:
> Virtually every compilation error involving ESAPI is going to be some sort
> of class path problem. There are close to 30 dependencies for ESAPI. Start
> with making sure they are all in your class path.... you might want to try
> dropping all of them in a specific dedicated directory defined by system
> property java.ext.dirs, which you can set on the 'java' / 'javac' command
> line. That's about all I can help as I have not used JDeveloper.
30 dependencies? Ouch. That's 30 points of failure outside your control.

I guess now is a good time to ask: what procedures are in place to
make sure ESAPI is always current with respect to its dependencies?
Does ESAPI reference the external repos to ensure the externals are
always up to date?


> On Dec 8, 2012 11:51 PM, "Vallance, Jack S CTR USAF AFMC 78 ABW/SCPM"
> <Jack.Vallance.ctr at robins.af.mil> wrote:
>> I am new to OWASP, We have an existing Application and we would like to
>> add ESAPI security to it.
>> We are using JDeveloper, we down loaded esapi-2.0.1-dist.zip, we have
>> tried to install it to use in are
>>  application but there are too many error to compile. Is there
>> instructions for installing using JDeveloper?
>> I'm sure that we are doing something wrong, but don't know what it is.

More information about the Esapi-user mailing list