2:36 a.m.
Classpath issue break localization in Hibernate Validator
---------------------------------------------------------
Key: AS7-1185
URL: https://issues.jboss.org/browse/AS7-1185
Project: Application Server 7
Issue Type: Bug
Components: Modules
Affects Versions: 7.0.0.CR1
Reporter: Juergen Zimmermann
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
2:36 a.m.
New subject: [JBoss JIRA] Updated: (AS7-1185) Classpath issue breaks localization in Hibernate Validator
[
https://issues.jboss.org/browse/AS7-1185?page=com.atlassian.jira.plugin.s...
]
Juergen Zimmermann updated AS7-1185:
------------------------------------
Summary: Classpath issue breaks localization in Hibernate Validator (was: Classpath
issue break localization in Hibernate Validator)
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: Modules
Affects Versions: 7.0.0.CR1
Reporter: Juergen Zimmermann
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
2:38 a.m.
New subject: [JBoss JIRA] Updated: (AS7-1185) Classpath issue breaks localization in Hibernate Validator
[
https://issues.jboss.org/browse/AS7-1185?page=com.atlassian.jira.plugin.s...
]
Juergen Zimmermann updated AS7-1185:
------------------------------------
Attachment: testcase.ear
testcase-src.zip
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: Modules
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
2:40 a.m.
New subject: [JBoss JIRA] Commented: (AS7-1185) Classpath issue breaks localization in Hibernate Validator
[
https://issues.jboss.org/browse/AS7-1185?page=com.atlassian.jira.plugin.s...
]
Juergen Zimmermann commented on AS7-1185:
-----------------------------------------
You can invoke the testcase as a RESTful webservice via a POST request, and just submit
this XML data so that the <name> content is invalid:
<?xml version="1.0" encoding="UTF-8"
standalone="yes"?>
<customer id="1">
<name>Name_1</name>
</customer>
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: Modules
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
11:25 a.m.
New subject: [JBoss JIRA] Commented: (AS7-1185) Classpath issue breaks localization in Hibernate Validator
[
https://issues.jboss.org/browse/AS7-1185?page=com.atlassian.jira.plugin.s...
]
jaikiran pai commented on AS7-1185:
-----------------------------------
The root of the .ear is not available in the classpath. Move those .properties to the
.war/WEB-INF/classes folder (if you need them in the web layer) or to the root of the ejb
jar file (if it's required in the EJB module).
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: Modules
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
11:25 a.m.
New subject: [JBoss JIRA] Updated: (AS7-1185) Classpath issue breaks localization in Hibernate Validator
[
https://issues.jboss.org/browse/AS7-1185?page=com.atlassian.jira.plugin.s...
]
jaikiran pai updated AS7-1185:
------------------------------
Component/s: EE
(was: Modules)
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
12:19 p.m.
New subject: [JBoss JIRA] Commented: (AS7-1185) Classpath issue breaks localization in Hibernate Validator
[
https://issues.jboss.org/browse/AS7-1185?page=com.atlassian.jira.plugin.s...
]
Juergen Zimmermann commented on AS7-1185:
-----------------------------------------
Hmm, but I need these properties files in the EJB *AND* in the web module. If the EAR root
isn't in the CLASSPATH anymore, I'd consider this as a serious regression.
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
12:21 p.m.
New subject: [JBoss JIRA] Commented: (AS7-1185) Classpath issue breaks localization in Hibernate Validator
[
https://issues.jboss.org/browse/AS7-1185?page=com.atlassian.jira.plugin.s...
]
jaikiran pai commented on AS7-1185:
-----------------------------------
EE never mandated the .ear root to be in the classpath. It was just a JBoss specific way
which was deprecated in AS5 (there was a flag to change the behaviour).
If you want it available in both EJB and web, then package it at the root of a jar and
place that jar in the .ear/lib folder. That should work. If it doesn't, then let us
know.
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
12:58 p.m.
New subject: [JBoss JIRA] Commented: (AS7-1185) Classpath issue breaks localization in Hibernate Validator
[
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
2:14 p.m.
New subject: [JBoss JIRA] Commented: (AS7-1185) Classpath issue breaks localization in Hibernate Validator
[
https://issues.jboss.org/browse/AS7-1185?page=com.atlassian.jira.plugin.s...
]
jaikiran pai commented on AS7-1185:
-----------------------------------
Thanks for testing and confirming that it works.
{quote}
Perhaps you should add this migration problem to a migration FAQ or something like that.
{quote}
Yes, this would make sense in the classloading article for AS7. I'll add some lines
about this, tomorrow.
Closing this JIRA.
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
2:14 p.m.
New subject: [JBoss JIRA] Closed: (AS7-1185) Classpath issue breaks localization in Hibernate Validator
[
https://issues.jboss.org/browse/AS7-1185?page=com.atlassian.jira.plugin.s...
]
jaikiran pai closed AS7-1185.
-----------------------------
Assignee: jaikiran pai
Resolution: Rejected
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
Assignee: jaikiran pai
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
2:23 p.m.
New subject: [JBoss JIRA] Reopened: (AS7-1185) Classpath issue breaks localization in Hibernate Validator
[
https://issues.jboss.org/browse/AS7-1185?page=com.atlassian.jira.plugin.s...
]
jaikiran pai reopened AS7-1185:
-------------------------------
Re-opening to add forum reference
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
Assignee: jaikiran pai
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
2:25 p.m.
New subject: [JBoss JIRA] Updated: (AS7-1185) Classpath issue breaks localization in Hibernate Validator
[
https://issues.jboss.org/browse/AS7-1185?page=com.atlassian.jira.plugin.s...
]
jaikiran pai updated AS7-1185:
------------------------------
Forum Reference: http://community.jboss.org/thread/169225?tstart=0
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
Assignee: jaikiran pai
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
2:25 p.m.
New subject: [JBoss JIRA] Closed: (AS7-1185) Classpath issue breaks localization in Hibernate Validator
[
https://issues.jboss.org/browse/AS7-1185?page=com.atlassian.jira.plugin.s...
]
jaikiran pai closed AS7-1185.
-----------------------------
Resolution: Rejected
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
Assignee: jaikiran pai
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
4923
days inactive
4929
days old
13 comments
2 participants
participants (2)
-
jaikiran pai (JIRA) -
Juergen Zimmermann (JIRA)