Cannot get esapi to run on eclipse #22

Closed
meg23 opened this Issue Nov 13, 2014 · 6 comments

Comments

Projects
None yet
1 participant

meg23 commented Nov 13, 2014

From joachim....@mediaman.de on February 24, 2009 06:33:52

I use Eclipse with Tomcat 5.5 and JRE 1.4.2 for a simple demo project.

owasp-esapi-full-java-1.4.jar is in my lib-folder AND added to the J2EE
Module Dependencies.

Used several methods to add the properties file to my VM arguments.

I continually get the following Exception report on a simple jsp file:

org.apache.jasper.JasperException: org/owasp/validator/html/PolicyException

I suspect there should be a "esapi" in the object path, but owasp is
immediately followed by validator. Since there is no documentation of
installation or troubleshooting the installation is seek for help here.

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

meg23 commented Nov 13, 2014

From joachim....@mediaman.de on February 24, 2009 03:34:48

PS: Root Cause is:

java.lang.NoClassDefFoundError: org/owasp/validator/html/PolicyException

Looks like a Class cannot be found...

meg23 commented Nov 13, 2014

From kfe...@gmail.com on April 16, 2009 13:10:13

Have you checked the "Problems" tab? Is there a warning similar to this?

Classpath entry C:/Users/XXXX/Downloads/owasp-esapi-full-java-1.4.jar will not be
exported or published. Runtime ClassNotFoundExceptions may result.

If so, check if there is a "Quick Fix" when you right click on the problem. For me,
it says, "Mark the associated raw classpath entry as a publish/export dependency".
This solves the problem for me.

meg23 commented Nov 13, 2014

From kfe...@gmail.com on April 16, 2009 13:34:46

To manually fix this issue, right-click the project and choose "Properties".
Select "Java EE Module Dependencies" from the list on the left.
If the ESAPI JAR is already listed, be sure it is checked off on the list.
If the ESAPI JAR is not listed, add it with "Add JAR" or "Add External JAR".
Apply. This should export ESAPI to the server to resolve your problem.

Status: Fixed
Owner: kfealz

meg23 commented Nov 13, 2014

From bhwhe...@gmail.com on July 09, 2009 05:15:12

There are dependancies not mentioned in the set-up. You need to include the antisamy
jar in your classpath also - it contains the missing class.

meg23 commented Nov 13, 2014

From abhijitp...@gmail.com on May 01, 2011 23:07:15

Add these lines to pom.xml

        <dependencies>
              <dependency>
              <groupId>owasp-esapi</groupId>
              <artifactId>owasp-esapi</artifactId>
        </dependency>
        <dependency>
              <groupId>antisamy</groupId>
              <artifactId>antisamy</artifactId>
        </dependency>
        <dependency>
              <groupId>commons-fileupload</groupId>
              <artifactId>commons-fileupload</artifactId>
        </dependency>
  </dependencies>

Then try with a clean/package. In case, if its still not working try with a clean/install/package

meg23 commented Nov 13, 2014

From harrison...@gmail.com on December 14, 2011 12:44:16

make sure you include antisamy-1.4.4.jar in your project

meg23 closed this Nov 13, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment