[ 
https://issues.apache.org/jira/browse/MYFACES-2483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12806767#action_12806767
 ] 

Leonardo Uribe commented on MYFACES-2483:
-----------------------------------------

Attached the final patch for this feature (fixPSSIf2009JAN-14.patch). I removed 
the listener used to register components to be restored fully, and it was 
replaced by doing that when the component is saved. Other minor updates to the 
algorithm has been done.

> Find a way to allow c:if work with partial state saving enabled
> ---------------------------------------------------------------
>
>                 Key: MYFACES-2483
>                 URL: https://issues.apache.org/jira/browse/MYFACES-2483
>             Project: MyFaces Core
>          Issue Type: Task
>          Components: JSR-314
>            Reporter: Leonardo Uribe
>            Assignee: Leonardo Uribe
>         Attachments: fixPSSIf2009JAN-10.patch, fixPSSIf2009JAN-11.patch, 
> fixPSSIf2009JAN-14.patch, fixPSSIf2009JAN-7.patch
>
>
> This one is difficult to solve but I still think it is possible.
> It was explored trying to solve MYFACES-2428, and it seems ri is trying to do 
> something about it too on:
> https://javaserverfaces.dev.java.net/issues/show_bug.cgi?id=1408
> and
> https://javaserverfaces.dev.java.net/issues/show_bug.cgi?id=1313
> One strategy to solve this one is this:
> 1. Mark the parent component containing c:if to not save it partially.
> 2. Do not execute c:if on postback and partial state saving enabled.
> In theory, the parent component should be restored fully from saved state.
> Note that things like:
> <c:if>....
>    <p>Some markup</p>
> <c:if>
> is just invalid. It is expected that c:if only contains components with state.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to