[
https://issues.apache.org/jira/browse/TAPESTRY-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Menard updated TAPESTRY-1925:
-----------------------------------
Attachment: TAPESTRY-1925.patch
Updated the type coercion to work with any Collection type. Although the grid
does expect to be able to reference items by index, implying a defined
iteration order, this invariant should be held by the fact that grid wraps up
the collection as a List anyway.
I added a test that simply checks for the non-existence of an error page when a
Set is used as a grid source. There's probably a better way to test, but I'm
still getting my feet wet.
> Grid does not handle Collections, only Lists.
> ---------------------------------------------
>
> Key: TAPESTRY-1925
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1925
> Project: Tapestry
> Issue Type: Bug
> Components: Core Components
> Affects Versions: 5.0.6
> Reporter: Kevin Menard
> Priority: Minor
> Attachments: TAPESTRY-1925.patch
>
>
> Tapestry throws an exception when providing an empty collection, such as
> java.util.Collections.EMPTY_SET, to the Grid component as the source
> parameter. The message is of the form "tried to access class
> java.util.Collections$EmptySet from clas $PropertyConduit_XXX".
> It appears to be a case of not knowing which type of class to use, rather
> than just using the interface.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
