RE: bean:message and performance
What about templates or tiles? -Moritz. -Original Message- From: Francois-Xavier Bonnet [mailto:[EMAIL PROTECTED]] Sent: Monday, November 19, 2001 2:18 PM To: [EMAIL PROTECTED] Subject: bean:message and performance Hello all, I am using bean:message tag for internationalizing my pages. My problem is that some pages have too many tags (sometimes up to 50 just for bean: message) : 1) for some jsp, the generated .class file may exceed the 64 K limit allowed for a java method 2) even if pages do not reach this limit, performance are poor I have been thinking about 2 solutions to this problem : 1) writing some servlet that would replace bean:message tags by their value before compilation and cache the result jsp file in one folder for each language. 2) using some other tool for i18n of my application (maybe cocoon ?) Any idea or advice would be greatly appreciated. Francois-Xavier [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]
bean:message and performance
Hello all, I am using bean:message tag for internationalizing my pages. My problem is that some pages have too many tags (sometimes up to 50 just for bean: message) : 1) for some jsp, the generated .class file may exceed the 64 K limit allowed for a java method 2) even if pages do not reach this limit, performance are poor I have been thinking about 2 solutions to this problem : 1) writing some servlet that would replace bean:message tags by their value before compilation and cache the result jsp file in one folder for each language. 2) using some other tool for i18n of my application (maybe cocoon ?) Any idea or advice would be greatly appreciated. Francois-Xavier [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: bean:message and performance
- Are you absolutely sure the i18n is the reason of the poor performance or is it an assumption? Using some profiling tool could help pinpoint the problem. - Another solution to the size issue: decompose your pages into included subcomponents that are of smaller size. Fr. -Original Message- From: Francois-Xavier Bonnet [mailto:[EMAIL PROTECTED]] Sent: 19 November 2001 14:18 To: [EMAIL PROTECTED] Subject: bean:message and performance Hello all, I am using bean:message tag for internationalizing my pages. My problem is that some pages have too many tags (sometimes up to 50 just for bean: message) : 1) for some jsp, the generated .class file may exceed the 64 K limit allowed for a java method 2) even if pages do not reach this limit, performance are poor I have been thinking about 2 solutions to this problem : 1) writing some servlet that would replace bean:message tags by their value before compilation and cache the result jsp file in one folder for each language. 2) using some other tool for i18n of my application (maybe cocoon ?) Any idea or advice would be greatly appreciated. Francois-Xavier [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] The information in this email is confidential and is intended solely for the addressee(s). Access to this email by anyone else is unauthorised. If you are not an intended recipient, please notify the sender of this email immediately. You should not copy, use or disseminate the information contained in the email. Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Capco. http://www.capco.com *** -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: bean:message and performance
Hi, I don't know if your poor performances come from bean:message tags, but there is an alternative to it. Another approach to i18n is having one page for each Locale. Each page contains appropriate translation. Pages can be grouped in localized directories. Tiles framework can help you for this (and for the 64k limit !). You can have different version of the same Tile (a jsp page), one for each Locale. When you insert your Tile, framework choose the appropriate one, according to Locale. Mapping between Tiles name to insert and real jsp page is done in tilesDefinition.xml file. You have one config file per Locale. Config file naming follow the Java properties file convention (extension with Locale's abbreviation). Tiles allow mixing of localized Tiles and use of bean:message. Use Tiles for big pages, tags for small part, menus, ... Hope this help, Cedric Francois-Xavier Bonnet wrote: Hello all, I am using bean:message tag for internationalizing my pages. My problem is that some pages have too many tags (sometimes up to 50 just for bean: message) : 1) for some jsp, the generated .class file may exceed the 64 K limit allowed for a java method 2) even if pages do not reach this limit, performance are poor I have been thinking about 2 solutions to this problem : 1) writing some servlet that would replace bean:message tags by their value before compilation and cache the result jsp file in one folder for each language. 2) using some other tool for i18n of my application (maybe cocoon ?) Any idea or advice would be greatly appreciated. Francois-Xavier [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]
