You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Henri Dupre (JIRA)" <de...@tapestry.apache.org> on 2007/11/29 08:23:43 UTC
[jira] Created: (TAPESTRY-1938) Improve component lookup in
updateComponents
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
[jira] Updated: (TAPESTRY-1938) Improve component lookup in
updateComponents
Posted by "Jesse Kuhnert (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jesse Kuhnert updated TAPESTRY-1938:
------------------------------------
Fix Version/s: (was: 4.1.5)
4.1.6
> 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.6
>
>
> 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
[jira] Updated: (TAPESTRY-1938) Improve component lookup in
updateComponents
Posted by "Marcus Schulte (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcus Schulte updated TAPESTRY-1938:
-------------------------------------
Fix Version/s: (was: 4.1.6)
4.1.7
> 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.7
>
>
> 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
[jira] Commented: (TAPESTRY-1938) Improve component lookup in
updateComponents
Posted by "Henri Dupre (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12546809 ]
Henri Dupre commented on TAPESTRY-1938:
---------------------------------------
I figured out the trick with async = true and java code I think you are right, it would tie to a specific container component. Could you give an example of your parameter solution?
> 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
[jira] Commented: (TAPESTRY-1938) Improve component lookup in
updateComponents
Posted by "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