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