SEC-2082: ClassNotFoundException: org.springframework.security.web.firewall.Firewall edResponse

[spring-projects-issues]

Migrated from SEC-2082

[spring-projects-issues]

Rob Winch said:

FirewalledResponse is in the spring-security-web-3.1.3.RELEASE.jar within maven central, so I am afraid I do not have enough information to determine what your issues is.

Where did you get your jar from (i.e. downloads section, maven central, spring's maven repositories, etc)?

Ensure all of your dependencies on the classpath (i.e. ensure you have spring-security-web-3.1.2.RELEASE.jar on your classpath)

Are there any other errors in the logs?

Can you provide a project that demonstrates the problem (I am not able to reproduce this)

[spring-projects-issues]

Vernon said:

To answer your questions:

1. maven file configuration download. I don't know where the jar file is from.
2. It occurred in a local deployment from a clear build. It is unlikely the jar file isn't in the library.
3. That was the only error at the time.
4. The error occurred in my local development. If you want to see the problem in a live environment, you need to have a physical access to the machine. That is not possible.

I rolled back the Spring Security version to 3.1.2, that is to change the SS version in my pom file, without any other change. And the problem doesn't occur.

[spring-projects-issues]

Rob Winch said:

In reply to comment #2:

To answer your questions:

1. maven file configuration download. I don't know where the jar file is from.

This will depend on your maven configuration. Can you post your pom.xml and maven settings.xml?

1. It occurred in a local deployment from a clear build. It is unlikely the jar
   file isn't in the library.

Can you post the project? Does the issue occur every time? Does it happen for other individuals using the build? If you rename your local maven repository, does the issue still occur (testing to see if your local maven repo is corrupt)?

1. That was the only error at the time.

Can you post the logs when this error occurs?

1. The error occurred in my local development. If you want to see the problem in
   a live environment, you need to have a physical access to the machine. That is
   not possible.

Your goal should be to provide a small project that replicates the issue. Typically a binary search (i.e. making a copy and deleting portions of the project that appear to be irrelevant until you have a minimal project) works best for me. If you are unable to provide information for me to reproduce the issue or a sample project to reproduce it, then this JIRA will be closed as cannot reproduce. There are a number of reasons I feel this is just to to:

If you look at the spring security sample projects there are many examples that demonstrate there is not an issue.

Additionally, there are many other users that have not had this issue.

If I cannot reproduce it, the issue cannot be fixed anyways

I rolled back the Spring Security version to 3.1.2, that is to change the SS
version in my pom file, without any other change. And the problem doesn't occur.

[spring-projects-issues]

Rob Winch said:

As per previous comments...closing as cannot reproduce