[
https://issues.apache.org/jira/browse/ISIS-3239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andi Huber updated ISIS-3239:
-----------------------------
Fix Version/s: 2.0.0-RC1
(was: 2.0.0-M9)
> To avoid leaky abstractions, a mixin collection should only ever emit
> collection domain events; ditto for properties.
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: ISIS-3239
> URL: https://issues.apache.org/jira/browse/ISIS-3239
> Project: Isis
> Issue Type: Improvement
> Affects Versions: 2.0.0-M8
> Reporter: Daniel Keir Haywood
> Assignee: Daniel Keir Haywood
> Priority: Minor
> Fix For: 2.0.0-RC1
>
>
> For mixins, currently the ActionInvocationFacetForDomainEventAbstract , which
> invokes the action and emits events, only ever emits an ActionDomainEvent for
> all types of mixins.
> But it doesn't look at the @Action, @Property or @Collection annotations on
> the class.
> Instead, it should first look at the class level if on of those annotations
> defines an domain event and when it doesn't then look at the method level.
> NB: this takes care of executing, executed ... think there will be some other
> code impacted for hide, disable, validate.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
