"We're already done pulling out our hair. "

Ah, AppFuse... love it or hate it? 

It used to always take a few days for a Spring project to get underway because of the time spent just integrating your tools and frameworks, like Ant / Maven, Hibernate / Ibatis, Struts 1 / Struts 2 / Spring MVC / Tapestry / Freemarker / <yet another web framework>, web services, etc.  Then along came AppFuse with the promise of pre-integration of these frameworks, plus code-generation, schema-generation, and UI-generation based on your domain model!  Wow, magic!

The reality didn't quite live up to the promise.  Yes, you did save a huge amount of time upfront in pre-integrating the tools and frameworks, but then you do spend some time later on paring down the bloat.  And then there were the bugs in code-generation - some issues in generating child classes in complex graphs.

Why are we complaining?  It was the best tool at the time and it did improve our productivity.  Props to you, Matt Raible!

AppFuse has a steep learning curve and some gotchas here and there.  It takes a while for developers to get ramped-up in the framework.  If you have an existing AppFuse system and want to work with developers who've been there and done that with AppFuse and know its ins and outs, look no further.  We're already done pulling out our hair. :-)