[
https://jira.jboss.org/jira/browse/JBSEAM-3446?page=com.atlassian.jira.pl...
]
Shane Bryzak closed JBSEAM-3446.
--------------------------------
Resolution: Done
The example in the security chapter has already been updated to reflect this, however the
wording in the paragraph describing this was outdated. I've now updated it to
describe the new way that entity permission checks are performed in 2.1.0.
Update documentation for new Entity Security with JPA behaviour
---------------------------------------------------------------
Key: JBSEAM-3446
URL:
https://jira.jboss.org/jira/browse/JBSEAM-3446
Project: Seam
Issue Type: Task
Components: Documentation Issues
Affects Versions: 2.1.0.BETA1
Reporter: Mike Pettypiece
Assignee: Shane Bryzak
Priority: Minor
Fix For: 2.1.0.GA
I've noticed that the behaviour of Entity security with JPA has changed in Seam 2.1.
Previously in Seam 2.0 the following Rule could be used:
rule CheckUserPermission
when
c: PermissionCheck( target == "user" )
Role( name == "admin" )
then
c.grant();
end;
However in Seam 2.1 "target" is the actual entity instance rather than the Seam
component name of the entity so the rule needs to be updated as follows:
rule CheckUserPermission
when
user: User()
c: PermissionCheck( target == user )
Role( name == "admin" )
then
c.grant();
end;
The documentation should be updated to note this.
--
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