The request_local functionality is part of the Interceptor stack, and
so the request has to go through as a Struts Action. An ordinary JSP
isn't processed as a Action, any more than a HTML page would be.

Otherwise, once the locale is changed, it should stick as part of the
session. The two things that could defeat the locale would be losing
the session, or resetting it with another link. The MailReader example
is localized, so the first question would be whether that example
works on the target system or not.

-- HTH, Ted
<http://www.husted.com/ted/blog/>


On Nov 30, 2007 9:42 AM, Andrew Stepanenko <[EMAIL PROTECTED]> wrote:
> I have something similar like this. If I append request_locale=uk to a
> JSP there is no effect, and still the default locale from
> struts.properties is displayed. If I append request_locale=uk to an
> .action link, than the locale is changed, but only for this current
> HTTP request. Next clicks on links cause the default locale to be
> displayed again.
>
> Did anyone experience anything similar to the above?
>
> Thanks,
> Andrew
>
>
> On Nov 30, 2007 4:34 PM, giglian <[EMAIL PROTECTED]> wrote:
> >
> > my web app display message in jsp page ( using <s:text name="......."/>)
> > always in one language.
> > I have two localization files (package.properties and package_it.properties
> > in the same folder), and I always get the messages in Italian language even
> > if the client language is English (en-us).
> > Rather in my production environment (O.S. Windows Server 2003 English), the
> > same web app always displaying the same messages in English language even if
> > the client language (IE 6) is Italian (it).
> > I tried to do everythings but with any result.
> > Please help me to solve this issue.
> > Thanks in advance for your time.
> >
> > Andrea

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to