[ http://issues.apache.org/jira/browse/TAPESTRY-1125?page=all ]
Jesse Kuhnert resolved TAPESTRY-1125.
-------------------------------------
Resolution: Fixed
The For component and DojoAjaxResponseBuilder logic have been re-factored to
properly handle these situations now. Please feel free to report back if the
problem persists.
> Duplicate id and updateComponents
> ---------------------------------
>
> Key: TAPESTRY-1125
> URL: http://issues.apache.org/jira/browse/TAPESTRY-1125
> Project: Tapestry
> Issue Type: Bug
> Components: Framework, Web
> Affects Versions: 4.1, 4.1.1
> Environment: Win XP, tomcat 5.5.17
> Reporter: Frank Jørgensen
> Assigned To: Jesse Kuhnert
> Fix For: 4.1.1
>
>
> Got a problem with duplicate id's :
> <a jwcid="@DirectLink"
> listener="listener:setAvailable"
> id="ognl:currentHour.id"
> updateComponents="ognl:{'calendar'}"
> async="ognl:true"
> parameters="ognl:currentHour"
> class="setavailable">
> </a>
> When Tapestry render the HTML there are 2 id's in the code, and this gives
> the async update a javascript error.
> Want to make my own id because, the link will not be a link after the async
> update, and if I let Tapestry generate the id's, then the DirectLink id's
> will not be the same as before the update. And the AJAX/DOJO javascript is
> not updated, so the next time I click on a Link it will not be async.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
