It would help if you answered Thiago's questions. On 6 Oct 2014, at 5:12 am, Name Surname <wintertime0...@outlook.com> wrote:
> Thanks Thiago a lot on your mention! :) And thank you Lava on your work > regarding Observe component. > OK, it should work like this way, however it doesn't. I pull all from db to > listaTiketa arrayList, and from there it should behave like filtering from > jvm, since it's listaTiketa filled with all the tickets pulled from DB. > However, this can't work. Maybe I should declare listaTiketa with @persist so > to store on start everything from db and manipulate with it? I would like to > hear your opinion regarding it. > >> Date: Sat, 4 Oct 2014 09:55:07 +0100 >> Subject: RE: Stitch observe component applied over DB entities >> From: lance.j...@googlemail.com >> To: users@tapestry.apache.org >> >> The stitch example you've referenced does exactly what you want from what I >> can see. Apart from filtering in the db query (rather than in the jvm) it's >> all there. > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org