Conventions Used in This Book

The following font conventions are used in this book:

Italic is used for:

Unix pathnames, filenames, and program names
Internet addresses, such as domain names and URLs
New terms where they are defined

Boldface is used for:

Names of GUI items (window names, buttons , menu choices, etc.)

Constant width is used for:

Command lines and options that should be typed verbatim
Names and keywords in Java programs, including method names, variable names, and class names
XML element names and tags, attribute names, and other XML constructs that appear as they would within an XML document

Indicates a tip, suggestion, or general note.

Indicates a warning or caution.

Using Code Examples

This book is here to help you get your job done. In general, you may use the code in this book in your programs and documentation. You do not need to contact us for permission unless you're reproducing a significant portion of the code. For example, writing a program that uses several chunks of code from this book does not require permission. Selling or distributing a CD-ROM of examples from O'Reilly books does require permission. Answering a question by citing this book and quoting example code does not require permission. Incorporating a significant amount of example code from this book into your product's documentation does require permission.

We appreciate, but do not require, attribution. An attribution usually includes the title, author, publisher, and ISBN. For example: " Programming Jakarta Struts , Second Edition, by Chuck Cavaness. Copyright 2004 O'Reilly Media, Inc., 0-596-00651-9."

If you feel your use of code examples falls outside fair use or the permission given above, feel free to contact us at permissions@oreilly.com.

Comments and Questions

Please address comments and questions concerning this book to the publisher:

O'Reilly Media, Inc.

1005 Gravenstein Highway North

Sebastopol, CA 95472

800-998-9938 (in the U.S. or Canada)

707-829-0515 (international or local)

707-829-0104 (fax)

There is a web page for this book, which lists errata, examples, and additional information. You can access this page at:

http://www.oreilly.com/catalog/0596006519

To comment or ask technical questions about this book, send email to:

bookquestions@oreilly.com

For more information about books, conferences, Resource Centers, and the O'Reilly Network, see the O'Reilly web site at:

http://www.oreilly.com

Acknowledgments

Writing a book of this type is never the work of just one person; it literally takes an army of hardened soldiers, and this book is no exception. From the editors to the marketing organization to the reviewers of the manuscript, this book simply would not have been possible without the group of dedicated folks that gave up many of their nights and weekends to help ensure that the quality was the highest possible. Any credit should be given to all of the great people involved; any mistakes are mine alone.

First, I need to thank my O'Reilly editors, Brett McLaughlin and Robert Eckstein, two of the most dedicated and sincere editors that I have worked with. I hope we have a chance to work together on future projects. Your advice and leadership made the task much easier than I could have imagined. I also would like to thank Kyle Hart from O'Reilly's marketing department. Your help was dearly appreciated.

Next, I would like to acknowledge the team of fine developers that I first learned Struts with. The bond that our little NV team had was something special that comes around only once in a while. I really enjoyed working with all of you.

The following people played a special role by giving me advice on the book's content and direction: Steve Ardis, Jill Entinger, See Yam Lim, and Ted Husted (although Ted may not realize that he contributed in this way).

When I first decided to post the draft chapters of the book, I made a comment that if any reviewers went beyond the call of duty, I would personally thank them in the acknowledgments of the book. Little did I realize how many would take me up on it! There are so many that I can't thank each and every one individually. Over 100 people contributed feedback for one or more chapters of this book. The Struts community is by far one of the best. Almost every person on the Struts mailing list has contributed in one way or another. To each of you, thank you!

Thanks to the following people: John Guthrie, David Karr, Brent Kyle, Stefano Scheda, and Rick Reumann for asking all the right questions, Mark Galbreath for reminding me of my 10th-grade English teacher, and James Mitchell and James Holmes for getting me involved with the Atlanta Struts group.

I need to say a special thanks to Tim Drury for his help on Chapter 16. His Ant skills are known worldwide. Special thanks also to Brian Keeton, who wrote Chapter 13 because I'm too slow -he's the smartest EJB developer I know. Both of you are great friends and simply the finest humans that I've ever met. Just knowing you has made me a better person. I hope we can work together again.

The group at TheServerSide.com deserves special thanks from me and the reviewers for allowing the draft chapters of this book to be available for download. This is a great example of what the future holds for book publishing.

I would be remiss if I didn't thank the entire Struts community. I have met and corresponded with many smart developers who also strike me as just really fun people to hang around with. The feedback and suggestions I received during this process were awesome . I hope that all of you got some benefit out of this, and I appreciate everyone's patience while some of this was figured out as I went.

Finally, all Struts developers should give thanks to Craig McClanahan for having the wits about him to create the framework and make it freely available to the community. He could have tried to make a profit from it by starting Struts, Inc., but he realized that he would be rewarded ten-fold anyway, and I'm sure he has been. Craig, it's a nice framework, you should be proud. And to all of the committers on the Struts project, what would it really be without you? Thanks for all of your help.