[
https://jira.jboss.org/jira/browse/JBSEAM-3146?page=com.atlassian.jira.pl...
]
Ryan de Laplante commented on JBSEAM-3146:
------------------------------------------
Does this mean if I have a List of entities that I'm iterating through in my view, I
won't be able to output edit and delete buttons for only the entities that the current
user is allowed to perform those operations on because the EL doesn't let me do that?
Does it take into account the entity identifier in the permission target? ex: Customer:1
means Customer.class, id=1
Allow Object... args in the hasPermission EL function
-----------------------------------------------------
Key: JBSEAM-3146
URL:
https://jira.jboss.org/jira/browse/JBSEAM-3146
Project: Seam
Issue Type: Feature Request
Components: Security
Affects Versions: 2.0.3.CR1, 2.1.0.A1
Reporter: Samuel Mendenhall
Priority: Minor
So the following is possible #{identity.hasPermission('blog', 'create',
arg1, arg2)} and the args can be accessed in the drl file, so we should also allow
#{s:hasPermission('blog', 'create', arg1, arg2)}
--
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