[jira] [Commented] (TAMAYA-356) Make resolvers configurable via Java API
[ https://issues.apache.org/jira/browse/TAMAYA-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16915337#comment-16915337 ] ASF subversion and git services commented on TAMAYA-356: Commit 912b5c4d15262a5d459cb7ecff04b6400c78c517 in incubator-tamaya-extensions's branch refs/heads/master from Anatole Tresch [ https://gitbox.apache.org/repos/asf?p=incubator-tamaya-extensions.git;h=912b5c4 ] TAMAYA-356 Added test comment. > 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 > Fix For: 0.4-incubating > > 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)
[jira] [Commented] (TAMAYA-356) Make resolvers configurable via Java API
[ https://issues.apache.org/jira/browse/TAMAYA-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16915336#comment-16915336 ] ASF subversion and git services commented on TAMAYA-356: Commit 33c14780edae0b19c324058ea16f8c727af24b93 in incubator-tamaya-extensions's branch refs/heads/master from Anatole Tresch [ https://gitbox.apache.org/repos/asf?p=incubator-tamaya-extensions.git;h=33c1478 ] TAMAYA-356 Extended resolver abtraction so a complete manual setup is possible without using the ServiceContext. > 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 > Fix For: 0.4-incubating > > 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)
[jira] [Commented] (TAMAYA-356) Make resolvers configurable via Java API
[ https://issues.apache.org/jira/browse/TAMAYA-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16915256#comment-16915256 ] ASF subversion and git services commented on TAMAYA-356: Commit 33c14780edae0b19c324058ea16f8c727af24b93 in incubator-tamaya-extensions's branch refs/heads/vote-0.4-incubating-01 from Anatole Tresch [ https://gitbox.apache.org/repos/asf?p=incubator-tamaya-extensions.git;h=33c1478 ] TAMAYA-356 Extended resolver abtraction so a complete manual setup is possible without using the ServiceContext. > 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 > Fix For: 0.4-incubating > > 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)
[jira] [Commented] (TAMAYA-356) Make resolvers configurable via Java API
[ https://issues.apache.org/jira/browse/TAMAYA-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16915257#comment-16915257 ] ASF subversion and git services commented on TAMAYA-356: Commit 912b5c4d15262a5d459cb7ecff04b6400c78c517 in incubator-tamaya-extensions's branch refs/heads/vote-0.4-incubating-01 from Anatole Tresch [ https://gitbox.apache.org/repos/asf?p=incubator-tamaya-extensions.git;h=912b5c4 ] TAMAYA-356 Added test comment. > 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 > Fix For: 0.4-incubating > > 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)
[jira] [Commented] (TAMAYA-356) Make resolvers configurable via Java API
[
https://issues.apache.org/jira/browse/TAMAYA-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
[jira] [Commented] (TAMAYA-356) Make resolvers configurable via Java API
[ https://issues.apache.org/jira/browse/TAMAYA-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16632971#comment-16632971 ] ASF GitHub Bot commented on TAMAYA-356: --- GitHub user alexsuter reopened a pull request: https://github.com/apache/incubator-tamaya-extensions/pull/11 Tamaya 356 resolvers java api https://issues.apache.org/jira/browse/TAMAYA-356 You can merge this pull request into a Git repository by running: $ git pull https://github.com/alexsuter/incubator-tamaya-extensions tamaya-356-resolvers-java-api Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-tamaya-extensions/pull/11.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #11 commit 89392d4c4f8c3deb09ee875c8583a9ee20aaca67 Author: Alex Date: 2018-09-19T16:16:00Z TAMAYA-350 - Do not provide null as "null" string commit 7d8d3238faf471bcb658aa444ba9a4e0b93ec391 Author: Alexander Suter Date: 2018-09-24T20:01:21Z TAMAYA-350 - Do not provide null as "null" string commit 182e5157d1e2298ccd1a3afe075db979f6d299ad Author: Alexander Suter Date: 2018-09-29T12:01:54Z TAMAYA-356 - Make resolvers configurable over java api > Make resolvers configurable via Java API > > > Key: TAMAYA-356 > URL: https://issues.apache.org/jira/browse/TAMAYA-356 > Project: Tamaya > Issue Type: Improvement >Reporter: Alexander Suter >Priority: Major > > 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 (v7.6.3#76005)
[jira] [Commented] (TAMAYA-356) Make resolvers configurable via Java API
[ https://issues.apache.org/jira/browse/TAMAYA-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16632970#comment-16632970 ] ASF GitHub Bot commented on TAMAYA-356: --- Github user alexsuter closed the pull request at: https://github.com/apache/incubator-tamaya-extensions/pull/11 > Make resolvers configurable via Java API > > > Key: TAMAYA-356 > URL: https://issues.apache.org/jira/browse/TAMAYA-356 > Project: Tamaya > Issue Type: Improvement >Reporter: Alexander Suter >Priority: Major > > 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 (v7.6.3#76005)
