[
https://jira.jboss.org/jira/browse/JBSEAM-2684?page=com.atlassian.jira.pl...
]
Alex Savitsky commented on JBSEAM-2684:
---------------------------------------
So I take it that MEII is beyond any fixing? What about the suggestions from JBSEAM-1814?
Wouldn't they work here?
Anyway, disabling this piece of code is exactly what I ended up doing in all of my Seam
projects. It's good to see that I'm in line with Seam developers' line of
thinking :)
#{entityQuery.dataModel} returns empty model
--------------------------------------------
Key: JBSEAM-2684
URL:
https://jira.jboss.org/jira/browse/JBSEAM-2684
Project: Seam
Issue Type: Bug
Components: Core, Framework
Affects Versions: 2.0.1.GA
Reporter: Alex Savitsky
Assignee: Norman Richards
Priority: Critical
Fix For: 2.1.0.BETA1
Attachments: Test.zip
When referenced from a JSF dataTable, a dataModel property from a conversation-scoped
EntityQuery ALWAYS returns an empty model. The resultList property works normally, though.
Placing the EntityQuery in session scope works, too.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira