Upgrading from 0.8.0 to 1.0.0

The following should help most casual users of the project update their applications:

• The most significant change in 0.9.0 is that ContextHolder and all of its related classes have been removed. This significant change was made for the sake of consistency with the core Spring project's approach of a single ThreadLocal per use case, instead of a shared ThreadLocal for multiple use cases as the previous ContextHolder allowed. This is an important change in 0.9.0. Many applications will need to modify their code (and possibly web views) if they directly interact with the old ContextHolder. The replacement security ThreadLocal is called SecurityContext and provides a single getter/setter for Authentication. There is thus no need to work with SecureContext or Context anymore.
  
  To migrate, simply modify all your code that previously worked with ContextHolder, SecureContext and Context to directly call SecurityContext. You will also note that the HttpSessionContextIntegrationFilter no longer provides a context property, so remove it from your application context XML. For the relatively small number of users who had customised their context, you will need to write your own ThreadLocal to provide functionality for your specific use case.
  
  We apologise for the inconvenience, but on a more positive note this means you receive strict type checking, you no longer need to mess around with casting to and from Context implementations, your applications no longer need to perform checking of null and unexpected Context implementation types, and the new SecurityContext is an InheritableThreadLocal - which should make life easier in rich client environments.
  
  
• AbstractProcessingFilter has changed its getter/setter approach used for customised authentication exception directions. See the AbstractProcessingFilter JavaDocs to learn more.