This is an automated email from the ASF dual-hosted git repository.
ahuber pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/isis.git
The following commit(s) were added to refs/heads/master by this push:
new 016182a491 ISIS-3084: mignotes for 'Remove the Notion of mutable
Collections'
016182a491 is described below
commit 016182a4910fbdeba0915fa282d5a1ad44697e8e
Author: andi-huber <[email protected]>
AuthorDate: Sat Jul 2 08:43:40 2022 +0200
ISIS-3084: mignotes for 'Remove the Notion of mutable Collections'
---
.../modules/ROOT/pages/2022/2.0.0-M8/mignotes.adoc | 23 ++++++++++++++++++++++
1 file changed, 23 insertions(+)
diff --git
a/antora/components/relnotes/modules/ROOT/pages/2022/2.0.0-M8/mignotes.adoc
b/antora/components/relnotes/modules/ROOT/pages/2022/2.0.0-M8/mignotes.adoc
index 4769687770..d5292f9490 100644
--- a/antora/components/relnotes/modules/ROOT/pages/2022/2.0.0-M8/mignotes.adoc
+++ b/antora/components/relnotes/modules/ROOT/pages/2022/2.0.0-M8/mignotes.adoc
@@ -14,6 +14,29 @@
| previously
| new
+| For _Domain Objects_ we had support for (direct) _Collection_ modification
(`addTo`, `removeFrom`).
+
+As this is part of _Restful Object Specification 1.0_, it was implemented for
the _RO Viewer_ and also the _WrapperFactory_.
+
+Specifically REST endpoints (removed):
+----
+DomainObjectResource
+ addToSet(...)
+ addToList(...)
+ removeFromCollection(...)
+----
+Events (removed)
+----
+CollectionAddToEvent
+CollectionRemoveFromEvent
+----
+| Has been removed without replacement. (An updated _Restful Object
Specification 2.0_ is in preparation.)
+
+It has proven difficulty to define what an "execution" would mean for
_Collection_ changes, hence we finally removed that notion.
+
+In some situations it however 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
encapsulate the required business logic.
+
| `@DomainService.logicalTypeName` deprecated for removal
| use `@Named` or any other semantics supported by Spring
+
