Originally posted by baskarsenguttuvan: Hi, Please let me know advantage of reading your book!!
Very good question Baska. Well, lets see what the advantages are ... If you are a novice, you will learn Struts.. If you are already experienced in Struts, you will pick some strategies or some novel ideas for designing your applications better. The best parts of the book (exluding coverage of other usual Struts functionality) are: 1)Exhaustive coverage of using images for form submissions (majority of us want that feature) 2)How to develop a DispatchAction like functionality for Image based form submissions. Note that you dont get this functionality out-of-the-box 3)How to edit and submit list based forms using indexed properties? 4)How to use Pager tag libraries with Struts to achieve paging. Illustration of a high performance paging mechanism 5) A foolproof exception handling framework that is production-ready 6) A mechanism to handle duplicate form submissions in a generic manner - You dont have to code the Sync Token code in every Action. 7) A crash course of JSTL, when and why JSTL makes sense with Struts and the case for Struts-EL
Finally advantage is always relative, since all of us have different skill sets. So, I encourage you to check out the table of contents to see if you stand to gain anything from the book.
"baskarsenguttuvan", Welcome to the JavaRanch! May I ask you to drop by at My Profile and change your display name into something compliant with our naming policy (first name and last name required)? Thanks. PS. You'll become eligible for the book promotion by having a valid display name
Originally posted by Albert Moliner: Hi. Any justification in the book of pros and cons of action chaining? I've seen some people dearly discourage its use, but I haven't been able to find the reasons in the struts mailing list. Thanks!
Well I like the concept of action chaining. I use them like this: - every form I display has an action that prepares the display of the page - every form will post to a specialized action that just processes the forms input So I will first prepare a page in action1. process the user's input in action2. Then I pass on control to action3 to prepare the next response to the user and so on. When the stuff I do is small I will merge action 1 and action2. but I will retain the action chaining to action3. Wonder what the others think about my reasoning hth Alexander