Spring 3.0 localization not working in tomcat, only from jetty locally?

Try classpath*:language ie, search ALL classpaths. Depending on where you are deploying your resource bundles, they may end up in different places in the classloader hierarchy in tomcat and jetty.

Thanks, but this just gives me an error. – tego May 23 at 7:41 Then I would try to hard-code to the actual location of the language resource bundle, like WEB-INF/classes/language. – pap May 23 at 9:10 That didn't work either.

What I think is so wierd about all this is that it loads the language_en. Properties not the default language. Properties file.

I'm not sure how to debug this properly either... – tego May 23 at 10:18.

FINALLY! I solved it! I had to set the JvmOptions: -Duser.

Language=no -Duser. Region=NO in order for tomcat to use the language. Properties and not the language_en.

Properties file. And for some strange reason it now also works when setting the locale (?locale=en) to english too.

Hope this will help some non-english-as-default-locale programmers in the future :P – tego May 23 at 10:49.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.