[jira] [Commented] (ISIS-550) Complete the guava EventBus support with new annotations

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

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

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

Commit 548cb14ff648c0099036a2e777b318e1f4d3daa0 in isis's branch refs/heads/ISIS-550 from [~danhaywood]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=548cb14 ]

ISIS-550: starting on PostsAddedToCollectionEvent

This is Oscar's patch attached to ISIS-550 ticket on 6-may-2014.


> Complete the guava EventBus support with new annotations
> --------------------------------------------------------
>
>                 Key: ISIS-550
>                 URL: https://issues.apache.org/jira/browse/ISIS-550
>             Project: Isis
>          Issue Type: New Feature
>          Components: Core
>    Affects Versions: core-1.2.0
>            Reporter: Dan Haywood
>            Assignee: Dan Haywood
>             Fix For: core-1.4.2
>
>         Attachments: patch-GC-550.diff
>
>
> A while back I introduced support for the Guava eventbus in the domain model, and introduced the @PostsPropertyChangedEvent.  This will cause the old/new values of the change to be sent to any (domain service) subscriber.
> This work is incomplete though.  We ought also to have some additional annotations for other significant actions.  I'm thinking:
> - @PostsCollectionAddedToEvent
> - @PostsCollectionRemovedFromEvent
> - @PostsActionInvokedEvent
> - @PostsObjectPersistedEvent
> - @PostsObjectDeletedEvent.  
> I think that this would probably cover most of the lifecycle events you would want to handle; it'd also be a pretty useful way of decoupling a domain model (without the overhead of publishing via Isis' PublishingService API).



--
This message was sent by Atlassian JIRA
(v6.2#6252)