[
https://issues.apache.org/jira/browse/TAMAYA-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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)
