2. Using the Tutorial Examples
3. Getting Started with Web Applications
5. JavaServer Pages Technology
7. JavaServer Pages Standard Tag Library
10. JavaServer Faces Technology
11. Using JavaServer Faces Technology in JSP Pages
12. Developing with JavaServer Faces Technology
13. Creating Custom UI Components
14. Configuring JavaServer Faces Applications
Application Configuration Resource File
Using the managed-bean Element
Initializing Properties Using the managed-property Element
Referencing an Initialization Parameter
Initializing Array and List Properties
Initializing Managed Bean Properties
Registering Custom Error Messages
Registering Custom Localized Static Text
Registering a Custom Converter
Registering a Custom Renderer with a Render Kit
Registering a Custom Component
Basic Requirements of a JavaServer Faces Application
Configuring an Application with a Deployment Descriptor
Identifying the Servlet for Life Cycle Processing
Specifying a Path to an Application Configuration Resource File
Specifying Where State Is Saved
Restricting Access to JavaServer Faces Components
Turning On Validation of XML Files
Including the Required JAR Files
Including the Classes, Pages, and Other Resources
15. Internationalizing and Localizing Web Applications
16. Building Web Services with JAX-WS
17. Binding between XML Schema and Java Classes
19. SOAP with Attachments API for Java
21. Getting Started with Enterprise Beans
23. A Message-Driven Bean Example
24. Introduction to the Java Persistence API
25. Persistence in the Web Tier
26. Persistence in the EJB Tier
27. The Java Persistence Query Language
28. Introduction to Security in the Java EE Platform
29. Securing Java EE Applications
31. The Java Message Service API
32. Java EE Examples Using the JMS API
36. The Coffee Break Application
37. The Duke's Bank Application
If the application developer provides an implementation of the Validator interface to perform validation, you must register this custom validator in the application configuration resource file by using the validator XML element:
<validator> ... <validator-id>FormatValidator</validator-id> <validator-class> com.sun.bookstore6.validators.FormatValidator </validator-class> <attribute> ... <attribute-name>formatPatterns</attribute-name> <attribute-class>java.lang.String</attribute-class> </attribute> </validator>
The validator-id and validator-class elements are required subelements. The validator-id element represents the identifier under which the Validator class should be registered. This ID is used by the tag class corresponding to the custom validator tag.
The validator-class element represents the fully qualified class name of the Validator class.
The attribute element identifies an attribute associated with the Validator implementation. It has required attribute-name and attribute-class subelements. The attribute-name element refers to the name of the attribute as it appears in the validator tag. The attribute-class element identifies the Java type of the value associated with the attribute.
Creating a Custom Validator explains how to implement the Validator interface.
Using a Custom Validator explains how to reference the validator from the page.
Copyright © 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices
Scripting on this page tracks web page traffic, but does not change the content in any way.