s:hasPermission - how to avoid multiple DB hits ?

[kipod]

Hi all,

I am using Seam's security mechanism (with the default jpaPermissionStore).
I have a lot of s:hasPermissions all over the place, and lots of ajax too.
This results in a ton of DB queries made by the PermissionManager, finding out if the user has the proper permissions - on every little button click...

Is there a way to avoid these excessive DB hits ?
My intention would be: Get the user's permissions and store them on the conversation (or even session), and stop re-querying them all the time (!)

Thanks!

[swd847]

You could try using the second level cache / query cache.

Otherwise I don't know. Personally I user a custom permission manager that caches the results in session scope so I am not very familiar with jpaPermissionStore. Perhaps you could create a session scoped component that wraps its functionality but caches the results of permission lookups?

[kipod]

Thank you! I will try to do it with a second level cache first.

[nico.ben]

Hi Jarder,
have you tried with a second level cache? Was it succesful?
I have the same problem with a lot of db hits.

Bye,
Nicola