ReloadableResourceBundleMessageSource doesn't work with app servers like Weblogic which do not exland the entire war on deployment. This is because ReloadableResourceBundleMessageSource has code like
location = servletContext.getRealPath(location); which returns null when the resource bundle in present in a war that does not get fully exploded. This is also why I dont use org.springframework.web.util.Log4jConfigListener. See this thread for more details. http://forum.springframework.org/showthread.php?t=13146&highlight=ReloadableReso%20urceBundleMessageSource I can see why ReloadableResourceBundleMessageSource is useful during development but don't see much value during deployment. Sanjiv On 12/6/06, thinkboy <[EMAIL PROTECTED]> wrote:
hi, I read that ReloadableResourceBundleMessageSource has the following benefit. • Allows for ResourceBundle refresh without stopping the VM should appfuse set ReloadableResourceBundleMessageSource instead of standard ResourceBundleMessageSource by default? since any change will be reloaded at real-time, it will be a plus for production environment. any problem or disadvantage that I missed out ? pls advise. ~thinkboy. -- View this message in context: http://www.nabble.com/is-ReloadableResourceBundleMessageSource-in-favor--tf2767327s2369.html#a7717143 Sent from the AppFuse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
