[ http://issues.apache.org/jira/browse/TAPESTRY-1155?page=all ]
Jesse Kuhnert resolved TAPESTRY-1155.
-------------------------------------
Fix Version/s: 4.1.1
Resolution: Fixed
> Same event ID is generated for EventListener rendered within loop
> -----------------------------------------------------------------
>
> Key: TAPESTRY-1155
> URL: http://issues.apache.org/jira/browse/TAPESTRY-1155
> Project: Tapestry
> Issue Type: Bug
> Components: Core
> Affects Versions: 4.1.1
> Environment: Not environment related
> Reporter: Andy Yeung
> Assigned To: Jesse Kuhnert
> Fix For: 4.1.1
>
>
> I have use the EventListener with the use of target while the target is
> rendered within a For. The script can generate multiple javascript with
> different clientId but the event ID are the same.
> ComponentEventConnectionWorker.getEvents function need to include the
> clientId during hash generation to prevent duplicated event ID for component.
> But I also found that this method is also called by renderBody method besides
> linkComponent. So I don't know whether the fix is adding a String as
> parameter for initial hash and pass target (renderBody) and
> clientId(linkComponent) to generate the initial hash value.
--
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]
