From 60ef10e331da72e3495bef8b311ce74e257aac4c Mon Sep 17 00:00:00 2001
From: Ben Alex Acegi Security started out as a method interceptor for Spring IoC container
managed beans. Typically such beans provide services layer functions.
- Over time Acegi Security grew to offer authentication services, ThreadLocal management,
+ Over time Acegi Security grew to offer authentication services, History
ThreadLocal management,
web request filtering, extra AOP support,
ACL features, additional authentication mechanisms and so on (for those interested,
- see our change log.
There's plenty written about why the - Spring Framework + Spring Framework is a good fit for modern applications. If you're not familiar with the benefits Spring offers, please take a few minutes to learn more about it. In numerous situations Spring will save you many months (or even years) of development time. @@ -60,7 +60,7 @@ avoid its use by writing equivalent getter, setter and lifecycle invocation processes in standard Java code. This is a natural consequence of the Spring way of development, which emphasises framework independence (it is not because we think there are good - good reasons people would not use Spring).
+ reasons people would not use Spring).If it sounds too hard (it's not) or counter-productive (it is) to replace Spring's IoC services, don't forget you can always deploy Acegi Security and the Spring @@ -86,7 +86,7 @@
In summary, we recommend you take a look at Spring and consider using it in your - applications. Irrespective of whether you do or not, we strongly recommend you use it + applications. Irrespective of whether you do so or not, we strongly recommend you use it for configuration and lifecycle management of Acegi Security. If that is also not desired, Acegi Security can easily be executed without Spring at all, providing you implement similar IoC services. Acegi Security has very minimal dependencies directly on Spring,