You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Jesse Kuhnert (JIRA)" <de...@tapestry.apache.org> on 2007/04/05 18:37:32 UTC
[jira] Created: (TAPESTRY-1404) updateComponents="rootComponentId"
doesn't use clientId
updateComponents="rootComponentId" doesn't use clientId
-------------------------------------------------------
Key: TAPESTRY-1404
URL: https://issues.apache.org/jira/browse/TAPESTRY-1404
Project: Tapestry
Issue Type: Bug
Components: XHR/dhtml/Ajax
Affects Versions: 4.1.2
Environment: any
Reporter: Jesse Kuhnert
Assigned To: Jesse Kuhnert
Fix For: 4.1.2
When using the updateComponents="basicComponentId" in the standard components like DirectLink the basicComponentId attribute isn't translated into the client id of the component as it is currently rendering. This causes lots of confusion in things like For loops / etc. ...Change the DirectServiceParameter / DirectEngine / whatever so that it properly resolves these parameters during link construction.
--
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-1404) updateComponents="rootComponentId"
doesn't use clientId
Posted by "Marcus Schulte (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcus Schulte updated TAPESTRY-1404:
-------------------------------------
Fix Version/s: (was: 4.1.6)
4.1.7
> updateComponents="rootComponentId" doesn't use clientId
> -------------------------------------------------------
>
> Key: TAPESTRY-1404
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1404
> Project: Tapestry
> Issue Type: Bug
> Components: XHR/dhtml/Ajax
> Affects Versions: 4.1.2
> Environment: any
> Reporter: Jesse Kuhnert
> Assignee: Jesse Kuhnert
> Fix For: 4.1.7
>
>
> When using the updateComponents="basicComponentId" in the standard components like DirectLink the basicComponentId attribute isn't translated into the client id of the component as it is currently rendering. This causes lots of confusion in things like For loops / etc. ...Change the DirectServiceParameter / DirectEngine / whatever so that it properly resolves these parameters during link construction.
--
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-1404) updateComponents="rootComponentId"
doesn't use clientId
Posted by "Jesse Kuhnert (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jesse Kuhnert updated TAPESTRY-1404:
------------------------------------
Fix Version/s: (was: 4.1.2)
4.1.3
> updateComponents="rootComponentId" doesn't use clientId
> -------------------------------------------------------
>
> Key: TAPESTRY-1404
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1404
> Project: Tapestry
> Issue Type: Bug
> Components: XHR/dhtml/Ajax
> Affects Versions: 4.1.2
> Environment: any
> Reporter: Jesse Kuhnert
> Assignee: Jesse Kuhnert
> Fix For: 4.1.3
>
>
> When using the updateComponents="basicComponentId" in the standard components like DirectLink the basicComponentId attribute isn't translated into the client id of the component as it is currently rendering. This causes lots of confusion in things like For loops / etc. ...Change the DirectServiceParameter / DirectEngine / whatever so that it properly resolves these parameters during link construction.
--
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-1404)
updateComponents="rootComponentId" doesn't use clientId
Posted by "Andreas Andreou (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561761#action_12561761 ]
Andreas Andreou commented on TAPESTRY-1404:
-------------------------------------------
Whenever i had a need for something like this, i would use
updateComponents="ognl:clientId"
Wouldn't this work for you?
> updateComponents="rootComponentId" doesn't use clientId
> -------------------------------------------------------
>
> Key: TAPESTRY-1404
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1404
> Project: Tapestry
> Issue Type: Bug
> Components: XHR/dhtml/Ajax
> Affects Versions: 4.1.2
> Environment: any
> Reporter: Jesse Kuhnert
> Assignee: Jesse Kuhnert
> Fix For: 4.1.4
>
>
> When using the updateComponents="basicComponentId" in the standard components like DirectLink the basicComponentId attribute isn't translated into the client id of the component as it is currently rendering. This causes lots of confusion in things like For loops / etc. ...Change the DirectServiceParameter / DirectEngine / whatever so that it properly resolves these parameters during link construction.
--
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-1404) updateComponents="rootComponentId"
doesn't use clientId
Posted by "Jesse Kuhnert (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jesse Kuhnert updated TAPESTRY-1404:
------------------------------------
Fix Version/s: (was: 4.1.5)
4.1.6
> updateComponents="rootComponentId" doesn't use clientId
> -------------------------------------------------------
>
> Key: TAPESTRY-1404
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1404
> Project: Tapestry
> Issue Type: Bug
> Components: XHR/dhtml/Ajax
> Affects Versions: 4.1.2
> Environment: any
> Reporter: Jesse Kuhnert
> Assignee: Jesse Kuhnert
> Fix For: 4.1.6
>
>
> When using the updateComponents="basicComponentId" in the standard components like DirectLink the basicComponentId attribute isn't translated into the client id of the component as it is currently rendering. This causes lots of confusion in things like For loops / etc. ...Change the DirectServiceParameter / DirectEngine / whatever so that it properly resolves these parameters during link construction.
--
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-1404) updateComponents="rootComponentId"
doesn't use clientId
Posted by "Jesse Kuhnert (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jesse Kuhnert updated TAPESTRY-1404:
------------------------------------
Fix Version/s: (was: 4.1.3)
4.1.4
> updateComponents="rootComponentId" doesn't use clientId
> -------------------------------------------------------
>
> Key: TAPESTRY-1404
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1404
> Project: Tapestry
> Issue Type: Bug
> Components: XHR/dhtml/Ajax
> Affects Versions: 4.1.2
> Environment: any
> Reporter: Jesse Kuhnert
> Assignee: Jesse Kuhnert
> Fix For: 4.1.4
>
>
> When using the updateComponents="basicComponentId" in the standard components like DirectLink the basicComponentId attribute isn't translated into the client id of the component as it is currently rendering. This causes lots of confusion in things like For loops / etc. ...Change the DirectServiceParameter / DirectEngine / whatever so that it properly resolves these parameters during link construction.
--
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