Yes, I do, but only for logged in users. I read on the Tapestry website or docs, that the visit should be created as late as possible and that it is bad practise to create it for every visitor...
The example was maybe not quite good...as most roles are only known after login... > --- Urspr�ngliche Nachricht --- > Von: "Hensley, Richard" <[EMAIL PROTECTED]> > An: "Tapestry users" <[email protected]> > Betreff: RE: ThreadLocal example pleeeeease! > Datum: Tue, 31 May 2005 13:19:35 -0400 > > Sarah, > > Do you have a Visit? > > This sounds like session specific information that is normally stored in > the > Visit. I would consider constructing a method in my Visit that knows how > to > navigate the global object correctly. > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, May 31, 2005 9:49 AM > To: [email protected] > Subject: ThreadLocal example pleeeeease! > > Could anyone of you post a quick example how to correctly > use ThreadLocal within a Tapestry page and a Tapestry component? > > My global object currently is a map of group data and the key is the group > key. Different page getter methods need parameters that is derived from > the > group data ..... > > E.g. administrator is on: > > admin.domain.com > > moderators on moderators.domain.com > > users on www.domain.com > > guests on guests.domain.com > > a method that is called getMenuOptions should retrieve the menu options. > > The menu can contain 4 different kinds of data. So it is all in a global > map > and the database is only queried once. > > But this leads to having to parse the map all the time > the method getMenuOptions or any other method that will indirectly call > it, > is called. > > and I want to sort of shift it into some sort of local variables to be > able > to directly access it. > > Is that possible using ThreadLocal ? If so, how ? > > Thank you! > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
