[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2029) Identity.checkEntityPermission() fails for entities mapped using orm.xml or .hbm.xml
[ http://jira.jboss.com/jira/browse/JBSEAM-2029?page=comments#action_12404318 ]
Denis Forveille commented on JBSEAM-2029:
-----------------------------------------
could this be backported to 2.0.2?
we are waiting for this since october now, it has been announced for correction in v2.0.0
then v2.0.1, then 2.0.2 and now it is corrected in v2.1.0
But there is still 150+ bug until 2.1 is GA and this is a major bug for us, ie it prevents
us to migrate to seam 2 (We aree using seam v1.2.1 in production since
the beginning of this month)
As soon as this bug is fixed in a released version, we migrate our app to seam v2
we are using POJOs with WebSphere v6.1.0.13
thanks
Identity.checkEntityPermission() fails for entities mapped using
orm.xml or .hbm.xml
------------------------------------------------------------------------------------
Key: JBSEAM-2029
URL: http://jira.jboss.com/jira/browse/JBSEAM-2029
Project: JBoss Seam
Issue Type: Bug
Components: Security
Affects Versions: 2.0.0.CR1
Reporter: Pete Muir
Assigned To: Shane Bryzak
Fix For: 2.1.0.BETA1
Entity.forClass() isn't a great way to determine the entity's Class and should be
done through PersistenceProvider
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira