1) Can't figure out a way. Maybe extending JPAPermissionStore (wich implements PermissionStore), but PermissionStore accepts just Permission on his interface and I have my own defined permission class. Any ideas?
2) Seems now it's possible (https://jira.jboss.org/jira/browse/JBSEAM-3664). I'll try this out when playing with 2.1.2.
1) Something doesn't make sense to me. Why I'm able to define my own Permission class if I'm not able to persist, neither query eventual fields (ex. company, creationDate, ... etc)?
Assuming that you are storing the company ID in session scope, you should just need to extend JpaIdentityStore and include the session-scoped company ID in any queries and entity updates. I think that you should only need to override the createPermissionQuery() and updatePermissionActions() methods.
I think you meant JpaPermissionStore, right?
extend JpaPermissionStoreyou meant add the new class to Seam package or just add it to my project?
1) I've been trying to extend JpaPermissionStore inside my projetct, but it was not possible because all properties and some methods were made private.
2) I've also tried to copy the content of JpaPermissionStore inside a new class (that it's worse than 1!!) and got problems wit ActionSet class (also not visible).
Hi Shane, Andre,
I ran into the same issue of not being able to extend JpaPermissionStore for the reasons mentioned above. Are there any workarounds to resolve this problem.