Book idea: Struts Best Practices

Some ideas for the book

• defining roles: Architect, HTML developer, Java developer, Tester, Designer, Business Analysts
• do not use DynaForms as it causes contention on the struts-config.xml file.
• a chapter of using Excel to create the properties and java constants file.
• a chapter on creating a custom MessageResource
• dividing up the work, for every page one action goes to a JSP/tiles and another action performs form processing
• only one form per page
• using JAAS to perform login rather than creating own login system.
• Useful utility classes such as: LabelValue bean
• Separating business logic from presentation logic

The main premise of the book is to prevent people from building new things on top of Struts where Struts already provides facilities or extension points. I've seen many projects that try to build so many extensions or wrappers around struts that you don't even know you're using Struts anymore. The purpose of using a framework is to lessen your work not to increase it, otherwise why the heck would we use it?