Hi, I'm working on my first EJB project, and was wondering if someone had some suggestions for handling localization issues for a web app. I've read some articles using java properties files with JSP to solve localization issues with web content, etc. Since we are using Weblogic for the app server, stateless EJB session beans would seem to be a possible solution. The article I read made heavy use of the JSP session object for storing page parameters, which could become expensive to the server. Since weblogic and EJB support bean instance pooling for stateless session EJB's, would this be a good route to go. For eg, since the stateless session beans do not accept parameters in .create() methods, would you want to implement a localization bean for each region? These beans could initialize off of their respective properties file, and then pooled for subsequent requests from the presentation tier. Is this a bad way to approach it, or should I consider a different type where you simply pass in a country code to create() and it reads the proper file? My first thoughts were to do a USLocale, FRLocale, SPLocale stateless session bean, etc. but I wouldn't want infrequently used objects to take up resources. Any advice or past solutions appreciated, Thanks Kris =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
