Hi Michael, if you create a new View-Root, it is expected that the old components get lost - I would say that the selectItems should be recreated. Is that the case in your backing bean? Can you try to clean out the binding as well, and see what happens then?
regards, Martin On 9/28/06, Michael Heinen <[EMAIL PROTECTED]> wrote:
Hi, could anybody of the developers please respond to this issue? I would like to update to 1.1.4 but the below issue is of course a show stopper. This code works with 1.1.3 so there must be something working different in 1.1.4. Michael ________________________________ From: Michael Heinen [mailto:[EMAIL PROTECTED] Sent: Mittwoch, 27. September 2006 14:51 To: MyFaces Discussion Subject: RE: selectOneMenu looses values with myFacesCore 1.1.4 Sorry for posting answers to my own question but could further isolate the problem. The action listeners that are called by the immediate links, contain the following code in order to create new views: FacesContext context = FacesContext.getCurrentInstance(); ViewHandler viewHandler = context.getApplication().getViewHandler(); UIViewRoot viewRoot = viewHandler.createView(context, context.getViewRoot().getViewId()); context.setViewRoot(viewRoot); context.renderResponse(); When I remove these lines then the dropdpwn contains all the expected values. But I have to create a new view in the action listener. So what's going wrong inside ??? Michael ________________________________ From: Michael Heinen [mailto:[EMAIL PROTECTED] Sent: Mittwoch, 27. September 2006 14:34 To: MyFaces Discussion Subject: RE: selectOneMenu looses values with myFacesCore 1.1.4 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?
-- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
