[jira] [Commented] (ISIS-830) Wire up JDO events to publish onto our EventBus (rather than publish our own events).

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ISIS-830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14972525#comment-14972525 ] 

ASF subversion and git services commented on ISIS-830:
------------------------------------------------------

Commit e5a1faa8e07c6f617223811b9490f0074b4825fa in isis's branch refs/heads/master from [~danhaywood]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=e5a1faa ]

ISIS-830: introduced new ObjectXxxEvent into applib, also AbstractLifecycleEvent superclass, updated PersistenceSession to call these events.

also:
- fixed toString for AbstractDomainEvent
- factored out internal interfaces for the interactions between:
  - PersistenceSession and IsisLifecycleListener2
  - PersistenceSession and IsisTransactionManager
  - PersistenceSession and PersistenceQueryProcessorAbstract implementations


> 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)