Howard, I don't quite understand how the %-notation in the descriptors at all affect the message localization. I thought all the messages generated by the services would stem from the injected Messages (or now the MessagesProxy). The % stuff in the descriptor OTOH would be used to for instance to provide localized descriptions for services and configuration points. Where is the overlap?
--knut On Tue, 25 Jan 2005 09:02:27 -0500, Howard Lewis Ship <[EMAIL PROTECTED]> wrote: > I'd like to take a crack at allowing the locale to be changed > dynamically. This would be more in keeping with HiveMind + a web > application (i.e., Tapestry), where each thread/request may want > messages localized to a different locale. > > I pretty much know how this will work: > - Registry's locale is the *default* locale > - A LocaleHolder service that stores the locale for the current thread > - A MessagesProxy > > MessagesProxy: The proxy is what's injected into services. It's > implementation will get the Locale from the LocaleHolder and ask the > Module for the concrete Messages for that locale, and redirect > implementations to that concrete Messages instance. > > The only problem is the %key syntax in the descriptors. That will > only be evaluated ONCE and in some arbitrary locale. I would propose > that the syntax be removed (or, at the very least, deprecated). > Thoughts? > > -- > Howard M. Lewis Ship > Independent J2EE / Open-Source Java Consultant > Creator, Jakarta Tapestry > Creator, Jakarta HiveMind > > Professional Tapestry training, mentoring, support > and project work. http://howardlewisship.com > > --------------------------------------------------------------------- > 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]
