[ http://issues.apache.org/jira/browse/MYFACES-286?page=all ]
Bruno Aranda closed MYFACES-286:
--------------------------------
Fix Version: 1.0.10m10
Resolution: Won't Fix
Although it may be an unpopular decision, I think we should do only what it is
specified in this case, because this will make transparent a migration from
myfaces to RI. If someone used Set in myfaces, he/she should change that if
migrated to RI.
The Spec (section 4.1.3.2, p4-8) states:
<<However, a DataModel wrapper instance must automatically be provided by the
JSF
implementation if the current value is of one of the following types:
- java.util.List
- Array of java.util.Object
- java.sql.ResultSet (which therefore also supports javax.sql.RowSet)
- javax.servlet.jsp.jstl.sql.Result
- Any other Java object is wrapped by a DataModel instance with a single row.>>
> x:datatable doesn't support Set
> -------------------------------
>
> Key: MYFACES-286
> URL: http://issues.apache.org/jira/browse/MYFACES-286
> Project: MyFaces
> Type: Bug
> Versions: 1.0.10m10
> Reporter: Low Heng Sin
> Assignee: Bruno Aranda
> Fix For: 1.0.10m10
> Attachments: HtmlDataTableHack.patch
>
> x:datatable doesn't support the java.util.Set interface. This is caused by
> the overriden createDataModel method in HtmlDatatableHack doesn't handle
> generic java collection interface ( It does in UIData ).
--
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
