[
https://issues.apache.org/jira/browse/ISIS-560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Haywood resolved ISIS-560.
------------------------------
Resolution: Fixed
now fully fixed, I think.
Required/validation errors now appear correctly in the field's feedback panel,
and drop-downs render with a non-null value after a validation error elsewhere.
The partial workaround fix previously committed and in v1.3.0 has been
removed... and wasn't completely good in any case. Specifically, a regular
validation error, eg per a validateXxx() method, would still have exhibited the
reported problem.
> 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.4.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)
