The errata list is a list of errors and their corrections that were found after the product was released.
The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.
Color Key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update
| Version |
Location |
Description |
Submitted by |
Date submitted |
| Other Digital Version |
3/9
4th paragraph |
Chapter 7, Calidating Input
instead
Chapter 7, Validating Input
(ebook from iTunes App Store)
Note from the Author or Editor:
"Calidating" should be "Validating" |
Hil Gonzalez |
Nov 24, 2010 |
| Printed |
Page 126
First paragraph |
Using a Map instead of List returned by getExpenseTypeChoices does not work. I added a new function getExpenseTypes to return the expenseTypes Map in EntryHandler.java:
public Map getExpenseTypes() {
return expenseTypes;
}
Then I changed the entryFormArea.jspf to use expenseTypes instead of i18nChoices (in final version, or expenseTypeChoices in stage2 version):
<h:selectOneMenu id="type" required="true"
value="#{entryHandler.currentEntry.type}"
disabled="#{reportHandler.editDisabled}">
<f:selectItems
value="#{entryHandler.expenseTypes}"/>
</h:selectOneMenu>
Doing so, causes the "Validation Error: Value is not valid" error on this component. There appears to be an issue with JSF selectItems accepting a Map in the valueBinding, probably a bug in JSF. I'm using JSF 1.1 with Tomcat 5.5.
Just an fyi.
|
Anonymous |
|
| Printed |
Page 152
Example 8-4 |
Error in disabled attribute:
<h:commandButton value="Add"
disabled="#{reportHandler.addEntryDisabled}"
action="#{entryHandler.add}"/>
It should read:
<h:commandButton value="Add"
disabled="#{reportHandler.editDisabled}"
action="#{entryHandler.add}"/>
|
Anonymous |
|