You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltaspike.apache.org by "Thomas Andraschko (JIRA)" <ji...@apache.org> on 2019/08/12 10:57:00 UTC

[jira] [Resolved] (DELTASPIKE-1384) Introduce @CreatedBy

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

Thomas Andraschko resolved DELTASPIKE-1384.
-------------------------------------------
    Resolution: Fixed

> Introduce @CreatedBy
> --------------------
>
>                 Key: DELTASPIKE-1384
>                 URL: https://issues.apache.org/jira/browse/DELTASPIKE-1384
>             Project: DeltaSpike
>          Issue Type: Improvement
>          Components: Data-Module
>            Reporter: Thomas Andraschko
>            Priority: Major
>             Fix For: 1.9.1
>
>
> From the mailing list:
> Hi all,
> I recently stumbled over the auditing capabilities of DeltaSpike Data
> module. I like them a lot, but I noticed that there is @CreatedOn and
> @ModifiedOn for the timestamps, but only @ModifiedBy. I noticed, that
> @ModifiedBy is set on creation (differently to @ModifiedOn), but it is
> not preserved on updates (obviously).
> I would like to have @CreatedBy as well - analog to how the 2 timestamp
> annotations work. That includes adding a setOnCreate property to
> @ModifiedBy.
> I'm happy to work on a patch for this, but before that I'd like to put
> up for discussion the following:
> * @ModifiedOn is (by default) not set on creation, @ModifiedBy is. So to
> preserve backwards compatibility the 2 would have different default
> behavior.
> Any thoughts on that?
> Cheers,
> Juri



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)