The good folks at Atlassian have written a nice tutorial on Integrating Crowd with AppFuse and Acegi. Crowd is a web-based single sign-on (SSO) tool that simplifies application provisioning and identity management. We use Crowd for the AppFuse project to maintain a single user store for JIRA, Confluence, and Bamboo. It's worked awesome for us.
AppFuse Light 1.8.1 is a bug fixes release that includes an upgrade to Spring 2.5 and Wicket 1.3 RC1. See the Release Notes for more information on what's changed since the last release.
What is AppFuse Light? Click here to find out.
AppFuse Light is a lightweight version of AppFuse.
I was inspired to create it while writing Spring Live and
looking at the struts-blank and webapp-minimal
applications that ship with Struts and Spring, respectively.
These "starter" apps were not robust enough for me, and I wanted
something like AppFuse, only simpler.
AppFuse Light is designed to show Java Web Developers how to start
a bare-bones webapp using a
Spring-managed middle-tier backend and
Hibernate for persistence. By default, AppFuse Light uses Spring for
its MVC framework, but you can change it to
Wicket. In addition, there's a
number of extras for Spring MVC, including Velocity and FreeMarker versions, Ajax
support and Acegi Security support.
This project was formerly named Equinox and has been under development since April 2004.
AppFuse Light now offers 60 possible combinations for
- Web Frameworks: JSF (MyFaces), Spring MVC (with
Ajax, Acegi Security, JSP, FreeMarker or Velocity), Stripes, Struts
1.x, Struts 2.x, Tapestry, WebWork, Wicket
- Persistence Frameworks: Hibernate, iBATIS, JDO (JPOX), OJB, Spring JDBC
If you have any questions about this release, please subscribe to the AppFuse user mailing list by sending a blank e-mail to
firstname.lastname@example.org. You can also post questions in a forum-like fashion using Nabble: http://appfuse.org/forum/user.
If you're a developer of one of the frameworks that AppFuse Light uses - I'd love a code review to make sure I'm "up to snuff" on how to use your framework. I'm also more than willing to give commit rights if you'd like to improve the implementation of your framework.
Live demos are available at:
What's on tap for AppFuse Light 2.0? Here's what I'm hoping to do:
- Drop the seldom-used persistence frameworks: JDBC, JDO and OJB.
- Drop Struts 1.x and WebWork as web frameworks (replaced by Struts 2).
- Support the same persistence frameworks as AppFuse: Hibernate,
iBATIS and JPA.
- Re-use appfuse-service, appfuse-hibernate, appfuse-ibatis and
appfuse-jpa in AppFuse Light. I'll likely include the core classes
(User, Role) since AppFuse Light is more "raw" than AppFuse.
- Require Java 5.
Let me know if you disagree with any of these items or would like to see other enhancements.