[ http://issues.apache.org/jira/browse/MYFACES-1365?page=comments#action_12421135 ] Torsten Krah commented on MYFACES-1365: ---------------------------------------
browse test1.faces first: 14.07.2006 17:31:48 my.examples.util.PhaseTracker beforePhase INFO: BEFORE RESTORE_VIEW(1) 14.07.2006 17:31:48 my.examples.util.PhaseTracker afterPhase INFO: AFTER RESTORE_VIEW(1) 14.07.2006 17:31:48 my.examples.util.PhaseTracker beforePhase INFO: BEFORE RENDER_RESPONSE(6) 14.07.2006 17:31:49 my.examples.util.PhaseTracker afterPhase INFO: AFTER RENDER_RESPONSE(6) click on selectmenu, choose a value: 14.07.2006 17:32:52 my.examples.util.PhaseTracker beforePhase INFO: BEFORE RESTORE_VIEW(1) 14.07.2006 17:32:52 my.examples.util.PhaseTracker afterPhase INFO: AFTER RESTORE_VIEW(1) 14.07.2006 17:32:52 my.examples.util.PhaseTracker beforePhase INFO: BEFORE APPLY_REQUEST_VALUES(2) 14.07.2006 17:32:52 my.examples.util.PhaseTracker afterPhase INFO: AFTER APPLY_REQUEST_VALUES(2) 14.07.2006 17:32:52 my.examples.util.PhaseTracker beforePhase INFO: BEFORE PROCESS_VALIDATIONS(3) 14.07.2006 17:32:52 my.examples.sortabletable.TableData rowsChanged INFO: value changed event: 5 14.07.2006 17:32:52 my.examples.util.PhaseTracker afterPhase INFO: AFTER PROCESS_VALIDATIONS(3) 14.07.2006 17:32:52 my.examples.util.PhaseTracker beforePhase INFO: BEFORE UPDATE_MODEL_VALUES(4) 14.07.2006 17:32:52 my.examples.util.PhaseTracker afterPhase INFO: AFTER UPDATE_MODEL_VALUES(4) 14.07.2006 17:32:52 my.examples.util.PhaseTracker beforePhase INFO: BEFORE INVOKE_APPLICATION(5) 14.07.2006 17:32:52 my.examples.util.PhaseTracker afterPhase INFO: AFTER INVOKE_APPLICATION(5) 14.07.2006 17:32:52 my.examples.util.PhaseTracker beforePhase INFO: BEFORE RENDER_RESPONSE(6) 14.07.2006 17:32:52 my.examples.util.PhaseTracker afterPhase INFO: AFTER RENDER_RESPONSE(6) now test2.faces - clear cookies, browse it: 14.07.2006 17:33:23 my.examples.util.PhaseTracker beforePhase INFO: BEFORE RESTORE_VIEW(1) 14.07.2006 17:33:23 my.examples.util.PhaseTracker afterPhase INFO: AFTER RESTORE_VIEW(1) 14.07.2006 17:33:23 my.examples.util.PhaseTracker beforePhase INFO: BEFORE RENDER_RESPONSE(6) 14.07.2006 17:33:23 my.examples.util.PhaseTracker afterPhase INFO: AFTER RENDER_RESPONSE(6) now change value like in test1.faces: 14.07.2006 17:33:53 my.examples.util.PhaseTracker beforePhase INFO: BEFORE RESTORE_VIEW(1) 14.07.2006 17:33:53 my.examples.util.PhaseTracker afterPhase INFO: AFTER RESTORE_VIEW(1) 14.07.2006 17:33:53 my.examples.util.PhaseTracker beforePhase INFO: BEFORE APPLY_REQUEST_VALUES(2) 14.07.2006 17:33:53 my.examples.util.PhaseTracker afterPhase INFO: AFTER APPLY_REQUEST_VALUES(2) 14.07.2006 17:33:53 my.examples.util.PhaseTracker beforePhase INFO: BEFORE PROCESS_VALIDATIONS(3) 14.07.2006 17:33:53 my.examples.sortabletable.TableData rowsChanged INFO: value changed event: 5 14.07.2006 17:33:53 my.examples.util.PhaseTracker afterPhase INFO: AFTER PROCESS_VALIDATIONS(3) 14.07.2006 17:33:53 my.examples.util.PhaseTracker beforePhase INFO: BEFORE RENDER_RESPONSE(6) 14.07.2006 17:33:54 my.examples.util.PhaseTracker afterPhase INFO: AFTER RENDER_RESPONSE(6) change it a second time: 14.07.2006 17:34:14 my.examples.util.PhaseTracker beforePhase INFO: BEFORE RESTORE_VIEW(1) 14.07.2006 17:34:14 my.examples.util.PhaseTracker afterPhase INFO: AFTER RESTORE_VIEW(1) 14.07.2006 17:34:14 my.examples.util.PhaseTracker beforePhase INFO: BEFORE APPLY_REQUEST_VALUES(2) 14.07.2006 17:34:14 my.examples.util.PhaseTracker afterPhase INFO: AFTER APPLY_REQUEST_VALUES(2) 14.07.2006 17:34:14 my.examples.util.PhaseTracker beforePhase INFO: BEFORE PROCESS_VALIDATIONS(3) 14.07.2006 17:34:14 my.examples.sortabletable.TableData rowsChanged INFO: value changed event: 15 14.07.2006 17:34:14 my.examples.util.PhaseTracker afterPhase INFO: AFTER PROCESS_VALIDATIONS(3) 14.07.2006 17:34:14 my.examples.util.PhaseTracker beforePhase INFO: BEFORE UPDATE_MODEL_VALUES(4) 14.07.2006 17:34:14 my.examples.util.PhaseTracker afterPhase INFO: AFTER UPDATE_MODEL_VALUES(4) 14.07.2006 17:34:14 my.examples.util.PhaseTracker beforePhase INFO: BEFORE INVOKE_APPLICATION(5) 14.07.2006 17:34:14 my.examples.util.PhaseTracker afterPhase INFO: AFTER INVOKE_APPLICATION(5) 14.07.2006 17:34:14 my.examples.util.PhaseTracker beforePhase INFO: BEFORE RENDER_RESPONSE(6) 14.07.2006 17:34:15 my.examples.util.PhaseTracker afterPhase INFO: AFTER RENDER_RESPONSE(6) Like you can see, for the first event their are phases missing. Using a submit button instead of onchange=submit() results in the same workflow like test2.faces. kind regards Torsten > h:selectOneMenu - Phase processing broken for the first selectOneMenu when > using 2 of them. > ------------------------------------------------------------------------------------------- > > Key: MYFACES-1365 > URL: http://issues.apache.org/jira/browse/MYFACES-1365 > Project: MyFaces Core > Issue Type: Bug > Affects Versions: 1.1.3 > Environment: tomcat 5.5.17, java 1.5 > Reporter: Torsten Krah > > Using two selectOneMenu on one page results in a broken phase processing. > example: > Works: > <html> > <%@ taglib uri="http://java.sun.com/jsf/core"; prefix="f"%> > <%@ taglib uri="http://java.sun.com/jsf/html"; prefix="h"%> > <%@ taglib uri="http://myfaces.apache.org/tomahawk"; prefix="t"%> > <[EMAIL PROTECTED] file="../inc/head.jsp"%> > <body> > <f:view> > <h:form> > <f:loadBundle basename="my.examples.ressources.messages" > var="msgs" /> > <h:selectOneMenu id="oneoption" value="#{tableData.rows}" > onchange="submit()" > valueChangeListener="#{tableData.rowsChanged}" > immediate="true"> > <f:selectItem itemValue="5" itemLabel="5" /> > <f:selectItem itemValue="10" itemLabel="10" /> > <f:selectItem itemValue="15" itemLabel="15" /> > <f:selectItem itemValue="20" itemLabel="20" /> > </h:selectOneMenu> > </h:form> > </f:view> > <[EMAIL PROTECTED] file="../inc/page_footer.jsp"%> > </body> > </html> > doesnt work: > <html> > <%@ taglib uri="http://java.sun.com/jsf/core"; prefix="f"%> > <%@ taglib uri="http://java.sun.com/jsf/html"; prefix="h"%> > <%@ taglib uri="http://myfaces.apache.org/tomahawk"; prefix="t"%> > <[EMAIL PROTECTED] file="../inc/head.jsp"%> > <body> > <f:view> > <h:form> > <f:loadBundle basename="my.examples.ressources.messages" > var="msgs" /> > <h:selectOneMenu id="oneoption" value="#{tableData.rows}" > onchange="submit()" > valueChangeListener="#{tableData.rowsChanged}" > immediate="true"> > <f:selectItem itemValue="5" itemLabel="5" /> > <f:selectItem itemValue="10" itemLabel="10" /> > <f:selectItem itemValue="15" itemLabel="15" /> > <f:selectItem itemValue="20" itemLabel="20" /> > </h:selectOneMenu> > <h:selectOneMenu value="#{tableData.country}" > onchange="submit()"> > <f:valueChangeListener > > type="my.examples.sortabletable.CountryListener" /> > <f:selectItems value="#{tableData.countryNames}" /> > </h:selectOneMenu> > </h:form> > </f:view> > <[EMAIL PROTECTED] file="../inc/page_footer.jsp"%> > </body> > </html> > Using the first one, the event gets fired and looking at the phase listener, > all 6 phases are processed. > Using the second example with both menus and firing an event on the first > menu, application invoke and model update phase aren't executed. > The second menu works fine > Only happens after the bean is new - using it on a already created session > bean, works. Only after the first invoking of the view this happens. > I don't see any cause why the first event should not process phase 4 and 5 ( > like it does when only one menu is used ), so imho it's a bug. > kind regards > Torsten -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
