Very good thoughts, but one important aspect has not been discussed yet. You'll need to tell the i18N object which Locale to use or specify a particular ResourceBundle with the correct Locale already set on it. Perhaps a new FileWriter would be appropriate in this case with XML attributes in log4j.xml defining the ResourceBundle basename (required) and the Locale country, language, and variant (all optional, defaults to Locale.getDefault()). Migfht also need to specify the charset for UTF-16 languages such as Chinese, Arabic, etc. You could then use Log4J as usual, but just passing in the key instead of the actual message. Heck at that point you could define mutiple i18N appenders of this new subclass then define a Logger with refs to all the internationalized appenders. Then you could be logging the same message in multiple languages simultaneously and the logging API would not change.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870740#3870740 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870740 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
