Home/ Questions/Q 8284169
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-08T10:59:46+00:00

I’m migrating an application that uses Spring security 3.0 to Spring security 3.1. I

  • 0

I’m migrating an application that uses Spring security 3.0 to Spring security 3.1.

I have been getting an error about incorrect schema being referenced:

SEVERE: Exception sending context initialized event to listener instance of class    
org.springframework.web.context.ContextLoaderListener
org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration    
problem: You must use a 3.0 schema with Spring Security 3.0.(2.0 or 3.1 versions are not  
valid) Please update your schema declarations to the 3.0.3 schema (spring-security- 
3.0.3.xsd).
Offending resource: ServletContext resource [/WEB-INF/security-context.xml]

When I look in /lib I see a number of jars that are 3.1 versions are duplicated as 3.0 versions. I suspect this is what is causing the error above.

When I look at the dependency tree of the pom.xml using the Eclipse Maven plugin, I can see where the earlier versions are being referenced (eg spring-security-acl depends on several 3.0 jars) but they are marked as ‘omitted for conflict with…’. Does that not mean they should be omitted from the built war file?

I’ve tried explicitly naming 3.1 versions of those files at the root of my pom but the older versions still get included.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I’m still not sure what was going on, but I tried creating a new project in Eclipse with the same pom and source files and now the project seems to behave itself.

    • 0