Uploaded image for project: 'Causeway'
  1. Causeway
  2. CAUSEWAY-2253

Derive ChoicesFacet from ChoicesFromFacet, remove special-case logic.

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • None
    • 2.0.0-M6
    • Viewer Wicket
    • None

    Description

      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.

      Attachments

        1. screenshot-1.png
          503 kB
          Daniel Keir Haywood

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            hobrom Andi Huber
            hobrom Andi Huber
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment