[
https://issues.apache.org/jira/browse/ISIS-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13994619#comment-13994619
]
ASF subversion and git services commented on ISIS-550:
------------------------------------------------------
Commit c1a259667282c21654435bcae22ee39f8e8bbefb in isis's branch
refs/heads/master from [~danhaywood]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=c1a2596 ]
ISIS-550: minor refactoring of InvocationResult
- make nested static class
- use factory methods to avoid boolean in method signature.
> 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)
