[ 
https://issues.apache.org/jira/browse/TRINIDAD-1488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matthias Weßendorf updated TRINIDAD-1488:
-----------------------------------------

       Resolution: Fixed
    Fix Version/s:  1.2.12-core
         Assignee: Matthias Weßendorf
           Status: Resolved  (was: Patch Available)

> ChangeManager: Ability to apply component changes to a subtree
> --------------------------------------------------------------
>
>                 Key: TRINIDAD-1488
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-1488
>             Project: MyFaces Trinidad
>          Issue Type: New Feature
>          Components: Archetype
>    Affects Versions:  1.2.11-core
>            Reporter: Andy Schwartz
>            Assignee: Matthias Weßendorf
>            Priority: Minor
>             Fix For:  1.2.12-core
>
>         Attachments: TRINIDAD-1488.patch
>
>
> The ChangeManager currently only supports applying component changes to the 
> entire view.  This is accomplished via the following API:
> public void applyComponentChangesForCurrentView(FacesContext facesContext)
> I would like to have the ability to apply component changes to a specific 
> subtree as opposed to the entire view.  This would require a new API along 
> the lines of:
> public void applyComponentChangesForSubtree(FacesContext facesContext, 
> NamingContainer root)
> Note that this method would operate on a subtree rooted at a NamingContainer 
> in order to allow ChangeManager to easily filter the component changes based 
> on id comparisons.  (SessionChangeManager already has access to scoped ids 
> for each component change, so checking whether a particular change is 
> applicable by examining the id should be very efficient.)
> The reason for requesting this new API is that I have cases where portions of 
> the subtree are created dynamically at render time, after 
> applyComponentChangesForCurrentView() has been called.  I need to be able to 
> apply component changes directly to the newly created subtrees without 
> re-applying the changes to the entire view.

-- 
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