I resolved writing my own i18n-interceptor.
Firstly I try to get the locale from session, if not I look for in the
request, if not we use the ActionContext by default set up in
struts.properties.
Anyway this is not the xwork 2.1.4 behavior, who looks for locale in
session, and then ActionContext.

Can anyone give me feedback about that?

thank x for your fast answer Wes ;)


2009/7/15 Wes Wannemacher <w...@wantii.com>

> If you are not using REST or the rest plugin, you can use struts
> 2.1.7, it is not a GA release because there was a missing class in the
> rest plugin. Or, you can build 2.1.8-SNAPSHOT. We should be getting an
> xwork 2.1.5 release soon and we'll roll a struts 2.1.8 release right
> afterwards. If the vote passes, 2.1.8 will be GA.
>
> -Wes
>
> On Wed, Jul 15, 2009 at 11:31 AM, David Canos<davidca...@gmail.com> wrote:
> > hi folks
> >
> > Currently Struts 2.1.6 is working with xwork 2.1.2 which has some bugs
> > related to i18n. They are fixed in xwork 2.1.3.
> > http://jira.opensymphony.com/browse/XW-679
> >
> > I've check struts jira and i haven't seen any upgrade xwork issue.
> > It's hard to work in a i18n context while the i18n-interceptor erases the
> > action context locale.
> >
> > I don't know if there are related cons upgrading the version of xwork.
> > Should I create this on Jira?
> >
> > thankx
> >
>
>
>
> --
> Wes Wannemacher
> Author - Struts 2 In Practice
> Includes coverage of Struts 2.1, Spring, JPA, JQuery, Sitemesh and more
> http://www.manning.com/wannemacher
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
> For additional commands, e-mail: user-h...@struts.apache.org
>
>

Reply via email to