Hey Howard. Yes, I'm the one that gave your book a poor review here at Javaranch.
I have been waiting for this promo though because I would like to ask a few questions about the book in relation to my review.
Why did you choose the Hangman Game as the first demo application in your book? To me, this is not something that someone learning Tapestry would want to know. The Login Form would have been a better starting place IMO.
The login form example started off really strong, but then faded into component descriptions and the example never seemed to be complete. Could you explain this?
It's not just your Action book. I think the entire In Action series is promoted badly. I think the entire series should be renamed as I don't think In Action signifies what these books actual teach.
I tried to keep my review of the book solely about the book and not about Tapestry. I find Tapestry very interesting, I just had issues with the book. If you could clear some of my questions up for me, that would be great.
I thought the Hangman application was fun, and a lighter introduction. Forms are a bit more complicated than basic links.
In addition, a lot of the "light touch" of Tapestry is demonstrated in the Hangman game; the clean division betweeen view (HTML template) and business logic (the model, i.e., the page class).
One of the books editorial reviewers had the same reaction you did, most of the others were very enthusiastic about Hangman.
In terms of what happens after login ... the point of the book is to understand that cycle of data coming into the application, being used for server-side processing, and flowing out again in the form of HTML. Once you have the user name and the password inside your page class, what happens next is not all that interesting, and is certainly not universal ... it could be a twenty or thirty or fifty page side track to discuss what it means to "log on" to the application.
Chapters 9 and 10 go into detail about mangaing login and user authentication in the context of a specific application, the Virtual Library.
What I wanted to do in the book, and I think I suceeded, was provide a series of examples that build gradually in complexity but also show the most common scenarios you will face developing a Tapestry application.
--<br />Howard M. Lewis Ship<br />Independent J2EE / Open-Source Java Consultant<br />Creator, Jakarta Tapestry<br />Creator, Jakarta HiveMind<br /><a href="http://howardlewisship.com" target="_blank" rel="nofollow">http://howardlewisship.com</a>