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

["Andreas Andreou (JIRA)" <de...@tapestry.apache.org>]

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

Andreas Andreou commented on TAPESTRY-1938:
-------------------------------------------

Wouldn't this tie your components to a specific container component?

What I usually do in this case is have an updateComponents parameter in my custom 
components, so that containers can specify it

You can also specify this in java code... cycle.getReseponseBuilder().updateComponent(id)

> 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
>             Fix For: 4.1.4
>
>
> 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.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org