[
https://issues.apache.org/jira/browse/MYFACES-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16979435#comment-16979435
]
Thomas Andraschko commented on MYFACES-4304:
--------------------------------------------
My sample app doesn't throw a exception, so i think it's different ;)
Same as the other issue. Try to replicate in primefaces-test and make a new
issue.
> dynamic ui:include doesn't always work
> --------------------------------------
>
> Key: MYFACES-4304
> URL: https://issues.apache.org/jira/browse/MYFACES-4304
> Project: MyFaces Core
> Issue Type: Bug
> Components: General
> Affects Versions: 2.2.12, 3.0.0-SNAPSHOT, 2.3.5
> Reporter: Thomas Andraschko
> Assignee: Thomas Andraschko
> Priority: Major
> Fix For: 2.2.13, 3.0.0-SNAPSHOT, 2.3.6
>
> Attachments: primefaces-test.7z
>
>
> Just run the attached sample
> - initially there is "" assigned to the ui:include
> - if you open the sidebar via "include 1", a new src is set and the UI
> updated but the include is not in the view
> it seems to happen because of this If:
> if (!PhaseId.RESTORE_VIEW.equals(ctx.getFacesContext().getCurrentPhaseId()))
> in the IncludeHandler.
> Seems that our IncludeHandler is executed to early in RESTORE_VIEW, as the
> new include is set in the INVOKE_APPLICATION phase.
> In both Mojarra and MyFaces VDL#buildView is called 2 times on the POST:
> 1) in RestoreView
> 2) in RenderResponse
> The difference is, that only Mojarra calls the IncludeHandler in both phases.
> MyFaces calls it only in RestoreView.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
