I will do that if it is still a problem when we start using 1.3 or 2.0.
Caching is ok so far.
- Juha
Johan Compagner wrote:
if you can get a nice test where i can see those hotspots (but then in
1.3 or 2.0)
then i will look at it to optimize that.
johan
On 2/1/07, *Juha Alatalo *
Localizer is meant to be a realy thin layer mainly providing easy to
use access helpers. Flexibility is meant to come from
ResourceStreamLocators and ResourceStreamFinder. In 1.x the
searchStack is still part of Localizer. In 2.x it has been moved into
the ResourceStreamFactory (used to be
if you can get a nice test where i can see those hotspots (but then in 1.3or
2.0)
then i will look at it to optimize that.
johan
On 2/1/07, Juha Alatalo [EMAIL PROTECTED] wrote:
Hi,
is there some way of using own Localizer in WebApplication? I found out
that in version 1.1 there was
Hi,
is there some way of using own Localizer in WebApplication? I found out
that in version 1.1 there was setLocalizer() method in Application, but
I couldn't find such anymore anywhere.
In quite many cases the path used in Localizer.visitResourceLoaders() is
realy long and there is done too
