DO NOT REPLY [Bug 30703] New: - MultiplePropertySelection should use Collection rather than List

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=30703>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=30703

MultiplePropertySelection should use Collection rather than List

           Summary: MultiplePropertySelection should use Collection rather
                    than List
           Product: Tapestry
           Version: unspecified
          Platform: Other
               URL: http://www.jroller.com/page/cardsharp
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Contrib
        AssignedTo: tapestry-dev@jakarta.apache.org
        ReportedBy: kwilliams@mindsharetech.net


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!

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org