You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by "Dan Haywood (JIRA)" <ji...@apache.org> on 2015/04/09 10:15:12 UTC

[jira] [Updated] (ISIS-867) Domain service to automatically maintain lastUpdatedAt and lastUpdatedBy on any entity.

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

Dan Haywood updated ISIS-867:
-----------------------------
    Component/s:     (was: Add-ons - please instead raise as issues in github repo)
                 Core

> Domain service to automatically maintain lastUpdatedAt and lastUpdatedBy on any entity.
> ---------------------------------------------------------------------------------------
>
>                 Key: ISIS-867
>                 URL: https://issues.apache.org/jira/browse/ISIS-867
>             Project: Isis
>          Issue Type: New Feature
>          Components: Core
>    Affects Versions: core-1.6.0
>            Reporter: Dan Haywood
>            Assignee: Dan Haywood
>            Priority: Minor
>             Fix For: 1.11.0
>
>
> using ISIS-865.
> Define:
> interface Updateable {
>     @Programmatic
>     public void updatedBy(String userName);
>     @Programmatic
>     publc void updatedAt(DateTime dt);
> }
> Install a JDO StoreLifecycleListener on the PersistenceManager when request starts, call in preStore.
> Should double-check plays well with auditing service.  (Should be ok, since even if this listener and Isis' global listener are called in indeterminate order, even then we only hit the auditing service just prior to committing the transaction.  Until that point we are just capturing the fact that entities have been enlisted in the xactn).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)