I forgot to mention that SearchControllerBean has sessionScope.

 

During debugging I found out that the corresponding setter setSavedSearchesMenu is called two times.

 

public void setSavedSearchesMenu(UISelectOne savedSearchesMenu) {

   this.savedSearchesMenu = savedSearchesMenu;

}

 

The first time the parameter savedSearchesMenu is correctly populated.

Then getSavedSearchesMenu is called.

The setter is called again then and savedSearchesMenu (of type HtmlSelectOneMenu) is not initialized anymore.

All attributes are null or false except _valid which is true.

Any ideas?

 

Is this a bug (It did work with 1.1.3) ?

 

Michael


From: Michael Heinen [mailto:[EMAIL PROTECTED]
Sent: Mittwoch, 27. September 2006 14:07
To: MyFaces Discussion
Subject: selectOneMenu looses values with myFacesCore 1.1.4

 

After updating myFacesCore to 1.1.4 a selectOneMenu is not working anymore. I use tomahawk-1.1.3.

The entries of the select one menu are cleared after clicking an immediate link.

When I go back to myFacesCore 1.1.3 everything works fine.

 

Here is the jsp snippet:

<h:panelGroup>

   <h:outputText value="Quick Search"/>

   <t:selectOneMenu id="lastSearch" binding="#{SearchControllerBean.savedSearchesMenu}"/>

</h:panelGroup>

 

SearchControllerBean:

public UISelectOne getSavedSearchesMenu() {

            if (this.savedSearchesMenu==null){

                        this.populateSavedSearchesMenu(); 

            }

            return this.savedSearchesMenu;

}

 

I set a breakpoint into the above method.

savedSearchesMenu is a HtmlSelectOneMenu and it's childrenList contains two objects:

An UISelectItem and an UISelectItems with 5 SelectItems.

But these are not displayed anymore in the html. The dropdown is empty.

Any ideas?

Reply via email to