You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Manfred Geiler (JIRA)" <de...@myfaces.apache.org> on 2006/11/23 09:33:04 UTC

[jira] Commented: (MYFACES-1409) incorrect behavior after RESTORE_VIEW responseComplete

    [ http://issues.apache.org/jira/browse/MYFACES-1409?page=comments#action_12452172 ] 
            
Manfred Geiler commented on MYFACES-1409:
-----------------------------------------

I don't get it.
Your log documents correct behaviour:
After the first RESTORE_VIEW when responseComplete = true there is no RENDER_RESPONSE following.
In the next (new!) Lifecycle, after the second RESTORE_VIEW the responseComplete = false (!) and the RENDER_RESPONSE is executed. This is ok.
Please, more info on that issue.
Thanks,
Manfred

> 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