JavaServer Faces
by Hans Bergsten

The unconfirmed error reports are from readers.  They have not yet been 
approved or disproved by the author or editor and represent solely the
opinion of the reader.

Here's a key to the markup:
        [page-number]: serious technical mistake
        {page-number}: minor technical mistake
        <page-number>: important language/formatting problem
        (page-number): language change or minor formatting problem
        ?page-number?: reader question or request for clarification

This page was updated April 18, 2007.


UNCONFIRMED  errors and comments from readers: 


[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.


{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}"/>