You could put an interceptor on your services if you wish.
-----Original Message-----
From: Andreas Bulling [mailto:[EMAIL PROTECTED] On Behalf Of
Andreas Bulling
Sent: Tuesday, May 16, 2006 11:57 AM
To: Tapestry users
Subject: Re: Best pratice - CRUD Security - Tapestry 4.0
On 16. Mai 2006 - 10:45:45, Brian K. Wallace wrote:
| This is where I stick with ACEGI being unobtrusive. Not discounting any
| other method of doing it at all, but I found that with ACEGI I add a
| hook into "login/logout" pages and there's no other intrusion into my
| Tapestry applications outside the configuration file (aka: no
| "isUserInRole("...")" of any kind.
But how is further access for example to the database checked?
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
