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 works when at least portion of data has be retrieved early. In my case, only a small among data, if there is any, has be retrieved before the page from the resource file. So these two approaches might not solve the problem >3. write a custom tag that extends the fmt tag What is the goal of this extension? Is it to refine the fmt tag implemention so that it will not eat up the much memory? Or to have the caching mechanism on? >4. patch fmt tag to cache it and submit the patch to shawn I would like to do that once I am free from current project. >5. you can write a custom extension to the resource bundle that does the >caching. that will allow you to use fmt tag as is and have your resource >extension do the caching For a set of large size resource files, this approache also comsumes a lot of memory and it will hold the memory during the life time of the application. Please point out if I am in any above statements. BTW, the reason of more than 200 items in the resource files is man sets of check boxes and pull down lists in the page. Is any way I can cut short the items in resource file? 7/25/2002 4:37:11 AM, peter lin <[EMAIL PROTECTED]> wrote: > >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. patch fmt tag to cache it and submit the patch to shawn >5. you can write a custom extension to the resource bundle that does the >caching. that will allow you to use fmt tag as is and have your resource >extension do the caching > > >I hope that helps > >peter > > >Vernon Wu wrote: >> >> 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 three resource files. >The initial memory usage is about 20m. >> During the translation process, the memory consumption glows to over 160m and >exceeds the machine limit. And the >> session dies and server crashes. >> >> Any solution for this problem? >> >> The web container I use is TC 4.0.4. >> >> Thanks, >> >> Vernon >> >> >> -- >> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> >> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > >-- >To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> >For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
