[
https://issues.apache.org/jira/browse/ISIS-560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13799886#comment-13799886
]
ASF subversion and git services commented on ISIS-560:
------------------------------------------------------
Commit d1142639941170f866810df5dfe96a1fc70b022d in branch refs/heads/master
from [~danhaywood]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=d114263 ]
ISIS-560: partial fix (but good enough)
rather than using Wicket's setRequired, instead just
rely on Isis' MandatoryFacet validation.
The (slightly unfortunate) side effect is that the exception appears in the
form's feedback panel,
rather than the parameters. I can live with that...
> When invoking an action, drop downs get cleared (in the UI) if there is a
> validation error, but the underlying model is set.
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: ISIS-560
> URL: https://issues.apache.org/jira/browse/ISIS-560
> Project: Isis
> Issue Type: Bug
> Components: Viewer: Wicket
> Affects Versions: viewer-wicket-1.2.0
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Fix For: viewer-wicket-1.3.0
>
>
> This allows the user to hit OK and complete the object even though it seems
> that there is no value for those drop downs.
> for example:
> ToDoItems#newToDo(...)
> leave description blank;
> the category/subcategory are blank, but can complete (so they actually have
> values)
--
This message was sent by Atlassian JIRA
(v6.1#6144)
