[jira] [Commented] (ISIS-542) Restrict which entities a service action is contributed to (as either a contributed action or contributed assocation).

[Jeroen van der Wal (JIRA)]

    [ 
https://issues.apache.org/jira/browse/ISIS-542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14738919#comment-14738919
 ] 

Jeroen van der Wal commented on ISIS-542:
-----------------------------------------

+2 from Jeroen & Johan ;-)

Since we're using contributions more and more we like to start working on this 
issue. We suggest extending @ParameterLayout with a contributed parameter.

Something like this:

public class PartyContributions{
    public void moveFundsTo(
        final Party fromParty,
        final @ParameterLayout(contributed = Contributed.Never) Party toParty) {
            ....
        }
}

> 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: 1.12.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)