On Tue, Mar 18, 2014 at 10:02 AM, Dmitriy Vsekhvalnov < dvsekhval...@gmail.com> wrote:
> Kalle, do you mean it works only for traversing object graph? (sorry i > probably have to check myself before asking stupid questions). > Yes. It checks that a security principal of the currently executing subject matches with the id of the configured association (e.g. "owner") of the entity that's being operated on. Kalle > On Tue, Mar 18, 2014 at 8:31 PM, Kalle Korhonen > <kalle.o.korho...@gmail.com>wrote: > > > On Tue, Mar 18, 2014 at 7:43 AM, Dmitriy Vsekhvalnov < > > dvsekhval...@gmail.com > > > wrote: > > > > > is tapestry-security-jpa provides filtering data support? E.g. when i > > > execute .list() operation with query can it apply filter based on owner > > or > > > other rule? > > > like Hibernate filters? > > > > > > > No, this is meant strictly for securing data instances based on their > > association with the currently executing subject. There's no concept for > > filtering and there's no need to explicitly apply a filter based on > owner. > > > > Kalle > > > > > > > > > On Tue, Mar 18, 2014 at 5:08 PM, Ken in Nashua <kcola...@live.com> > > wrote: > > > > > > > Thanks Kalle, thats the answer I was seeking. > > > > > > > > Which persistence Service wold in order to ORM o MySQL ? > > > > > > > > Does that JPA construct do it itself somehow like javabeans or can I > > use > > > > the existing hibernate persistence service that comes with your > suite ? > > > > > > > > Thanks for the solution, appreciate that. > > > > Ken > > > > > > > > > >
