[jira] [Commented] (ISIS-1005) Allow users to implement an optional service to perform pre-commit processing ("ChangedObjectService")

["Dan Haywood (JIRA)" <ji...@apache.org>]

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

Dan Haywood commented on ISIS-1005:
-----------------------------------

While this isn't that difficult to implement, it might be more elegant to implement using domain events... and there is a separate ticket to generating these on lifecycle callbacks.

Gonna push this back for now, therefore; might decide we don't need it.

> Allow users to implement an optional service to perform pre-commit processing ("ChangedObjectService")
> ------------------------------------------------------------------------------------------------------
>
>                 Key: ISIS-1005
>                 URL: https://issues.apache.org/jira/browse/ISIS-1005
>             Project: Isis
>          Issue Type: New Feature
>          Components: Core
>    Affects Versions: core-1.7.0
>            Reporter: Dan Haywood
>            Assignee: Dan Haywood
>            Priority: Minor
>             Fix For: core-1.9.0
>
>
> For example, Oscar's app has this code everywhere:
>     public void updating() {
>         this.setDateUpdated(Clock.getTimeAsDateTime().toDate());
>         this.setUpdatedByUser(this.domainFactoryService.currentUserName());
>     }
> Instead, this could be done by passing all objects enlisted in the xactn (same stuff as used by audit service) to a new service.
> This should be done immediately prior to calling auditing (so that if additional objects get dirtied by the service, then they are audited also).



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