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

[<jue...@we...>]

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. =
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 ;-) It's much easier: A =
JSTL LocalizationContext allows you to specify the ResourceBundle that =
JSTL tags should access, on a per-request basis (via special request =
attributes). Spring simply passes a MessageSource-wrapping =
ResourceBundle subclass in there.

Juergen


-----Original Message-----
From: spr...@li...
[mailto:spr...@li...]On Behalf
Of Max Kutny
Sent: Wednesday, March 17, 2004 1:07 PM
To: spr...@li...
Subject: [Springframework-developer] interference with jstl bundle
lookup strategy


Guys,

will you advise me with the following issue: once the DispatcherServlet
is loaded fmt tags fail to found the resource bundle unless it's
configured as a MessageSource.

Am I getting right that spring intersepts calls to
ResourceBunld.getBundle() (probably by providing own class loader)?

If that was made intentionally what was the rationale behind?

Thanks.

-- Max



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=3D1470&alloc_id=3D3638&op=3Dcli=
ck
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer