[
https://issues.apache.org/jira/browse/ISIS-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13796502#comment-13796502
]
ASF subversion and git services commented on ISIS-401:
------------------------------------------------------
Commit 0476cc57709d5f4bbcda3fafb6491b70fb4f53b1 in branch refs/heads/master
from [~danhaywood]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=0476cc5 ]
ISIS-401: highlight row in table if changed by other
How it works:
- When the concurrency exception is found, it is stored in the EntityModel of
the row.
- IsisAjaxFallbackDataTable now uses a custom IItemReuseStrategy that allows
this this model
to be reused for the repainting of the table with new UI Items.
- requires EntityModel to implement equals/hashCode
- when repainting is done, the exception is cleared and in its stead the
row has a class set, "reloaded-after-concurrency-exception". This is
styled to highlight the row.
- a new Javascript library "livequery" (MIT licensed), sets up a callback
that looks for this new class. It sets up a callback to detect any row
element with this class and to remove it after a short period.
> In wicket viewer, concurrency checking is currently disabled when invoke
> action on an entity.
> ---------------------------------------------------------------------------------------------
>
> Key: ISIS-401
> URL: https://issues.apache.org/jira/browse/ISIS-401
> Project: Isis
> Issue Type: Bug
> Components: Viewer: Wicket
> Affects Versions: viewer-wicket-1.1.0
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Priority: Minor
> Fix For: viewer-wicket-1.3.0
>
>
> It should be re-enabled, however the links should be recomputed if the object
> is changed as the result of an edit. This might simply be a matter of
> changing from using Ajax to forcing a re-render.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
