[
https://jira.jboss.org/jira/browse/JBLOGGING-28?page=com.atlassian.jira.p...
]
Alessio Soldano commented on JBLOGGING-28:
------------------------------------------
I think this is caused by the LogRecord in created in JDK14LoggerPluginInstance, which is
missing the resouceBundle.
Doing what follows solve the problem here:
Index: src/main/java/org/jboss/logging/jdk/JDK14LoggerPluginInstance.java
===================================================================
--- src/main/java/org/jboss/logging/jdk/JDK14LoggerPluginInstance.java (revisione 3538)
+++ src/main/java/org/jboss/logging/jdk/JDK14LoggerPluginInstance.java (copia locale)
@@ -75,6 +75,7 @@
record.setLoggerName(name);
record.setThrown(t);
record.setSourceMethodName(null); // prevent expensive, yet guaranteed to be
incorrect lookup
+ record.setResourceBundle(log.getResourceBundle());
log.log(record);
}
I18n logger does not use bundle
-------------------------------
Key: JBLOGGING-28
URL:
https://jira.jboss.org/jira/browse/JBLOGGING-28
Project: JBoss Logging
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jboss-logging-jdk
Affects Versions: 2.2.0.CR1-jboss-logging
Reporter: Alessio Soldano
Assignee: David Lloyd
I've tried the recently added feature for using I18n loggers, forcing the
JDK14LoggerPlugin being used through system property.
My bundle seems not to be taken into consideration thought.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira