Gian -
Or even better how do the costs of
implementation relate to each other,
in the book's scenarios?
Alas, I didn't directly track that information (although it would be interesting now). It would also be biased -- some of the frameworks were in beta, so I had to track down problems that don't exist now. There was also learning curve involved with some of them.
Here is a highly subjective list of my relative effort for each framework, with top being the least and bottom being the most:
Struts Velocity
InternetBeans Express
WebWork
Tapestry
Cocoon
Of course, this also doesn't take into account the added features. Tapestry has a steep learning curve, but if offers a stunning array of services. Struts is pretty easy for an existing developer, but doesn't offer as much as some of the others.
Neal Ford<br />Author, <i>Art of Java Web Development: Struts, Tapestry, Commons, Velocity, JUnit, Axis, Cocoon, InternetBeans, WebWork</i><br /><a href="http://www.nealford.com" target="_blank" rel="nofollow">www.nealford.com</a>