re: transient collections, I have a possible solution for that. I recently introduced the DomainObjectList as a view model around arbitrary object collections. This is used by the RO viewer if a certain Accep-Header is specified, and removes the need for an RO client to have to handle a special case of standalone lists... instead everything returned by the RO API is always just a domain object (either entity or view model).
Perhaps in v2 we could push this idea deeper into the framework, so that any action that returns a collection is automatically wrapped in a DomainObjectList. The only snag I can see is programmatic calls through a wrapper (ie wrapped target object by WrapperFactory); the caller would expect a collection so the wrapper would need to extract from the DomainObjectList that holds it). On Wed, 12 Sep 2018, 16:55 Andi Huber, <notificati...@github.com> wrote: > @andi-huber <https://github.com/andi-huber> requested your review on: > apache/isis#123 <https://github.com/apache/isis/pull/123> Isis 1976 > rethink object adapters. > > — > You are receiving this because your review was requested. > > > Reply to this email directly, view it on GitHub > <https://github.com/apache/isis/pull/123#event-1841541090>, or mute the > thread > <https://github.com/notifications/unsubscribe-auth/AA-9yaRqVWnsmyQ2OCPynfM1XQ8vwsW0ks5uaS5agaJpZM4Wlrbw> > . > [ Full content available at: https://github.com/apache/isis/pull/123 ] This message was relayed via gitbox.apache.org for devnull@infra.apache.org
