[jira] Resolved: (TAPESTRY-1938) Improve component lookup in updateComponents

View: New views
1 Messages — Rating Filter:   Alert me  

[jira] Resolved: (TAPESTRY-1938) Improve component lookup in updateComponents

by Tapestry - Dev mailing list :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


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

Andreas Andreou resolved TAPESTRY-1938.
---------------------------------------

       Resolution: Won't Fix
    Fix Version/s:     (was: 4.1.7)
                   unspecified
         Assignee: Andreas Andreou

> Improve component lookup in updateComponents
> --------------------------------------------
>
>                 Key: TAPESTRY-1938
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1938
>             Project: Tapestry
>          Issue Type: Improvement
>          Components: Core Components
>    Affects Versions: 4.1.3
>            Reporter: Henri Dupre
>            Assignee: Andreas Andreou
>             Fix For: unspecified
>
>
> Currently updateComponents works only with nested components. However, since Taperstry 4.1 all components have unique ids. It would be nice if updateComponent would allow updating any component on the page with a given id instead of only nested ones.

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