SEC-1136: Remove SpringSecurityException #1385

Closed
spring-issuemaster opened this Issue Apr 12, 2009 · 2 comments

1 participant

@spring-issuemaster

Luke Taylor (Migrated from SEC-1136) said:

There is no longer much purpose in having a single base exception throughout the framework, given the diversity of uses. It would make more sense to have the base exceptions for the core areas of functionality (acls, access-failure, authentication-failure etc) extend NestedRuntimeException individually as the Spring Framework does.

@spring-issuemaster

Luke Taylor said:

I’ve introduced a new base class for Acl exceptions. ExceptionTranslationFilter now checks explicitly or AccessDeniedException and AuthenticationException (as it really should) and Jaas exceptions are translated to AuthenticationException instances.

@spring-issuemaster

Luke Taylor said:

In retrospect, there’s no need to use NestedRuntimeException anymore as basic Java classes now all provide access to the root cause.

@spring-issuemaster spring-issuemaster added this to the 3.0.0 M1 milestone Feb 5, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment