[
https://issues.jboss.org/browse/AS7-1185?page=com.atlassian.jira.plugin.s...
]
Juergen Zimmermann commented on AS7-1185:
-----------------------------------------
OK, I wasn't aware that the .ear root inside the classpath was JBoss specific. I
understand that this feature is gone.
Using a JAR just containing the .properties files works.
Perhaps you should add this migration problem to a migration FAQ or something like that.
Classpath issue breaks localization in Hibernate Validator
----------------------------------------------------------
Key: AS7-1185
URL:
https://issues.jboss.org/browse/AS7-1185
Project: Application Server 7
Issue Type: Bug
Components: EE
Affects Versions: 7.0.0.CR1
Reporter: Juergen Zimmermann
Attachments: testcase-src.zip, testcase.ear
If you want Hibernate Validator to produce internationalized / localized messages you
need properties files like e.g. ValidatorMessages_en.properties or
ValidatorMessages_de.properties. These properties files must be in the Classpath. Thus if
you need them in an EJB module, they are placed in the root directory of the EAR.
According to the language the right file is picked up, and the right hand side has the
localized message belonging to the key on the left hand side. However, if no key is found
or if the properties file isn't found, then the localized message is just
"{key}" aka the template message.
I'll attach a testcase to reproduce this issue that ValidatorMessage_xx.properties
isn't found in the Classpath.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira