If I understand you right, you want data (in this case the locale) to be stored at a scope higher than session, because it involves more webapps, but less than "application", because it is user (session) specific. Far as I know, there is no such scope defined. Maybe you can simulate this behaviour by adding the webapps together as modules of one encapsulating webapp, and store the locale in the session scope for the encapsulating webapp? Just an idea.
Jeroen > -----Oorspronkelijk bericht----- > Van: Jan Normann Nielsen [mailto:[EMAIL PROTECTED] > Verzonden: maandag 17 mei 2004 14:31 > Aan: Struts Users Mailing List > Onderwerp: Re: R: Sharing what I've learned: locale switching > > Andrea M. wrote: > > >Hi Jan > >What do you mean with "sharing user chosen locale"? > >Does your user access thru a common login application? > >If it's something like that, then you might share your Locale putting it > in > >session > >Session.setAttribute("myLocale", myLocale); > > > >Then retrieving it in the other applications with > >(Locale)request.getSession().getAttribute("myLocale); > > > >This usually works pretty well since Session is a serializable object. > >Not sure it would work in a clustered environment though > > > > > I have no problem putting the locale in the session if it wasn't for the > fact that each deployed web application has its own session handler, so > the locale is not shared between web applications. It this possible? > > Best regards, > Jan Nielsen > > --------------------------------------------------------------------- > 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]
