[
https://issues.apache.org/jira/browse/ISIS-1254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15004390#comment-15004390
]
ASF subversion and git services commented on ISIS-1254:
-------------------------------------------------------
Commit 25ce7360983c20b7760bb5064a103bc813e91bdc in isis's branch
refs/heads/master from [~danhaywood]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=25ce736 ]
ISIS-1254: adding Noop subclasses for the domain events so that the programmer
can explicitly disable event propogation if required.
> Disable action/property/collection events if set to Noop domain events
> ----------------------------------------------------------------------
>
> Key: ISIS-1254
> URL: https://issues.apache.org/jira/browse/ISIS-1254
> Project: Isis
> Issue Type: Improvement
> Components: Core
> Affects Versions: 1.10.0
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Labels: isis-2.0
> Fix For: 1.11.0
>
>
> Following the pattern introduced in ISIS-1252 for the XxxUiEvents.
> Thus, to disable an event being fired for an action, use:
> {code}
> @Action(domainEvent=ActionDomainEvent.Noop.class)
> public void someAction() { ... }
> {code}
> Note though that to avoid breaking backward compatibility the default for the
> annotation attribute is still "ActionDomainEvent.Default.class", meaning that:
> {code}
> @Action
> public void someAction() { ... }
> {code}
> *will* (still) cause an event to be fired.
> ~~~
> We will probably make Noop the default in 2.0.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
