On Tue, 17 Feb 2015 17:01:15 -0200, Erich Gormann <e.gorm...@gormann.de>
wrote:
Hi all,
Hi!
thanks for your precious hints. For this time @InjectContainer is
sufficient for my needs.
Its all about self written input field components, which render behavior
is controlled by user permissions determining if a user is permitted to
read/write fields by generic/reflective checks of his permissions for
certain entities and their fields.
I suggest you to move the permission checks to services and use them in
the components. Also think about the possibility of creating mixins for
that, which are a great tool to change a component or page behavior
without changing their sources. You'd have better code in the end.
Also check tapestry-security...
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
