Issue Details (XML | Word | Printable)

Key: GDS-626
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: William Draï
Reporter: Christoph Guse
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
GraniteDS

Support for Spring Security 3.0

Created: 05/Feb/10 02:29 PM   Updated: 26/Feb/10 02:27 PM   Resolved: 26/Feb/10 02:27 PM
Component/s: Spring services
Affects Version/s: 2.1.0_RC2
Fix Version/s: 2.1.0_GA

Environment: Java 1.6, Tomcat 6.0.20, Windows XP


 Description  « Hide
When I try to use GraniteDS with Spring 3 on a tomcat, I get the following exception:
java.lang.ClassNotFoundException: org.springframework.security.BadCredentialsException

I looked up the class in the API. It seems the BadCredentialsException was moved. In 2.0.x version of Spring-Security the path location is

org.springframework.security.BadCredentialsException,

in 3.0.x version the path is

org.springframework.security.authentication.BadCredentialsException

William Draï added a comment - 05/Feb/10 04:02 PM
The Spring Security 3 API is completely different.
It will be needed to implement a SpringSecurity3Service and an Identity3 bean.

heyoulin added a comment - 05/Feb/10 04:44 PM
I think should change to Spring Security 3.0 and remove 2.0. I already edit my code to Spring Security 3.0.

Max Bruchmann added a comment - 16/Feb/10 09:41 PM
can you remove the acegi and spring sec 2 libs and spring sec 3 libs to the eclipse projects build path?

Max Bruchmann added a comment - 16/Feb/10 09:44 PM
oops I meant "...and add the spring sec 3 libs to eclipse build path"

William Draï added a comment - 17/Feb/10 12:15 AM
Thanks, I always forget to commit the .classpath :(