Tamaya Examples


This example shows the basic functionality that is available when Tamaya is used without any further extensions. It shows how configuration can be added to the classpath and how it can be accessed.

Simple PropertySource

This example shows how to write and register an additional PropertySource and PropertySourceProvider, which is the SPI to add your own configuration data and locations. For a more advanced example you may also have a look at the provided default metamodels, e.g. the simple metamodel (currently in the experimental part and not shipped with the current release).


This example shows how resources can be located using ANT-styled paths and this feature can help you to implement PropertySourceProvider instances that provide configuration for a set of files/folders at a certain (searchable) location, as provided by the resource extension_.


The resolver example defines a configuration file that illustrates the usage of placeholders that are resolved on configuration access, as provided by the resolver extension.


The injection sample shows how to inject configuration into a created object instance, or how to instantiate a proxied configuration template, which provides a type-safe configuration access mechanism. This functionality is provided by the injection extension. Hereby neither JSR 330 nor 299 are used, so it is pure and minimal SE based implementation.


This example shows how the event extension can be used to automatically adapt the current configuration when the underlying configuration data is changing, e.g. when new configuration is added to a file folder, or removed or adapted.


This example shows how to build a Configuration using a simple pure SE builder API as provided by the builder extension.


THe remote example shows a simple setup where parts of the Configuration are read remotedly.