ESAPI 2.2.0.0 DisplayTag 1.2 initialize class error #732
-
|
Updating from ESAPI 2.1.0.1 to 2.2.0.0 the below error occurs. The jar is in the WEB-INF/lib when packaged so im not sure if there is another dependency I am missing. Thanks [https-openssl-apr-10.10.10.101-9443-exec-1] org.apache.catalina.core.ApplicationDispatcher.invoke Servlet.service() for servlet [jsp] threw exception |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 5 replies
-
|
There are several dependency updates between the two esapi versions you're listing, and a few dependencies were entirely removed/replaced. My guess is that there was a transitive dependency on one of the removed dependencies, or an older version of the dependency, that is no longer packaged as part of the library. Roll the esapi library version back and use the maven dependency plugin to identify content you depend on that you are not specifying in your pom.
For any content identified as used and undeclared, add a declaration to your project. (Your project needs it so you should own it) After you've addressed all of those, you should be able to update esapi to the new version. |
Beta Was this translation helpful? Give feedback.
-
|
Right, but if you update to 2.2.1.0 or later (which you really should as it addresses 2 ESAPI vulnerabilities and lots of stuff that your SCA tools will squawk about), be sure to remember to update your ESAPI.Logger property in your ESAPI.properties file. You may find the discussion #696 useful in that regard. |
Beta Was this translation helpful? Give feedback.
-
|
@Pale-Banana - Did either or our replies help? If not, we are going to need more info. |
Beta Was this translation helpful? Give feedback.
-
|
@Pale-Banana - Any update on this? The class that caused the exception, org.displaytag.tags.TableTag, is not something that I think ESAPI has ever used. I'm not sure what is picking that up, but you may want to try running something like: $ mvn -B dependency:treeand see what is pulling displaytag in. |
Beta Was this translation helpful? Give feedback.
-
|
This is resolved. Thank you |
Beta Was this translation helpful? Give feedback.
-
|
Super. |
Beta Was this translation helpful? Give feedback.
There are several dependency updates between the two esapi versions you're listing, and a few dependencies were entirely removed/replaced.
My guess is that there was a transitive dependency on one of the removed dependencies, or an older version of the dependency, that is no longer packaged as part of the library.
Roll the esapi library version back and use the maven dependency plugin to identify content you depend on that you are not specifying in your pom.
mvn dependency:analyzeFor any content identified as used and undeclared, add a declaration to your project. (Your project needs it so you should own it)
After you've addressed all of those, you should be able to update esapi to the n…