[Springframework-developer] Re: interference with jstl bundle lookup strategy

[Max K. <mk...@um...>]

> The only thing that Spring does in terms of JSTL is to expose a JSTL
> LocalizationContext to JstlViews: So if you use a DispatcherServlet
> with JstlViews, fmt tags in those views will access the Spring
> MessageSource.

That's clear now. When I provided no messageSource bean Spring created the
empty one for me. Thus my fmt tags failed to see the l10n messages.

Could you explanation to be added to the "MVC step by step" tutorial?
MessageSource first appeared on the step 2 and it wasn't clear of how
Spring handles LocalizationContext with jstl. I also skim the reference
documentation and wasn't able to find it there either.


> In all other views like plain InternalResourceViews,
> there shouldn't be any sort of JSTL interference.

> And no, Spring doesn't mess with the classloader ;-)

Sorry for that. I found that ResourceBundle.getBundle() failed for another reason.


Thanks.

-- Max