Validation does not work with esapi jakarta jar about esapi-java-legacy HOT 3 CLOSED

This line in your exception stack trace:

at org.owasp.esapi.util.ObjFactory.loadMethodByStringName(ObjFactory.java:196) ~[esapi-2.5.3.1.jar:2.5.3.1]

shows that you are using the wrong jar file. The Jakarta jar file for ESAPI should be named 'esapi-jakarta-2.5.3.1.jar' instead. (E.g., see https://repo1.maven.org/maven2/org/owasp/esapi/esapi/2.5.3.1/.)
Maybe Gradle pulled down both versions or the wrong version, I'm not sure. I you want to create a mini-dummy project using your build.gradle and Spring Boot 3.x, I can take a look at it and see if I can figure it out, but otherwise, I don't have the time to troubleshoot this for quite some time.

from esapi-java-legacy.

@popa-raluca - BTW, one quick and dirty workaround might be for you to explicitly download the 'esapi-jakarta-2.5.3.1.jar' directly from https://repo1.maven.org/maven2/org/owasp/esapi/esapi/2.5.3.1/ and then rename 'esapi-jakarta-2.5.3.1.jar' as 'esapi-2.5.3.1.jar'. It's admittedly a bit of a kludge, but it should allow you to make progress. If this happens with the Jakarta version of the jar though, please let us know. I just used 'strings' to confirm that the 'javax.servlet.http' package had been rewritten (at the byte-code level) as 'jakarta.servlet.http', but that's the only testing I did on it.

from esapi-java-legacy.

I think the problem was that the initial dependency that I added was without the jakarta identifier, and a clean build didn't add the correct lib afterwards. I was able to force redownload of the dependencies using gradle clean build --refresh-dependencies and then the right jakarta jar was added.

from esapi-java-legacy.