[
https://issues.apache.org/jira/browse/ISIS-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Haywood resolved ISIS-248.
------------------------------
Resolution: Fixed
rev: 1376402
> Perform concurrency checking within the persistor (rather than rely on every
> viewer/client to do the check)
> -----------------------------------------------------------------------------------------------------------
>
> Key: ISIS-248
> URL: https://issues.apache.org/jira/browse/ISIS-248
> Project: Isis
> Issue Type: Improvement
> Components: Core: Runtime
> Affects Versions: 0.2.0-incubating
> Reporter: Dan Haywood
> Fix For: 0.3.1-incubating
>
>
> Currently it is the responsibility of each viewer to check whether a domain
> object has been updated prior to completing an edit.
> For example, if an object is displayed, the viewer renders the OID (usually
> in the HTML) and also caches the version of the object somewhere (either in
> the HTML, or possibly in a http session). If the user then invokes an
> action, then the viewer resolves the object and checks that the version has
> not changed.
> This ticket is to move this check into the persistor so that, when an object
> is resolved, the version is also supplied. The persistor then throws a
> concurrency check if there is a mismatch.
> The intention is for the API of the Persistor to remain unchanged, accepting
> only an Oid to resolve the object, but to use the version details that can
> now be stored in the Oid (see ISIS-245).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
