Hi Kalle,
Thank you for explaining what Tynamo Model has to offer. It certainly
looks interesting, and promises to save much time in creating CRUD heavy
apps in Tapestry. I'll give it a go on my next webapp.
For now, I think I'll simply inspect the user's permissions in the
onActivate() method
Attachments don't come through to the mailing list but so you have a table
that describes permissions for all of the entities? Obviously, visually
showing or hiding buttons on the client doesn't really enforce security but
you are right, Tynamo doesn't really offer anything for this case out of
the
Hi Basile,
Thanks for replying. Yes, I'd discovered Tynamo, but wondered whether it
might be overkill given that I'd already inherited authentication code
from the Tapestry Hotel demo app.
It wasn't clear on the Tynamo site how Tynamo acquires permissions from my
(attached) 'role' table. And if
Hi All,
The Tapestry Hotel demo app has proven a good lesson in implementing
AUTHENTICATION. Having developed a multi-user Tapestry app, I now need to
implement AUTHORISATION, but the Hotel demo app is aimed at just one user
type: visitors.
I created a role table in my Tapestry application (scre
