Thanks to a colleague that mentioned AppFuse, I Googled, ended here and then found this article - Seven simple reasons to use AppFuse in developerWorks (at this point, you know it’s good, since developerWorks articles are usually deserve thumbs up). Going through it, I have no idea how AppFuse slipped under my radar for so long. This framework (or super-framework), if does all it claims to do, is the perfect tool to use to kick-start any Java web project. It’s that good. Integrated testing (DBUnit, jMock, bla bla), ease of deployment (Maven 2, Ant), support for persistence layers (Hibernate, iBATIS), able to use the popular web frameworks (Struts 1, WebWorks, Spring MVC), and much more (I’m still reading here). We’ve got a couple of projects coming in, and you can bet I’ll use AppFuse 
Filed under:
Programming
2 Responses to this post
Leave a comment
Hey, have you used AppFuse for any of your applications? So, what is your opinion now? I have a requirement where I am supposed to develop a small website (say within 20 pages), with not much load, but has to complete within a short time. I don’t know Spring/Hibernate/Maven/Webworks. I have a working knowledge of Struts. What is your suggestion?
If time is a concern, I would say stay away from new stuff as much as possible. If you’ve not used AppFuse before, now might not be a good time to start experimenting.
My suggestion is to stick with Struts if you need to finish things quickly. Learning Webworks would take time by itself. Spring too has a learning curve, but should still be relatively quick to pickup.
The only new stuff I think it’s worth learning is Hibernate since it does allow you to do away with all SQL and JDBC boilerplate code.
My AppFuse project is still yet to start so I’ve not used it yet.