You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2020/01/05 17:26:00 UTC

[jira] [Commented] (ISIS-2253) Actions fail MM Validation when associated

    [ https://issues.apache.org/jira/browse/ISIS-2253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17008362#comment-17008362 ] 

ASF subversion and git services commented on ISIS-2253:
-------------------------------------------------------

Commit 61b7d6b860c6d08c270f6077ac3bc898fe9e07e2 in isis's branch refs/heads/master from Andi Huber
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=61b7d6b ]

ISIS-2253: minor simplifications

> Actions fail MM Validation when associated
> ------------------------------------------
>
>                 Key: ISIS-2253
>                 URL: https://issues.apache.org/jira/browse/ISIS-2253
>             Project: Isis
>          Issue Type: Bug
>          Components: Core, Core: Viewer: Wicket
>            Reporter: Andi Huber
>            Assignee: Andi Huber
>            Priority: Major
>             Fix For: 2.0.0
>
>
> In fact, this is a case of two wrongs not quite making a right. There's a nasty hack in that it is the Wicket viewer that knows how to populate the choices for the parameter, and it does this without looking for an autoComplete or choices facet ; it just picks up the checked items of the associated collection.
>  The short term solution to fix DemoApp is just to update that metamodel validator to also take into account any AssociatedWithFacet.
>  The long term "correct" solution is a new facet factory that will derive a ChoicesFacet from the AssociatedWithFacet, and then to remove the special case logic from the Wicket viewer.
> That would then make the validator correct as it is now written.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)