I found that in my case my code was working fine with following versions of
hibernate:
org.hibernate
hibernate
3.2.4.ga
org.hibernate
hibernate-entitymanager
3.3.1.ga
When I added acegi:
org.acegisecurity
acegi-security
1.0.5
I started seeing the problem. Apparenetly acegi uses an older version of
hibernate which has this problem.
The workaround was to use a fully qualified class name in the query (thanks to
Aleksei Valikov for suggesting that).
Note that the bugon this issue:
http://jira.jboss.com/jira/browse/JBSEAM-570?page=worklog&decorator=printable
was closed with no comment which does not help folks running into the problem.
Thanks.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4092149#4092149
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4092149
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user
