Hi Matt, The more people that learn about AppFuse, the more that will likely contribute to it, and I'm sure some formal published content like this will go a long way to that goal. What a great opportunity to expand the community!
I definitely think that some content about "best practices" in coding would help people understand how to use AppFuse efficiently. For example, once you have a model for CRUD, from each layer of an app, giving the developer reasons to stick with that model (and not create a new way of doing CRUD) would really help. The same would go for other application-needs, like: security (auth/authz), views (css/xhtml). Something has to be said for making choices on infrastructural pieces, and then using those tools efficiently as they were designed to be used. I think a framework's value is in enabling speedy application development, and AppFuse highlights this well. If you're writing to a reader concerned about productivity, getting them to understand that committing to a to a framework is like committing to a best practice, which will allow them to work faster, is really compelling. Also, "configuration" might be an interesting section in your chapter. For each framework that AppFuse supports, the configuration is setup in the code, and nearly automatically setup in each app. This lets people use many framework features without having to worry so much about getting them configured, which takes a lot of time. From my own experience, dealing with Hibernate was initially painful, and went something like this: 1) understand mappings, 2) set everything up for Tomcat, 3) hand-code cfg.xml and other XML files, 4) create SQL scripts for the database, 5) run it all and pray it works, 6) decode obscure stacktraces.... well, it was better than the original EJB! Now Hibernate tools have come a long way, and AppFuse integrates them well, so all you have to do is create your object with annotations, and enter it in the hibernate.cfg.xml and you're in the DB! Customizations to the configuration are a snap, once the AppFuse groundwork is laid out. It's amazing, and a lot of the pain is taken away by using a system that is already configured. cheers, Jason mraible wrote: > > All, > > I've been asked to write a chapter on AppFuse for John Ferguson > Smart's upcoming Java Power Tools book: > > http://www.javapowertools.com > > Here's what John wrote in an e-mail where he asked me to write about > AppFuse: > > > >> For a tool like AppFuse, I would expect maybe 10-15 pages should be >> enough to cover the essential. As I said, I haven't played around with >> AppFuse yet, but the sort of things that would be interesting to cover >> could be: >> >> - How to jump-start a Java project with AppFuse (with a concrete >> example) >> - How to integrate with Maven (using the archetypes!) >> - How to integrate with Ant >> >> Things like integration with Spring and Hibernate should be mentioned, >> but not really treated in detail, as the vision of the book is very >> much around productivity support tools rather than APIs. >> > > What kind of things would you like to see in a 10-15 page chapter on > AppFuse? Here's what I'm thinking: > > Page(2): Topic > --------------------------------------------- > 1: What is AppFuse? > 2: Integrated Frameworks > 4: Starting a New Project with Archetypes > 5: Running/Deploying an Application > 6. Generating CRUD > 8: Testing > 9: Community > 10: Roadmap/Future > > Thanks for any feedback! > > Matt > > -- > http://raibledesigns.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/What-would-you-want-in-a-10-15-page-chapter-on-AppFuse--tf3854205s2369.html#a10921821 Sent from the AppFuse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
