com.atlassian.confluence.pages.templates
Class DefaultTemplateI18nHandler
java.lang.Object
com.atlassian.confluence.pages.templates.DefaultTemplateI18nHandler
- All Implemented Interfaces:
- TemplateI18nHandler
public class DefaultTemplateI18nHandler
- extends Object
- implements TemplateI18nHandler
TODO - this class and interface really necessary? On the plus side, it abstracts the site-locale decision away
from the main TemplateHandler. On the minus side.... this.
- Since:
- 5.2
Method Summary |
String |
translate(Message message)
Translate a template i18n message to the correct String for the current site language. |
Methods inherited from class java.lang.Object |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
DefaultTemplateI18nHandler
public DefaultTemplateI18nHandler(I18NBeanFactory i18nBeanFactory,
LocaleManager localeManager)
translate
public String translate(Message message)
- Description copied from interface:
TemplateI18nHandler
- Translate a template i18n message to the correct String for the current site language.
- Specified by:
translate
in interface TemplateI18nHandler
- Parameters:
message
- a Message with key and optional arguments
- Returns:
- a translated String
Copyright © 2003-2013 Atlassian. All Rights Reserved.