Which is a potential backwards compatibility issue, not an issue with HtmlTag being able to grab a locale and render its "lang" attribute. That seems like a fairly weird use-case though.
Quoting David Graham <[EMAIL PROTECTED]>: > >Even if no requests ever get processed by ActionServlet, having HtmlTag > >just use > >RequestUtils.retrieveUserLocale will still do the right thing (i.e. return > > >a > >locale based on the Accept-Language header, or the default locale for the > >server). I don't see how that would break localization behavior. > > Because it also creates a session and stores the Locale in there. Apps may > > be relying on that object to be in the session by using the html tag. > > David > > _________________________________________________________________ > Protect your PC - get McAfee.com VirusScan Online > http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963 > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > -- Kris Schneider <mailto:[EMAIL PROTECTED]> D.O.Tech <http://www.dotech.com/> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
