tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dimitris Zenios (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAP5-2025) Duplicate generated ids
Date Mon, 15 Apr 2013 14:22:15 GMT

    [ https://issues.apache.org/jira/browse/TAP5-2025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13631741#comment-13631741
] 

Dimitris Zenios commented on TAP5-2025:
---------------------------------------

Why dont you use an atomic variable that will increment and set as uid along with currentTimeInMillis.
This way there is no possibility of having conflicts.
                
> 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

Mime
View raw message