[ https://issues.apache.org/jira/browse/ISIS-2877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17432249#comment-17432249 ]
ASF subversion and git services commented on ISIS-2877: ------------------------------------------------------- Commit e96dc9bf0a7e3b0ed0aa1661a1e8f56e6c4a6583 in isis's branch refs/heads/2877-compound.value.types from Andi Huber [ https://gitbox.apache.org/repos/asf?p=isis.git;h=e96dc9b ] ISIS-2877: parameter support actions are special - don't render a result page (WIP) - don't trigger domain events or publishing - circumvent rule checking > Support for Value Type Composition > ---------------------------------- > > Key: ISIS-2877 > URL: https://issues.apache.org/jira/browse/ISIS-2877 > Project: Isis > Issue Type: Improvement > Components: Isis Core, Isis Viewer Wicket > Reporter: Andi Huber > Assignee: Andi Huber > Priority: Major > Fix For: 2.0.0-M7 > > > It should be sufficient to specify a value-type say CalendarEvent to be a > compound of already existing value-types (date, time, duration, title, notes) > = base-types, without the need of further integration with the UI. > Given all the required information via a ValueSemanticsProvider, the > framework should be smart enough to handle: > * property update dialogs (optional - for that to work, we might just > require an update action that takes all required base-types as arguments) > * action dialogs (eg. just embed the base-types) > * table columns (eg. just embed the base-types, or as an alternative use > value semantics 'rendering') -- This message was sent by Atlassian Jira (v8.3.4#803005)