[jira] [Commented] (TAMAYA-356) Make resolvers configurable via Java API

["Anatole Tresch (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TAMAYA-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16915219#comment-16915219 ] 

Anatole Tresch commented on TAMAYA-356:
---------------------------------------

This can be achieved as follows:
 * Use the _ConfigurationBuilder_ to setup your configuration programmatically.
 * Create your custom _DefaultExpressionEvaluator_ by adding only the resolvers needed in the order required.
 * Configure an _ExpressionResolutionFilter_ with the _ExpressionEvaluator_ created in the previous step.
 * Add the filter to your configuration setup using the _ConfigurationBuilder_.
 * Create your _Configuration_, enjoy!

In code:

 
{code:java}
ExpressionEvaluator evaluator = new DefaultExpressionEvaluator(
      Arrays.asList(new FileResolver(), new DecryptResolver()));
ExpressionResolutionFilter reolverFilter = new ExpressionResolutionFilter(evaluator);
ConfigurationBuilder builder = Configuration.createConfigurationBuilder();
...
builder.addPropertyFilters(reolverFilter);
Configuration config = builder.build();
{code}
 

 

> Make resolvers configurable via Java API
> ----------------------------------------
>
>                 Key: TAMAYA-356
>                 URL: https://issues.apache.org/jira/browse/TAMAYA-356
>             Project: Tamaya
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Alexander Suter
>            Assignee: Anatole Tresch
>            Priority: Major
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> I would like to create a tamaya configuration with some specific resolvers with a java api, because I don't want to use the Java Service Loader approach.
>  
> Example:
>  * I only want to use the FileResolver and my custom DecryptResolver. All other core resolvers must not be activated.
>  * Furthermore I completley setup my tamaya Configuration over Java API (without Service Loader approach)



--
This message was sent by Atlassian Jira
(v8.3.2#803003)