You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by "Dan Haywood (JIRA)" <ji...@apache.org> on 2015/03/12 16:34:40 UTC
[jira] [Updated] (ISIS-542) Restrict which entities a service
action is contributed to (as either a contributed action or contributed
assocation).
[ https://issues.apache.org/jira/browse/ISIS-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Haywood updated ISIS-542:
-----------------------------
Fix Version/s: (was: core-1.9.0)
core-1.10.0
> Restrict which entities a service action is contributed to (as either a contributed action or contributed assocation).
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: ISIS-542
> URL: https://issues.apache.org/jira/browse/ISIS-542
> Project: Isis
> Issue Type: New Feature
> Components: Core
> Affects Versions: core-1.2.0
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Fix For: core-1.10.0
>
>
> For example, an action
> void foo(A a, B b) { ... }
> will be contributed to both entities A and B. We might want to allow it to be contributed to one or the other.
> Suggestion is that @NotContributed annotation applies to action parameters (with current behaviour maintained for compatibility as the default for all parameters of the action):
> eg
> void foo(
> @NotContributed(As.Action) A,
> @NotContributed(As.Association) B) { ... }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)