[ http://issues.apache.org/jira/browse/TAPESTRY-208?page=all ]
Jesse Kuhnert updated TAPESTRY-208:
-----------------------------------
Bugzilla Id: (was: 30703)
Fix Version: 4.0.1
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!
was:
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!
Version: 4.0
(was: unspecified)
Environment:
Operating System: All
Platform: Other
was:
Operating System: All
Platform: Other
Priority: Blocker
> MultiplePropertySelection should use Collection rather than List
> ----------------------------------------------------------------
>
> Key: TAPESTRY-208
> URL: http://issues.apache.org/jira/browse/TAPESTRY-208
> Project: Tapestry
> Type: Bug
> Components: Contrib
> Versions: 4.0
> Environment: Operating System: All
> Platform: Other
> Reporter: Kurtis Williams
> Assignee: Jesse Kuhnert
> Priority: Blocker
> Fix For: 4.0.1
>
> 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!
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
