After further investigation, I don't see this is being done (at least in
the 1.1 release - I have not investigated further)
This is a straight forward fix. All I did to resolve this was extend
the processLocale method in my request processor as follows:
---
protected void processLocale(HttpServletRequest request,
HttpServletResponse response)
{
super.processLocale(request, response);
// Message Resources
MessageResources msgResources = (MessageResources)
request.getAttribute(Globals.MESSAGES_KEY);
if ((msgResources != null)
&& (msgResources.getConfig() != null))
{
Config.set(request, Config.FMT_LOCALIZATION_CONTEXT,
msgResources.getConfig());
}
}
---
Note: that I use the core "javax.servlet.jsp.jstl.core.Config" class.
However, this adds a dependency on the jstl jar itself. For my project
this was acceptable, but for Struts this probably isn't acceptable (yet
at least). Instead you could easily just set the
msgResources.getConfig() value as a request attribute under the key:
"javax.servlet.jsp.jstl.fmt.localizationContext.request"
That is basically what that set does.
This should be standard behavior of the default request processor. (If
not already.)
- Mike
On Thu, 2004-10-07 at 14:28, Mike Stanley wrote:
> Could we add code to either the request processor or the action servlet
> to add the default message resource defined in a struts.config to a
> scope (app/session/request) under the key
> "javax.servlet.jsp.jstl.fmt.localizationContext", so the default bundle
> works with fmt:message without having to do a fmt:setBundle. I would
> think it make sense to do this on a request basis to support different
> modules.
>
> If this is already the case already, then I must be doing something else
> wrong. If it is being set like this the case... please let me know,
> ignore this request, and let me be the first to say nice!!
>
> Thanks
> - Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
