We have discussed this somewhat in the past but never developed sufficient motivation. The least intrusive change would be to update the Logger factory to use the message as a key with the resource bundles located in the classpath say under conf/logging-i18n
It should emit a default resource bundle for the messages that don't have a matching key to dynamically build the keys which can be localized. This will allow one to gradually localize output as needed. There does need to be a varargs like I18N encapsulation object for the cases where the log message cannot really be used as a key due to it being composed of runtime values. The aop approach is not going to work with 3.2 due to the jdk1.3 requirements imposed by the 3.2 branch. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3860525#3860525 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3860525 ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
