Some further reflections: WW and SPR both use ThreadLocal to store the locale of the thread's request. However, there still needs to be a shared object that can set/retrieve the local across web frameworks.
So I 100% agree with the ThreadLocal use, but it is not directly relevant to my question. That would be an implementation of the locale resolver, in which it would expose the locale in the thread for a particular framework. So if I am running with a local resolver whose implementation sets both SAF/SAF2, it would set the appropriate values for each framework. Understand? This is kind of complex for me to describe, but I hope the point is clear. Paul Hubert Rabago <[EMAIL PROTECTED]> wrote: It looks like it requires Java 5. Has there been a decision to move SAF2 to Java 5? Hubert On 6/30/06, Niall Pemberton wrote: > From memory (WW in Action) there seems to be similar concepts in > Cintoo messages that WW/SAF2 has - but I was hoping someone who knows > would comment. > > The license is Apache 2 and it looks good to me - is this something > that SAF2 would benefit from or is that area already well covered? > > http://messages.cintoo.org/ > http://www.infoq.com/news/Cintoo-Messages-1.0-i18n > http://www.theserverside.com/news/thread.tss?thread_id=41116 > > Niall > > --------------------------------------------------------------------- > 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] --------------------------------- How low will we go? Check out Yahoo! Messengers low PC-to-Phone call rates.
