[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3446) Update documentation for new Entity Security with JPA behaviour

Pete Muir (JIRA) jira-events at lists.jboss.org
Sat Oct 4 19:46:21 EDT 2008


     [ https://jira.jboss.org/jira/browse/JBSEAM-3446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pete Muir updated JBSEAM-3446:
------------------------------

       Issue Type: Task  (was: Bug)
    Fix Version/s: 2.1.0.GA
         Assignee: Shane Bryzak
         Priority: Minor  (was: Major)


> 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

        



More information about the seam-issues mailing list