[ https://issues.apache.org/jira/browse/DELTASPIKE-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16905065#comment-16905065 ]
Thomas Andraschko commented on DELTASPIKE-1384: ----------------------------------------------- https://github.com/apache/deltaspike/pull/93 > 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)