Give this one a try later!
1. Setter methods take strings only
2. Action controller checks values
3. Store error messages using FacesContext.addMessage
4. Return null to redisplay form
How To Create Error Messages
Give this one a try later!
, 1. FacesContext.getCurrentInstance();
2. new FacesMessage("some warning");
3.
// add a message to form as a whole
context.addMessage(null, facesMessage);
or
// add a message to specific element
context.addMessage("someId", facesMessage);
How To Do Implicit Automatic Validation
Give this one a try later!
1. Define bean properties to be simple standard types
2. System attempts to convert types automatically and redisplays form if
conversion error with error message (converterMessage)
3. Define required fields on form with required="true" (requiredMessage)
h:dataTable Implementation
Give this one a try later!
, <h:dataTable var="item" value="#{bean.collection}"
styleClass="tableStyle"
headerClass="headerStyle"
rowClasses="even, odd">
<h:column>
<f:facet name="header">Prop</f:facet>
#{item.prop}
</h:column>
</h:dataTable>
EJB JavaBean Types
Give this one a try later!
1. Sessions Beans
2. Java Persistence API (JPA)
3. Message Driven Beans
Good Software Characteristics
Give this one a try later!
1. Correct
2. Scalable
3. Available
4. Secure
5. Sound
6. Interoperable
Need for Validation