On Oct 1, 2012, at 5:42 AM, Julien Martin wrote:
Hello,
I am experiencing trouble with my embedded tomcat: when I run my Spring app
using the embedded Tomcat, it seems the properties are not resolved.
What about using a standard (i.e. not embedded, not part of Eclipse) Tomcat
Thanks Daniel,
I've just deployed my app onto a standard Tomcat: it works ok.
My Spring config is as follows (the relevant parts at least):
bean
class=org.springframework.context.support.ResourceBundleMessageSource
id=messageSource
property name=basenames
I am still trying to work out how to fix this problem.
Can someone please explain to me what the difference is between standard
Tomcat and embedded Tomcat (maven plugin)? Especially where does the
embedded (maven plugin) Tomcat looks for the webapp resources?
Here is how I configured the plugin:
It is working. This is odd...
I changed from
*property name=basenames
value=/META-INF/i18n/application,/META-INF/i18n/messages /
*to
*property name=basenames
value=META-INF/i18n/application,META-INF/i18n/messages /*
Notice I removed the leading slashes. It is now working with Tomcat Maven
plugin.
