[ http://issues.apache.org/jira/browse/MYFACES-1409?page=comments#action_12452595 ] Leonid Mikhailov commented on MYFACES-1409: -------------------------------------------
Manfred, I believe there is an incompaibility in the behvior between MyFaces and JSF-RI which the attached ajax-progress-bar sample from the Sun's blueprint catalog illustrates. Concerning the trace, it is not the same trace one gets when running this code against JSF-RI. I guess that is exactly why the sample does not work correctly. Run the sample and see for yourself. Regards, Leonid > incorrect behavior after RESTORE_VIEW responseComplete > ------------------------------------------------------ > > Key: MYFACES-1409 > URL: http://issues.apache.org/jira/browse/MYFACES-1409 > Project: MyFaces Core > Issue Type: Bug > Components: General > Affects Versions: 1.1.5-SNAPSHOT > Environment: Windows XP, apache-tomcat-5.5.17 > Reporter: Leonid Mikhailov > Fix For: 1.1.5-SNAPSHOT > > Attachments: ajax-progress-bar-jsf-MyFaces.war > > > The following behavior appears to be incorrect in myfaces implementation of > JSF. > After FacesContext.responseComplete is issued in the afterPhase method of > the PhaseListener at the RESTORE_VIEW phase, myfaces implementation skips to > RENDER_RESPONSE phase. This appears to be incorrect, as following a call to > FacesContext.responseComplete JSF implementation should exit JSF lifecycle > completely, i.e. the next phase of the lifecycle should be again > RESTORE_VIEW. > > This problem can be observed when running Sun's Progress Bar with JSF and > AJAX Sample with myfaces libraries on Tomcat. -- 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
