Question about new Permission Manager API; Seam 2.1

[chris.simons]

Seam Team,

Regarding the Permission Manager API that is new to 2.1 BETA, in the documentation it is written:

The PermissionManager component is an application-scoped Seam component that provides a number of methods for managing permissions. Before it can be used, it must be configured with a permission store (although by default it will attempt to use JpaPermissionStore if it is available). To explicitly configure a custom permission store, specify the permission-store property in components.xml.

Does this mean we could customize our permission store to, say, store an extra object - like an organization that the permission belongs to?

So, for example, something like:
listPermissions(Object target, Organization org)?

Do you think you all will have time to put together a Seam example of how to get the most out of this new API?

Thanks!

[shane.bryzak]

That paragraph means that you can create your own permission store that persists the permissions to a different type of backend other than a database, for example a file or LDAP directory.

If you want to support custom permission recipient types (other than users and roles) then I recommend that you extend JpaPermissionStore and override the appropriate methods there.  Off the top of my head, you'll need to at least implement your own updatePermissionActions() method, and possibly others too.