[
https://issues.apache.org/jira/browse/ISIS-3084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17560946#comment-17560946
]
ASF subversion and git services commented on ISIS-3084:
-------------------------------------------------------
Commit 6dd943862d1edaee8637ae769683b670bf763d2e in isis's branch
refs/heads/master from Andi Huber
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=6dd943862d ]
ISIS-3084: Remove direct Collections modification endpoints from RO
> [RO/Wrapper] Remove the Notion of mutable Collections (with associated Events)
> ------------------------------------------------------------------------------
>
> Key: ISIS-3084
> URL: https://issues.apache.org/jira/browse/ISIS-3084
> Project: Isis
> Issue Type: Improvement
> Components: Isis Core, Isis Viewer RO
> Reporter: Andi Huber
> Assignee: Andi Huber
> Priority: Major
> Fix For: 2.0.0-M8
>
>
> Quoting Dan:
> Collection changes have historically been supported, but they are mostly
> deprecated/removed for v2. Part of the rationale for that is the difficulty
> of defining what an "execution" would mean for them.
> Historically there was "addToXxx" and "removeFromXxx" prefixes for a
> collection "getXxx". When we moved to building web UIs, this was somewhat
> difficult to express. In any case, it also makes sense to limit which
> objects can be added to or removed from a collection.
> Thus, one would make the collection read only and then define actions that
> encapsulated the required business logic.
> [... as] this stuff is only semi-deprecated, because you'll see that the RO
> viewer does define endpoints representing mutable collections, and the
> WrapperFactory also supports the notion. All this code could be removed [...]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
