Vernon,
> After more than three hours research and test, I haven't resolve the
> problem yet. If my understand is right, what you suggested is to
> have the following code frame in the JSP page:
>
>
< I had this line at the very
> begining of the page
>
> greetingMorning
>
><--
Han,
Thanks for your cue.
After more than three hours research and test, I haven't resolve the problem yet. If
my understand is right, what you
suggested is to have the following code frame in the JSP page:
< I
had this line at the very
begining of the page
greetingMorning
Vernon,
you should be able to avoid unnecessary loading of resource bundles by
using the and tags.
If you use at the beginning of your page, it will
establish a localization context and store the appropriate resource
bundle in it. Any subsequent actions will leverage this
resource bundle, in
Thanks Tim.
It seems I have to have a custom tag as the fmt tage replacement. I guess I shall
start with studying the fmt tag code.
On the other hand, I hope that Shawn will come another set of fmt implementation since
200 items in one page are not
an abnormal case.
Vernon
7/25/2002 2:55:
Caching as the page is generated would not help, but pre-caching on
server start up could solve your problem. I would think that the huge
overhead you're experiencing is that when it tries to assemble the page in
question, it's creating and destroying objects to retrieve the proper
language s
See the below.
7/25/2002 12:00:36 PM, peter lin <[EMAIL PROTECTED]> wrote:
>
>
>Vernon Wu wrote:
>>
>> Peter,
>>
>> Thanks for your suggestion.
>>
>> Can you clarify the statement: "the data in the resource files are static"?
>>
>> In regarding of the five options you mentioned:
>> >1. use t
Vernon Wu wrote:
>
> Peter,
>
> Thanks for your suggestion.
>
> Can you clarify the statement: "the data in the resource files are static"?
>
> In regarding of the five options you mentioned:
> >1. use the cache tag, which uses fmt tag
> >2. write a custom tag which caches it as someone else
Peter,
Thanks for your suggestion.
Can you clarify the statement: "the data in the resource files are static"?
In regarding of the five options you mentioned:
>1. use the cache tag, which uses fmt tag
>2. write a custom tag which caches it as someone else mentioned
The caching mechanism only w
You have a couple different options that will scale much better if the
data in the resource files are static and do not change dynamically.
1. use the cache tag, which uses fmt tag
2. write a custom tag which caches it as someone else mentioned
3. write a custom tag that extends the fmt tag
4. p
Thanks for sharing your approache.
That is a method I can consider. I hope there is a soluation other than dividing the
page into two or three pages.
Vernon
7/24/2002 8:43:34 PM, Tim Kettering <[EMAIL PROTECTED]> wrote:
>
>I'm no expert on this stuff, but I had something similar to this (al
I'm no expert on this stuff, but I had something similar to this (although
nowhere on the scale of yours) - with lots of hex color values littered
through the the website being controlled by tags that grabbed values off a
XML file, and it was really dragging down the rendering process.
So what I
I use the jstl-fmt port of jstl in my current project. I have three resource files:
default, en, and zh. About 440 entries in
each file. When I open a page with about 250 items in the resource file, the memory
consumption increases
dramatically. To save the memory usage, I delete one of the t
12 matches
Mail list logo
