[
https://issues.apache.org/jira/browse/ISIS-800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14029585#comment-14029585
]
ASF subversion and git services commented on ISIS-800:
------------------------------------------------------
Commit a2916d7c983288ede95149a0a2fd61c0585ef4a4 in isis's branch
refs/heads/master from [~danhaywood]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=a2916d7 ]
ISIS-800: wizard now implemented.
More or less there. One minor issue is that can't disable reference panels
dynamically; wanted to have a ToDoItemWizard#subcategory that would show,
disabled, if populated by the 'updateCategory' action.
But this is a niche use case; I think what is there is probably good enough for
most.
> Wizard-like form for Wicket viewer
> ----------------------------------
>
> Key: ISIS-800
> URL: https://issues.apache.org/jira/browse/ISIS-800
> Project: Isis
> Issue Type: New Feature
> Components: Core, Viewer: Wicket
> Affects Versions: viewer-wicket-1.5.0, core-1.5.0
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Priority: Minor
> Fix For: viewer-wicket-1.6.0, core-1.6.0
>
>
> Erik Hair on [email protected]:
> Is it in some way possible to create a wizard like form or open an action
> with an action? I tried to return a not yet persisted object from an action
> and hoped I could edit some properties and add some elements to collections
> of the object before persisting it to the database...
> ~~~~~~
> Dan:
> Short answer is that we don't really (properly) support this. And we should.
> I agree that @NotPersistable is confusing and its not clear what to use; the
> right solution would be to implement a view model (currently: implement the
> ViewModel interface), and then - optionally - write a custom ComponentFactory
> for the Wicket viewer to render the wizard appropriately.
> But the snag even with the above is that (currently) view models are
> immutable; they support actions but their properties cannot be edited.
> I can see the way forward on this; I don't think it's difficult, but it will
> require a change in core and probably the wicket viewer also.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
