Oh ok cool. Was that fix included in the 1.1.0 release? That's what
I'm using and I'm having problems with.
Rich
Bruno Aranda wrote:
Well, since 15 september this is already implemented in myfaces (see
MYFACES-565 http://issues.apache.org/jira/browse/MYFACES-565).
Best regards,
Bruno
2005/9/27, Richard Wallace <[EMAIL PROTECTED]>:
Hey all,
I was just trying to get a Hibernate mapped collection, a Set, displayed
on a page with a t:dataList component. Much to my chagrin I started to
get exceptions like "javax.servlet.ServletException: ServletException in
'/admin/departmentType/list.jsp': javax/servlet/jsp/jstl/sql/Result"
which I thought was really odd since I don't use any such beast in my
app, it's all Hibernate based.
I thought that maybe something was wrong with my collection mapping so
tried just doing a <h:outputText value="#{myPojo.myMappedCollection}" />
and it displayed the correct data. So I did some digging in the
tomahawk docs and it says for "supported types see JSF Spec 4.1.3." Of
course, that is a spec doesn't include sets, only Lists and ResultSets.
So I can only guess myfaces tried to map the collection to a ResultSet
and failed and so gave the not so informative message.
Looking on the list for dataTable and Hibernate messages to see how
people had coped with this I found that the t:dataTable component "can
create DataModels directly from Sets". So, what I'm wondering is why
doesn't the t:dataList support this?
That would make life so much simpler for me and probably others using
Hibernate like this. Thoughts?
Thanks,
Rich
