SEC-889: Can't set a SecurityContextHolderStrategy instance for SecurityContextHolder directly #1144

Closed
spring-issuemaster opened this Issue Jun 17, 2008 · 3 comments

1 participant

@spring-issuemaster

Jürgen Heil (Migrated from SEC-889) said:

Currently i can put a custom strategy to hold the SecurityContext via SecurityContextHolder.setStrategyName(String). By SecurityContextHolder.initialize() the class try to load the custom strategy. When the custom class isn’t in the classpath i get a ClassNotFoundException. I found no way to set the instance directly.

@spring-issuemaster

Luke Taylor said:

I’m not quite clear what the problem is? Could you expand a bit on your requirements?

For example, why would your custom class not be on the classpath?

@spring-issuemaster

Jürgen Heil said:

My class ist not in the classpath because i’m using an OSGi-Container. I solved it by implementing a fragment bundle to your security-bundle.

@spring-issuemaster

Luke Taylor said:

OK - that sounds like a suitable resolution so I'll close as "won't fix". If there are any other comments or suggestions, please enter them here.

@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