Done
https://issues.apache.org/jira/browse/TAP5-2025
Please vote the bug
On Sat, Nov 3, 2012 at 7:38 PM, Thiago H de Paula Figueiredo <
thiag...@gmail.com> wrote:
> On Sat, 03 Nov 2012 12:47:51 -0200, Dimitris Zenios <
> dimitris.zen...@gmail.com> wrote:
>
> I managed to fix it by overriding
On Sat, 03 Nov 2012 12:47:51 -0200, Dimitris Zenios
wrote:
I managed to fix it by overriding
JavascriptSupport PartialMarkupRendererFilter to use "_" +
atomicValue.addAndGet(1) + Long.toHexString(System.currentTimeMillis())
as unique ids suffix.I don't know if this is the optimal solution b
Nice work! Please file a JIRA and post it to the list
On Nov 3, 2012, at 5:43 AM, Dimitris Zenios wrote:
> Hi everyone.
>
> I have a page that has 10 grids.Each grid is inPlace updated and also
> contained inside a progressive display.What happens is that sometimes a
> sort event link id is t
The problem is inside the javascriptSupport PartialMarkupRendererFilter.Id
allocator has prefix of Long.toHexString(System.currentTimeMillis()). So if
two request come at the same time all generated ids of both request will
have the same prefix.Thats what happens here.Since each grid is inside a
pr
Since each grid is inPlace then sorting links become an ajax link that is
connected with the zone through updatezoneonevent javascript function.If we
have two elements with the same id then both will be updated when doing
ajax request for sort.
On Sat, Nov 3, 2012 at 1:39 PM, Thiago H de Paula Fi
On Sat, 03 Nov 2012 07:43:52 -0200, Dimitris Zenios
wrote:
Hi everyone.
Hi!
As far as I can remember, this problem is caused by Grid using @Persist in
the field that holds the sorting information, not due to repeated ids.
--
Thiago H. de Paula Figueiredo
--
