[
https://issues.apache.org/jira/browse/ISIS-781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13998522#comment-13998522
]
Dan Haywood commented on ISIS-781:
----------------------------------
Related to this, Jeroen and I have been talking about maybe changing the Wicket
viewer so that it works a bit like JIRA ... only allow a single field to be
updated at a time.
If this was done, then potentially quite a lot of code in Wicket viewer might
simplify... I'm thinking that much of the current edit stuff could go and
instead use the existing code for invoking actions.
One of the side-effects of such a refactoring is that we would inherit the
ability that the result of the action/edit could be a different object.
How that relates to this is that, although it would seem that the view model
object is mutable, in fact the user would be looking at a new object that has
taken the place of the original.
> Add edit capability to view objects
> -----------------------------------
>
> Key: ISIS-781
> URL: https://issues.apache.org/jira/browse/ISIS-781
> Project: Isis
> Issue Type: Improvement
> Components: Core
> Affects Versions: core-1.4.0
> Reporter: David Tildesley
> Assignee: Dan Haywood
> Fix For: core-1.4.2
>
>
> View object should have the same capability as domain object in the viewer.
> Currently it does not support "edit". Without this capability, actions must
> be employed and state management becomes more of an issue on the server side.
> The view object should support all of the viewer specific semantics that the
> domain objects support via the viewer generation.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
