org.trimou.engine.config

Interface ConfigurationAware

All Known Subinterfaces:

Helper, KeySplitter, LocaleSupport, MissingValueHandler, MustacheListener, Resolver, TemplateLocator, TextSupport

All Known Implementing Classes:

AbstractConfigurationAware, AbstractHelper, AbstractMustacheListener, AbstractResolver, AbstractTemplateLocator, ArrayIndexResolver, BasicSectionHelper, BasicValueHelper, BasicHelper, BracketDotKeySplitter, ClassPathTemplateLocator, DateTimeFormatHelper, DateTimeFormatResolver, DotKeySplitter, DummyTransformResolver, EachHelper, FilePathTemplateLocator, FileSystemTemplateLocator, IfHelper, IndexResolver, IsHelper, ListIndexResolver, LocaleAwareResolver, LocaleAwareValueHelper, MapCustomKeyResolver, MapResolver, MapTemplateLocator, NoOpMissingValueHandler, NumberFormatResolver, NumberIsEvenHelper, NumberIsOddHelper, PathTemplateLocator, ReflectionResolver, ResourceBundleHelper, ResourceBundleResolver, ThisResolver, ThrowingExceptionMissingValueHandler, TransformResolver, UnlessHelper, WithHelper

public interface ConfigurationAware

Configuration-aware components can define additional configuration keys to be processed (i.e. system properties) and also initialize self with partially initialized engine configuration (it's only safe to inspect properties and global data).

Author:

Martin Kouba

Method Summary

Methods

Modifier and Type	Method and Description
Set<ConfigurationKey>	getConfigurationKeys()
void	init(Configuration configuration) Initialize the component.

Method Detail

init

void init(Configuration configuration)

Initialize the component. Keep in mind that the configuration itself is likely not fully initialized yet. It's only safe to inspect properties and global data.

Parameters:

configuration -

getConfigurationKeys

Set<ConfigurationKey> getConfigurationKeys()

Returns:

the set of configuration keys to discover