Uploaded image for project: 'Tapestry'
  1. Tapestry
  2. TAPESTRY-208

MultiplePropertySelection should use Collection rather than List

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Blocker
    • Resolution: Fixed
    • 4.0
    • 4.0.1
    • Contrib
    • None
    • Operating System: All
      Platform: Other
    • 30703

    Description

      The MultiiplePropertySelection component would be far more useful if the
      selectedList property was a java.util.Collection rather than a java.util.List.
      I've checked the source code and there's no reason that it needs to be a
      java.util.List. In fact, I've converted it to use java.util.Collection (and
      changed the property to "value" rather than "selectedList" - personal preference
      there) and it all works perfectly.

      This is important as the most widely used collection in Hibernate is
      java.util.Set. In fact, the Hibernate team has explicitly said that they expect
      Sets comprising the majority of Hibernate collections in most apps. If I had to
      marshall/unmarshal my Sets into Lists every time I used a group of checkboxes...
      yikes!

      Attachments

        Activity

          People

            jkuhnert Jesse Kuhnert
            kwilliams@mindsharetech.net Kurtis Williams
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: