Home

This Chapter
-Chapter 4: Input Validation and Data Conversion
-Data Types for Your Action Form’s Properties
-Input Validation and Data Conversion Example
-Using BeanUtils
-Efficient Conversion
-Summary

Table of Contents
-Introduction
-Chapter 1: Model 2 and Struts
-Chapter 2: Input Validation with Action Forms
-Chapter 3: The HTML Tag Library
-Chapter 4: Input Validation and Data Conversion
-Chapter 5: The Validator Plugin
-Chapter 6: The Expression Language
-Chapter 7: JSTL
-Chapter 8: The Bean Tag Library
-Chapter 9: The Logic Tag Library
-Chapter 10: Struts-EL, Nested, selectLabel
-Chapter 11: Message Handling and Internationalization
-Chapter 12: The Tiles Framework
-Chapter 13: Securing Struts Applications
-Chapter 14: The Config Object
-Chapter 15: The Persistence Layer
-Chapter 16: Object Caching
-Chapter 17: File Upload and File Download
-Chapter 18: Paging and Sorting
-Chapter 19: Preventing Double Submits
-Chapter 20: Early HttpSession Invalidation
-Chapter 21: Decorating Request Objects
-Chapter 22: How Struts Works

Previous
Next

 

Chapter 4

Input Validation and Data Conversion

As you have learned in Chapter 2, the action form’s main reason for existence is to help Struts programmers with user input validation. This chapter takes a closer look at input validation and deals with data conversion, a task that almost always precedes input validation. This chapter starts with a discussion of how to choose data types for your action form’s properties, so that smooth data conversion can be achieved in both Struts’ internals and in action objects. Three examples are then presented and the open source utility class BeanUtils, which is part of the Jakarta Commons project, is discussed.

Note

Chapter 5 covers the Validator plug-in, which helps you validate user input without Java code.

Previous
Next