[
https://issues.apache.org/jira/browse/MYFACES-2774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12887140#action_12887140
]
Leonardo Uribe commented on MYFACES-2774:
-----------------------------------------
Other option instead use a Map<UIComponent, Boolean> per view could be use a
Stack<Map<UIComponent, Boolean> > or something similar.
ComponentSupport.markForDeletion is called first and then
ComponentSupport.finalizeForDeletion is called last, but most times if no
components where marked for deletion on the current "level" finalizeForDeletion
does not do anything, but in that way or something similar we can "detect" when
this is happening.
> Remove MARK_DELETED attribute from the component
> ------------------------------------------------
>
> Key: MYFACES-2774
> URL: https://issues.apache.org/jira/browse/MYFACES-2774
> Project: MyFaces Core
> Issue Type: Improvement
> Components: General, JSR-314
> Affects Versions: 2.0.0
> Reporter: Marius Petoi
> Priority: Minor
> Attachments: markDeletedFaceletContext.patch
>
>
> The ComponentSupport.MARK_DELETED attribute is used only inside one request.
> It doesn't need to be saved in the state. It should be removed from the
> attributes of the component. Instead a list of components marked for deletion
> should be included in the FaceletContext.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
