[
https://issues.apache.org/jira/browse/ISIS-2794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17394350#comment-17394350
]
ASF subversion and git services commented on ISIS-2794:
-------------------------------------------------------
Commit af246519fef7b9b2b2c2fa02883c0fb2b2ec7896 in isis's branch
refs/heads/ISIS-2728 from danhaywood
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=af24651 ]
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
> 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)
