[
https://issues.apache.org/jira/browse/ISIS-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13994623#comment-13994623
]
ASF subversion and git services commented on ISIS-550:
------------------------------------------------------
Commit 5f15fa74cb61ddd21040b9033af74e84cc838214 in isis's branch
refs/heads/master from [~danhaywood]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=5f15fa7 ]
ISIS-550: refactored DomainObjectInvocationHandler and ImperativeFacets
Previously DOIH (that the WrapperFactory's wrapper proxies delegates to) was
hard-coded to search for particular ImperativeFacets and act accordingly.
This has now been abstracted out into the concept of an Intent (enum defined in
ImperativeFacet) which allows more precise control as to how to interpret any
given method that is invoked through the wrapper .
In addition:
- split PostPropertyChangedEventFacet into two:
PostsPropertyChangedEventSetterFacet and PostsPropertyChangedEventClearFacet,
so that both can wrap an underlying *FacetViaMethod.
This pattern is then consistent with the PostsCollectionFacets (though not
the PostsActionInvokedEventFacet)
- (related to ISIS-769), have moved the setup of request-scoped services from
the PersistenceSession#open and into IsisTransactionManager#startTransaction.
This is for symmetry with the #endTransaction.
> 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)
