You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@tapestry.apache.org by "Kalle Korhonen (JIRA)" <ji...@apache.org> on 2013/04/15 15:24:17 UTC

[jira] [Resolved] (TAP5-2025) Duplicate generated ids

     [ https://issues.apache.org/jira/browse/TAP5-2025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kalle Korhonen resolved TAP5-2025.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 5.4
                   5.3.7

Changed to use nanoTime() instead of millis. This doesn't prevent id conflicts from happening, but should greatly reduce the chances.
                
> Duplicate generated ids
> -----------------------
>
>                 Key: TAP5-2025
>                 URL: https://issues.apache.org/jira/browse/TAP5-2025
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.3.5, 5.3.6
>            Reporter: Dimitris Zenios
>            Assignee: Kalle Korhonen
>              Labels: duplicate, id
>             Fix For: 5.3.7, 5.4
>
>
> IdGenerator of javascriptSupport PartialMarkupRendererFilter is using Long.toHexString(System.currentTimeMillis()) as a suffix for ids.If two ajax requests arrive at the same time they will both have the same suffix.If both request will render a component named Sort (From grid) then many sort links will have same ids.Found it out because i had 10 progressive displays in my page each drawing an inPlace grid.Some of the sort links will also sort another grid when clicked since they have the same id.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira