It seems that if I specify a Locale("es") for the first invocation of a jsp,
I will get the appropriate output. Spanish Text for labels and headings.
However, if I access the same page with a different Locale("en") from
another browser, I still get the same output in Spanish.
It appears that the format applies at compile time rather than run time
even though I specify scope as "page" instead of "session", both
give same result.
I base this on trying this where I have run a Mozilla as Locale("en" ) and
on second machine accessed the same page with IE as Locale("es") or
Mozilla on second machine also as Locale("es") only.
The access from the second machine has zero latency before it sends back the page.
Is my understanding faulty?
If this behavior is correct, then this capability for internationalization
means which ever language gets compiled first wins?
(I restarted the mozilla and ie after I changed the Locales.)
<%@ page contentType="text/html" %>
<%@ taglib prefix="c" uri="http://java.sun.com/jstl/core"; %>
<%@ taglib prefix="fmt" uri="http://java.sun.com/jstl/fmt"; %>
<c:if test="${param.language == 'en'}">
<fmt:setLocale value="en" scope="page" />
</c:if>
<c:if test="${param.language == 'es'}">
<fmt:setLocale value="es" scope="page" />
</c:if>
<fmt:setBundle basename="sitetext" scope="page" />
--
To unsubscribe, e-mail: <mailto:taglibs-user-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:taglibs-user-help@;jakarta.apache.org>
