[ http://www.stripesframework.org/jira/browse/STS-749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ben Gunter updated STS-749: --------------------------- Fix Version/s: (was: Release 1.5.5) Since there seems to be a good bit of disagreement on the exact nature of the problem and since Christian's comments indicate this has something to do with the layout tags, I'm unscheduling this issue until we can get more information on exactly what's happening. The layout tags have undergone major changes since 1.5.3, and a lot of problems related to the old layout code have been fixed as a side effect of those changes. I would like to know if this is still a problem in 1.5.4 and the soon-to-be-released 1.5.5. > <fmt:formatDate /> wrong locale when using Layouts and custom LocalePicker > -------------------------------------------------------------------------- > > Key: STS-749 > URL: http://www.stripesframework.org/jira/browse/STS-749 > Project: Stripes > Issue Type: Bug > Components: Formatting > Environment: Win 7, Java 6, Resin 3.1.10 > Reporter: Christian Yttesen > > Reading the Stripes documentation about localization: > << > Secondly, you should rarely have a need to use the <fmt:setLocale.../> tag. > Because of Stripes' strategy of using a filter and a request wrapper, all > components in your application, including the JSTL tags, will always get the > right locale when they call request.getLocale(). > >> > Using the Layout template mechanism I cannot get <fmt:formatDate /> to use > the locale returned by my custom LocalePicker - it seems to always use the > browsers preferred locale. > If I include <fmt:setLocale value="${pageContext.request.locale}" /> on my > page it works fine. But reading the above documentation makes me wonder why > thats required? -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira ------------------------------------------------------------------------------ Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Stripes-development mailing list Stripes-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/stripes-development