[
https://issues.apache.org/jira/browse/ISIS-2794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17394374#comment-17394374
]
ASF subversion and git services commented on ISIS-2794:
-------------------------------------------------------
Commit fe8d82b3e08e8f739609f3a277e7b4824a9b87a6 in isis's branch
refs/heads/master from danhaywood
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=fe8d82b ]
ISIS-2794: fixes entity change property to access values directly
... rather than being evaluated as if a user.
This only showed up as a defect while testing with secman, where invoking with
InteractionInitiatedBy.USER results in the filter visibility check, in turn
causing a query flush. EclipseLink complains of a flush within a flush
(RepeatableWriteUnitOfWork#writeChanges). Using
InteractionInitiatedBy.FRAMEWORK is the correct approach - we always want to
emit the correct values of the property change for auditing, irrespective of
whether the end user has access to the records or not
(cherry picked from commit af246519fef7b9b2b2c2fa02883c0fb2b2ec7896)
> JPA Lifecycle events do not fire
> --------------------------------
>
> Key: ISIS-2794
> URL: https://issues.apache.org/jira/browse/ISIS-2794
> Project: Isis
> Issue Type: Bug
> Components: Isis Persistence JPA
> Affects Versions: 2.0.0-M5
> Reporter: Daniel Keir Haywood
> Assignee: Andi Huber
> Priority: Major
> Fix For: 2.0.0-M6
>
>
> see docs on Lifecycle Events here
> https://isis.apache.org/refguide/2.0.0-M5/applib-classes/events/lifecycleevent.html#section-top
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
