No, something else is going on here. @Persist should be specific to the user session by default. Without seeing more of your page and component class code, I can't offer any conjectures. But I've used @Persistany times with no user-bleed over so something else is definitely going on here.
Robert GATAATGCTATTTCTTTAATTTTCGAA > On Sep 15, 2014, at 5:25 PM, Boris Horvat <horvat.z.bo...@gmail.com> wrote: > > Hi all, > > I have a question and a problem that I was unable to find in tapestry > documentation. > > I have a page that has a filter component. This components basically > accepts a filter and then displays is properties. A user can modify those > properties and when it presses a button this value is set back to the > components parameter. This in returns is then propagated (since parameters > are bi-directional) back to the page that is then able to filter for > correct data. > > Now my problem is that since I have > > @Persist > @Property > private Filter filter > > on my page and once a value from component is is returned to this property > for the user1 it is also applied to the user2. > > Is this something expected? I would expect that if the value is returned > for user1 then user2 can't see this, am i wrong? > > In my FilterComponent I have > > @Parameter > private Filter filter; > > and then when a form is submitted I do something like > > filter = new Filter(selectedSections()) > > Reading a tapestry documentation I get that page only has one instance, so > does this mean that once I place something in the component's parameter it > is unable to determine in which session it should be place? > > Thanks and let me know if you need more code > > -- > Sincerely > *Boris Horvat* --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
