[
https://issues.apache.org/jira/browse/ISIS-830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14972529#comment-14972529
]
ASF subversion and git services commented on ISIS-830:
------------------------------------------------------
Commit c7d12e30b3685e5d982c818b49ac3d21802e43eb in isis's branch
refs/heads/master from [~danhaywood]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=c7d12e3 ]
ISIS-830: new lifecycle events following pattern of existing domain events...
... being abstract and with a Default impl, Also no-arg constructor.
This should make ISIS-803 easier to implement when we get around to it
> Wire up JDO events to publish onto our EventBus (rather than publish our own
> events).
> -------------------------------------------------------------------------------------
>
> Key: ISIS-830
> URL: https://issues.apache.org/jira/browse/ISIS-830
> Project: Isis
> Issue Type: Bug
> Components: Core
> Affects Versions: core-1.5.0
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Fix For: 1.10.0
>
>
> Specifically:
> - ObjectPersistedEvent // postCreate in JDO terminology
> - ObjectUpdatingEvent // preStore in JDO terminology
> - ObjectUpdatedEvent // postStore in JDO terminology
> - ObjectRemovingEvent // preDelete in JDO terms
> This would be a more flexible solution for many use cases than implementing
> updating() etc.... can centralize logic.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
