Spring Security 2.0 Final Release: No More Dead Fairies |
|

Spring Security 2.0 has been released. This is a major step forward for the Spring Portfolio. Spring (Acegi) Security is already the Java platform's most widely used enterprise security framework, with over 250,000 downloads on SourceForge and over 20,000 downloads per release. Through making it so much simpler to use, this release will undoubtedly take adoption to a new level.
I'm particularly pleased about this release for a number of reasons:
- It's a great thing for the Spring community. It's (a lot) simpler to use, as well as more powerful. It puts the most powerful enterprise Java security solution within the reach of many more users, pretty much eliminating the hurdles to adoption. See this tutorial for an example of just how much easier it makes it to secure a typical web application. The proliferation of XML bean definitions is a thing of the past.
- It's a continuation of the work of Spring 2.x, through applying the power of a custom XML namespace to enable aggressive defaulting, while still allowing for customization.
- Like Spring 2.5, it exhibits the current Spring Portfolio trend toward radical reduction in the need for XML.
- It's a proof of the value of the SpringSource business model. Our revenue model enables us to invest more than ever in creating open source software. Without being able to hire both Acegi/Spring Security creator Ben Alex and the other major committer, Luke Taylor, this release either wouldn't have occurred or would have been much less extensive.
- It's good for the fairy kingdom.
Acegi/Spring Security creator Ben Alex and Luke Taylor have done a great job. Ben will be talking about Spring Security at Java One next month. If you'll be in San Francisco then, it will be a great opportunity to hear about the new features and get a chance to talk to the guy behind the product.
Download here.
Similar Posts
- Why did we raise $10m?
- Long time, no blog
- What's New and Cool in Spring 2.0?
- New releases in the Spring Portfolio
- Why the name Acegi?





-FoX- says:
Added on April 17th, 2008 at 4:36 amSpringSource surely did a good job with this release, simplifying the configuration for the security aspect. Securing with Acegi was no problem, but you needed to know the internal working of the system well, now there is more abstraction to the configuration.
What about the other enfant-terrible, Spring-RCP?
I really think it is time to either drop the project, or start supporting it in a better way!
Jason says:
Added on April 17th, 2008 at 5:57 amI'm very much looking forward to using it. As soon as 2.0.1 comes out
Oh, and does this release mean that blanket legal immunity has been offered to previous Acegi users who are at least partially responsible for the Fairy genocide? I still live in fear of being arrested and tried in The Hague…
blair says:
Added on April 17th, 2008 at 5:08 pm-FoX-: Spring-RCP has had a 1.0 release in the last month, and it looks like some bug fixes will be coming for it.
In bigger news however, there is a new project called Spring-Desktop, which looks like it is going to be a rewrite of RCP, hopefully using the bean binding / beans validation and swing application framework JSRs (295, 296 and 303).
Markus Jais (codekite.com) says:
Added on April 18th, 2008 at 1:16 amGreat news. The further reduction of the XML stuff is great.
Güzel Sözler says:
Added on April 21st, 2008 at 8:05 pmThanks for the great news..
söve says:
Added on November 4th, 2008 at 8:48 amthanks.
pavan says:
Added on July 9th, 2009 at 11:55 amI feel spring security 2.0 is good. But I want to know can we use spring security with stand along swing clients if possible how. I tried at many places but did not get any example
komik videolar says:
Added on November 16th, 2009 at 1:56 pmThanks for the great news..
tatil otelleri says:
Added on February 19th, 2010 at 12:18 pmThanks for the great news..
metin2 yang says:
Added on May 10th, 2010 at 4:01 ammade by owen
estetik says:
Added on April 6th, 2011 at 2:49 amGood article i like and thank you for this article.
tr..