[Hibernate-JIRA] Created: (ANN-458) Hibernate Validator initialization always requires keys in ValidatorMessges.properties
5:40 a.m.
Hibernate Validator initialization always requires keys in ValidatorMessges.properties
--------------------------------------------------------------------------------------
Key: ANN-458
URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-458
Project: Hibernate Annotations
Type: Bug
Components: binder
Reporter: Christian Bauer
Priority: Critical
Seam + Hibernate Validator doesn't work. When AnnotationConfiguration boots, it always
uses the DefaultMessageInterpolator (this is actually a separate problem, not only the
event listeners should use the configured interpolator) and the default interpolator
always throws an exception if the message key can't be found.
This is an even bigger problem if you don't want or have a
ValidatorMessages.properties file, like in a typical Seam application where everything is
in messages.properties (Seam managed component). You can't override or set the
resource bundle that is used on startup.
A quick fix would be to not throw an exception in DefaultMessageInterpolator if the key
can't be found in the resource bundle. The key should then be returned as the message.
I see no reason why that shouldn't work, it's the users own fault if he forgot the
key. It's also the regular behavior in JSF.
This is my quick hack to make it work, in DefaultMessageInterpolator:
String string = null;
try {
string = messageBundle != null ? messageBundle.getString( token ) : null;
}
catch( MissingResourceException e ) {
//give a second chance with the default resource bundle
}
if (string == null) {
try {
string = defaultMessageBundle.getString( token );
}
catch( MissingResourceException e) {
return message;
/* We don't want that:
throw new MissingResourceException(
"Can't find resource in validator bundles, key " + token,
defaultMessageBundle.getClass().getName(),
token
);
*/
}
}
I'm writing now about this in the JPwH book, so I expect that I can in the future
simply have messages.properties for Seam with my Hibernate Validator messages. This fix
has to be in 3.2.1.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
6:03 a.m.
New subject: [Hibernate-JIRA] Commented: (ANN-458) Hibernate Validator initialization always requires keys in ValidatorMessges.properties
[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-458?page=co...
]
Christian Bauer commented on ANN-458:
-------------------------------------
After I made that change, I found that this also doesn't work:
TooShortOrLongUsername = Minimum {min}, maximum {max} alphanumeric characters.
I don't know what I'm doing wrong, this is the same as in the HAN test suite.
Hibernate Validator initialization always requires keys in
ValidatorMessges.properties
--------------------------------------------------------------------------------------
Key: ANN-458
URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-458
Project: Hibernate Annotations
Type: Bug
Components: binder
Reporter: Christian Bauer
Priority: Critical
Seam + Hibernate Validator doesn't work. When AnnotationConfiguration boots, it
always uses the DefaultMessageInterpolator (this is actually a separate problem, not only
the event listeners should use the configured interpolator) and the default interpolator
always throws an exception if the message key can't be found.
This is an even bigger problem if you don't want or have a
ValidatorMessages.properties file, like in a typical Seam application where everything is
in messages.properties (Seam managed component). You can't override or set the
resource bundle that is used on startup.
A quick fix would be to not throw an exception in DefaultMessageInterpolator if the key
can't be found in the resource bundle. The key should then be returned as the message.
I see no reason why that shouldn't work, it's the users own fault if he forgot the
key. It's also the regular behavior in JSF.
This is my quick hack to make it work, in DefaultMessageInterpolator:
String string = null;
try {
string = messageBundle != null ? messageBundle.getString( token ) : null;
}
catch( MissingResourceException e ) {
//give a second chance with the default resource bundle
}
if (string == null) {
try {
string = defaultMessageBundle.getString( token );
}
catch( MissingResourceException e) {
return message;
/* We don't want that:
throw new MissingResourceException(
"Can't find resource in validator bundles, key " + token,
defaultMessageBundle.getClass().getName(),
token
);
*/
}
}
I'm writing now about this in the JPwH book, so I expect that I can in the future
simply have messages.properties for Seam with my Hibernate Validator messages. This fix
has to be in 3.2.1.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
12:55 p.m.
New subject: [Hibernate-JIRA] Commented: (ANN-458) Hibernate Validator initialization always requires keys in ValidatorMessges.properties
[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-458?page=co...
]
Emmanuel Bernard commented on ANN-458:
--------------------------------------
org.hibernate.validator.test.HibernateAnnotationIntegrationTest does tests the
MessageInterpolator property use
your code should be string = "{" + token + "}" (actually this is
wrong too but that's the idea. You're in a loop
Hibernate Validator initialization always requires keys in
ValidatorMessges.properties
--------------------------------------------------------------------------------------
Key: ANN-458
URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-458
Project: Hibernate Annotations
Type: Bug
Components: binder
Reporter: Christian Bauer
Priority: Critical
Seam + Hibernate Validator doesn't work. When AnnotationConfiguration boots, it
always uses the DefaultMessageInterpolator (this is actually a separate problem, not only
the event listeners should use the configured interpolator) and the default interpolator
always throws an exception if the message key can't be found.
This is an even bigger problem if you don't want or have a
ValidatorMessages.properties file, like in a typical Seam application where everything is
in messages.properties (Seam managed component). You can't override or set the
resource bundle that is used on startup.
A quick fix would be to not throw an exception in DefaultMessageInterpolator if the key
can't be found in the resource bundle. The key should then be returned as the message.
I see no reason why that shouldn't work, it's the users own fault if he forgot the
key. It's also the regular behavior in JSF.
This is my quick hack to make it work, in DefaultMessageInterpolator:
String string = null;
try {
string = messageBundle != null ? messageBundle.getString( token ) : null;
}
catch( MissingResourceException e ) {
//give a second chance with the default resource bundle
}
if (string == null) {
try {
string = defaultMessageBundle.getString( token );
}
catch( MissingResourceException e) {
return message;
/* We don't want that:
throw new MissingResourceException(
"Can't find resource in validator bundles, key " + token,
defaultMessageBundle.getClass().getName(),
token
);
*/
}
}
I'm writing now about this in the JPwH book, so I expect that I can in the future
simply have messages.properties for Seam with my Hibernate Validator messages. This fix
has to be in 3.2.1.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
2:01 p.m.
New subject: [Hibernate-JIRA] Commented: (ANN-458) Hibernate Validator initialization always requires keys in ValidatorMessges.properties
[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-458?page=co...
]
Christian Bauer commented on ANN-458:
-------------------------------------
I don't understand your comment. Please document the usage of {} etc.
Hibernate Validator initialization always requires keys in
ValidatorMessges.properties
--------------------------------------------------------------------------------------
Key: ANN-458
URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-458
Project: Hibernate Annotations
Type: Bug
Components: binder
Versions: 3.2.0.ga
Reporter: Christian Bauer
Priority: Critical
Fix For: 3.2.1
Seam + Hibernate Validator doesn't work. When AnnotationConfiguration boots, it
always uses the DefaultMessageInterpolator (this is actually a separate problem, not only
the event listeners should use the configured interpolator) and the default interpolator
always throws an exception if the message key can't be found.
This is an even bigger problem if you don't want or have a
ValidatorMessages.properties file, like in a typical Seam application where everything is
in messages.properties (Seam managed component). You can't override or set the
resource bundle that is used on startup.
A quick fix would be to not throw an exception in DefaultMessageInterpolator if the key
can't be found in the resource bundle. The key should then be returned as the message.
I see no reason why that shouldn't work, it's the users own fault if he forgot the
key. It's also the regular behavior in JSF.
This is my quick hack to make it work, in DefaultMessageInterpolator:
String string = null;
try {
string = messageBundle != null ? messageBundle.getString( token ) : null;
}
catch( MissingResourceException e ) {
//give a second chance with the default resource bundle
}
if (string == null) {
try {
string = defaultMessageBundle.getString( token );
}
catch( MissingResourceException e) {
return message;
/* We don't want that:
throw new MissingResourceException(
"Can't find resource in validator bundles, key " + token,
defaultMessageBundle.getClass().getName(),
token
);
*/
}
}
I'm writing now about this in the JPwH book, so I expect that I can in the future
simply have messages.properties for Seam with my Hibernate Validator messages. This fix
has to be in 3.2.1.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
2:01 p.m.
New subject: [Hibernate-JIRA] Updated: (ANN-458) Hibernate Validator initialization always requires keys in ValidatorMessges.properties
[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-458?page=all ]
Christian Bauer updated ANN-458:
--------------------------------
Fix Version: 3.2.1
Version: 3.2.0.ga
Priority: Blocker (was: Critical)
Hibernate Validator initialization always requires keys in
ValidatorMessges.properties
--------------------------------------------------------------------------------------
Key: ANN-458
URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-458
Project: Hibernate Annotations
Type: Bug
Components: binder
Versions: 3.2.0.ga
Reporter: Christian Bauer
Priority: Blocker
Fix For: 3.2.1
Seam + Hibernate Validator doesn't work. When AnnotationConfiguration boots, it
always uses the DefaultMessageInterpolator (this is actually a separate problem, not only
the event listeners should use the configured interpolator) and the default interpolator
always throws an exception if the message key can't be found.
This is an even bigger problem if you don't want or have a
ValidatorMessages.properties file, like in a typical Seam application where everything is
in messages.properties (Seam managed component). You can't override or set the
resource bundle that is used on startup.
A quick fix would be to not throw an exception in DefaultMessageInterpolator if the key
can't be found in the resource bundle. The key should then be returned as the message.
I see no reason why that shouldn't work, it's the users own fault if he forgot the
key. It's also the regular behavior in JSF.
This is my quick hack to make it work, in DefaultMessageInterpolator:
String string = null;
try {
string = messageBundle != null ? messageBundle.getString( token ) : null;
}
catch( MissingResourceException e ) {
//give a second chance with the default resource bundle
}
if (string == null) {
try {
string = defaultMessageBundle.getString( token );
}
catch( MissingResourceException e) {
return message;
/* We don't want that:
throw new MissingResourceException(
"Can't find resource in validator bundles, key " + token,
defaultMessageBundle.getClass().getName(),
token
);
*/
}
}
I'm writing now about this in the JPwH book, so I expect that I can in the future
simply have messages.properties for Seam with my Hibernate Validator messages. This fix
has to be in 3.2.1.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
2:13 p.m.
New subject: [Hibernate-JIRA] Commented: (ANN-458) Hibernate Validator initialization always requires keys in ValidatorMessges.properties
[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-458?page=co...
]
Emmanuel Bernard commented on ANN-458:
--------------------------------------
I mean the fix/hack is broken, you should set string to token and also take the delimiters
into account.
This problem should certainly not be blocker. You must set up all your keys anyway to have
a fully functional application. An application where
"{message.wrong_size} 34"
pops up to the user always looks like a toy app to me.
Hibernate Validator initialization always requires keys in
ValidatorMessges.properties
--------------------------------------------------------------------------------------
Key: ANN-458
URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-458
Project: Hibernate Annotations
Type: Bug
Components: binder
Versions: 3.2.0.ga
Reporter: Christian Bauer
Priority: Blocker
Fix For: 3.2.1
Seam + Hibernate Validator doesn't work. When AnnotationConfiguration boots, it
always uses the DefaultMessageInterpolator (this is actually a separate problem, not only
the event listeners should use the configured interpolator) and the default interpolator
always throws an exception if the message key can't be found.
This is an even bigger problem if you don't want or have a
ValidatorMessages.properties file, like in a typical Seam application where everything is
in messages.properties (Seam managed component). You can't override or set the
resource bundle that is used on startup.
A quick fix would be to not throw an exception in DefaultMessageInterpolator if the key
can't be found in the resource bundle. The key should then be returned as the message.
I see no reason why that shouldn't work, it's the users own fault if he forgot the
key. It's also the regular behavior in JSF.
This is my quick hack to make it work, in DefaultMessageInterpolator:
String string = null;
try {
string = messageBundle != null ? messageBundle.getString( token ) : null;
}
catch( MissingResourceException e ) {
//give a second chance with the default resource bundle
}
if (string == null) {
try {
string = defaultMessageBundle.getString( token );
}
catch( MissingResourceException e) {
return message;
/* We don't want that:
throw new MissingResourceException(
"Can't find resource in validator bundles, key " + token,
defaultMessageBundle.getClass().getName(),
token
);
*/
}
}
I'm writing now about this in the JPwH book, so I expect that I can in the future
simply have messages.properties for Seam with my Hibernate Validator messages. This fix
has to be in 3.2.1.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
2:29 p.m.
New subject: [Hibernate-JIRA] Commented: (ANN-458) Hibernate Validator initialization always requires keys in ValidatorMessges.properties
[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-458?page=co...
]
Christian Bauer commented on ANN-458:
-------------------------------------
"you should set string to token and also take the delimiters into account. "
What?
Hibernate Validator is the _only_ framework that would not let an i18n message key simply
pass through when it can't be found in the message resources. It makes no sense in
development, try to use it. Translation and message definition is usually a second step.
Try to use POT in any Unix software, or PHP software. They all let the key through.
My deployment should not fail everytime I forget a key. Worse, you currently have to
restart the whole appserver to reload a resource bundle (Seam will have a solutionf or
that soonish). This makes this behavior a total nightmare.
I absolutely expect that this will be fixed in 3.2.1 and that I will see a message key
when I forget to define a value for it.
Hibernate Validator initialization always requires keys in
ValidatorMessges.properties
--------------------------------------------------------------------------------------
Key: ANN-458
URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-458
Project: Hibernate Annotations
Type: Bug
Components: binder
Versions: 3.2.0.ga
Reporter: Christian Bauer
Priority: Blocker
Fix For: 3.2.1
Seam + Hibernate Validator doesn't work. When AnnotationConfiguration boots, it
always uses the DefaultMessageInterpolator (this is actually a separate problem, not only
the event listeners should use the configured interpolator) and the default interpolator
always throws an exception if the message key can't be found.
This is an even bigger problem if you don't want or have a
ValidatorMessages.properties file, like in a typical Seam application where everything is
in messages.properties (Seam managed component). You can't override or set the
resource bundle that is used on startup.
A quick fix would be to not throw an exception in DefaultMessageInterpolator if the key
can't be found in the resource bundle. The key should then be returned as the message.
I see no reason why that shouldn't work, it's the users own fault if he forgot the
key. It's also the regular behavior in JSF.
This is my quick hack to make it work, in DefaultMessageInterpolator:
String string = null;
try {
string = messageBundle != null ? messageBundle.getString( token ) : null;
}
catch( MissingResourceException e ) {
//give a second chance with the default resource bundle
}
if (string == null) {
try {
string = defaultMessageBundle.getString( token );
}
catch( MissingResourceException e) {
return message;
/* We don't want that:
throw new MissingResourceException(
"Can't find resource in validator bundles, key " + token,
defaultMessageBundle.getClass().getName(),
token
);
*/
}
}
I'm writing now about this in the JPwH book, so I expect that I can in the future
simply have messages.properties for Seam with my Hibernate Validator messages. This fix
has to be in 3.2.1.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
2:31 p.m.
New subject: [Hibernate-JIRA] Commented: (ANN-458) Hibernate Validator initialization always requires keys in ValidatorMessges.properties
[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-458?page=co...
]
Christian Bauer commented on ANN-458:
-------------------------------------
Btw, in case this isn't clear: The blocker is that AnnotationConfiguration requires
ValidatorMessages.properties, hardcoded. But this is just a consequence of the default
behavior that I'd consider worth changing.
Hibernate Validator initialization always requires keys in
ValidatorMessges.properties
--------------------------------------------------------------------------------------
Key: ANN-458
URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-458
Project: Hibernate Annotations
Type: Bug
Components: binder
Versions: 3.2.0.ga
Reporter: Christian Bauer
Priority: Blocker
Fix For: 3.2.1
Seam + Hibernate Validator doesn't work. When AnnotationConfiguration boots, it
always uses the DefaultMessageInterpolator (this is actually a separate problem, not only
the event listeners should use the configured interpolator) and the default interpolator
always throws an exception if the message key can't be found.
This is an even bigger problem if you don't want or have a
ValidatorMessages.properties file, like in a typical Seam application where everything is
in messages.properties (Seam managed component). You can't override or set the
resource bundle that is used on startup.
A quick fix would be to not throw an exception in DefaultMessageInterpolator if the key
can't be found in the resource bundle. The key should then be returned as the message.
I see no reason why that shouldn't work, it's the users own fault if he forgot the
key. It's also the regular behavior in JSF.
This is my quick hack to make it work, in DefaultMessageInterpolator:
String string = null;
try {
string = messageBundle != null ? messageBundle.getString( token ) : null;
}
catch( MissingResourceException e ) {
//give a second chance with the default resource bundle
}
if (string == null) {
try {
string = defaultMessageBundle.getString( token );
}
catch( MissingResourceException e) {
return message;
/* We don't want that:
throw new MissingResourceException(
"Can't find resource in validator bundles, key " + token,
defaultMessageBundle.getClass().getName(),
token
);
*/
}
}
I'm writing now about this in the JPwH book, so I expect that I can in the future
simply have messages.properties for Seam with my Hibernate Validator messages. This fix
has to be in 3.2.1.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
11:32 a.m.
New subject: [Hibernate-JIRA] Resolved: (ANN-458) Hibernate Validator initialization always requires keys in ValidatorMessges.properties
[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-458?page=all ]
Emmanuel Bernard resolved ANN-458:
----------------------------------
Resolution: Fixed
Assign To: Emmanuel Bernard
Hibernate Validator initialization always requires keys in
ValidatorMessges.properties
--------------------------------------------------------------------------------------
Key: ANN-458
URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-458
Project: Hibernate Annotations
Type: Bug
Components: binder
Versions: 3.2.0.ga
Reporter: Christian Bauer
Assignee: Emmanuel Bernard
Priority: Blocker
Fix For: 3.2.1
Seam + Hibernate Validator doesn't work. When AnnotationConfiguration boots, it
always uses the DefaultMessageInterpolator (this is actually a separate problem, not only
the event listeners should use the configured interpolator) and the default interpolator
always throws an exception if the message key can't be found.
This is an even bigger problem if you don't want or have a
ValidatorMessages.properties file, like in a typical Seam application where everything is
in messages.properties (Seam managed component). You can't override or set the
resource bundle that is used on startup.
A quick fix would be to not throw an exception in DefaultMessageInterpolator if the key
can't be found in the resource bundle. The key should then be returned as the message.
I see no reason why that shouldn't work, it's the users own fault if he forgot the
key. It's also the regular behavior in JSF.
This is my quick hack to make it work, in DefaultMessageInterpolator:
String string = null;
try {
string = messageBundle != null ? messageBundle.getString( token ) : null;
}
catch( MissingResourceException e ) {
//give a second chance with the default resource bundle
}
if (string == null) {
try {
string = defaultMessageBundle.getString( token );
}
catch( MissingResourceException e) {
return message;
/* We don't want that:
throw new MissingResourceException(
"Can't find resource in validator bundles, key " + token,
defaultMessageBundle.getClass().getName(),
token
);
*/
}
}
I'm writing now about this in the JPwH book, so I expect that I can in the future
simply have messages.properties for Seam with my Hibernate Validator messages. This fix
has to be in 3.2.1.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
11:34 a.m.
New subject: [Hibernate-JIRA] Updated: (ANN-458) Hibernate Validator initialization always requires keys in ValidatorMessges.properties
[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-458?page=all ]
Emmanuel Bernard updated ANN-458:
---------------------------------
Component: validator
(was: binder)
Hibernate Validator initialization always requires keys in
ValidatorMessges.properties
--------------------------------------------------------------------------------------
Key: ANN-458
URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-458
Project: Hibernate Annotations
Type: Bug
Components: validator
Versions: 3.2.0.ga
Reporter: Christian Bauer
Assignee: Emmanuel Bernard
Priority: Blocker
Fix For: 3.2.1
Seam + Hibernate Validator doesn't work. When AnnotationConfiguration boots, it
always uses the DefaultMessageInterpolator (this is actually a separate problem, not only
the event listeners should use the configured interpolator) and the default interpolator
always throws an exception if the message key can't be found.
This is an even bigger problem if you don't want or have a
ValidatorMessages.properties file, like in a typical Seam application where everything is
in messages.properties (Seam managed component). You can't override or set the
resource bundle that is used on startup.
A quick fix would be to not throw an exception in DefaultMessageInterpolator if the key
can't be found in the resource bundle. The key should then be returned as the message.
I see no reason why that shouldn't work, it's the users own fault if he forgot the
key. It's also the regular behavior in JSF.
This is my quick hack to make it work, in DefaultMessageInterpolator:
String string = null;
try {
string = messageBundle != null ? messageBundle.getString( token ) : null;
}
catch( MissingResourceException e ) {
//give a second chance with the default resource bundle
}
if (string == null) {
try {
string = defaultMessageBundle.getString( token );
}
catch( MissingResourceException e) {
return message;
/* We don't want that:
throw new MissingResourceException(
"Can't find resource in validator bundles, key " + token,
defaultMessageBundle.getClass().getName(),
token
);
*/
}
}
I'm writing now about this in the JPwH book, so I expect that I can in the future
simply have messages.properties for Seam with my Hibernate Validator messages. This fix
has to be in 3.2.1.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
7124
days inactive
7129
days old
hibernate-issues@lists.jboss.org
9 comments
2 participants
participants (2)
-
Christian Bauer (JIRA) -
Emmanuel Bernard (JIRA)