Multi language support is another `vote` for separation logic from presentation.
Deployment of resources is easy. The trick is to package them separately from your application, have a look at Tomcat (apache-tomcat-5.5.15\common\i18n\). The idea is that you add your resources to classpath and use ResourceBundle at runtime to look for required resource bundle. As a result of such approach when you need to localize your application you make a new resource bundle, put it into your classpath and restart an application, no logic need to be changed. You may check http://java.sun.com/developer/TechTips/1998/tt0521.html#tip2 for reference. There is some performance consideration with resource bundles, but there is a few solutions for it. 2 mholzner: I am sorry that you had such a bad experience with xslt processors, but in numerous system that I designed and develop I haven't seen a single case of bottle-neck caused by xslt processor. I can't say anything about xalan, I am using saxon and newer had problem with it. I am using WebModels framework with xslt based view, and it perform quite well even on junk hardware. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3927124#3927124 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3927124 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
