Thank you Dan for your excellent recap and proposal. I have one more thought: since @ViewModel and @DomainObject(nature=UI_VIEW) are the same concepts it might be more intuitive to use @DomainObject(nature=VIEW_MODEL)
On Sat, Jan 3, 2015 at 1:27 PM, Dan Haywood <[email protected]> wrote: > On 3 January 2015 at 12:16, GESCONSULTOR <[email protected]> wrote: > > > > > > > Just some thoughts. i don't see compatible an option called "UI_VIEW" in > a > > "domain" object. > > > > Perhaps just "VIEW"? > > > > > The reason I'm suggesting UI_VIEW is that (as you stated yourself) "VIEW" > is overloaded.... it might refer to a UI/app-layer view on top of the > problem domain, or it might refer to a proxy on top of some externally > managed entity. > > > > > If that's the case, what would differentiate it from a @ViewModel? > > > > > > Nothing; it's the same concept. > > In other words, my proposal is that we allow a UI-layer view model to be > expressed either as @ViewModel or as @DomainObject(nature=UI_VIEW). > > Both are supported out-of-the-box in Isis, but we expect that any given > project/developer will only use one or the other. It's a matter of > personal preference. > > Then, the new Isis Maven plugin plus metamodel validators can be used to > enforce this preference in the build pipeline. > > Hope that helps clarify the proposal > > Dan >
