[
https://issues.apache.org/jira/browse/TAMAYA-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16551308#comment-16551308
]
ASF subversion and git services commented on TAMAYA-273:
--------------------------------------------------------
Commit 681cb1e5668b0a581528bf85e09d1ab6f54a30f9 in incubator-tamaya-sandbox's
branch refs/heads/master from [~wlieurance]
[
https://git-wip-us.apache.org/repos/asf?p=incubator-tamaya-sandbox.git;h=681cb1e
]
TAMAYA-273 Fix infinite recursion in metamodel
With the lazily loaded configuration in metamodel, the logic is
susceptible to an infinite recursion if any part of the configuration
setting does a getConfiguration in the middle. The spi delegation logic
added getConfiguration logging to all static calls as part of
5a130523ab7d3a9d33091b13f62db90ddb8fba5c in incubator-tamaya, which
caused this module to infinitely recurse and fail. This commit breaks
the chain of possible recursion.
> Describe current configuration provider configuration upon Tamaya launch
> ------------------------------------------------------------------------
>
> Key: TAMAYA-273
> URL: https://issues.apache.org/jira/browse/TAMAYA-273
> Project: Tamaya
> Issue Type: Improvement
> Components: Core
> Affects Versions: 0.3-incubating
> Reporter: Philipp Ottlinger
> Assignee: Anatole Tresch
> Priority: Major
>
> After starting an application that makes use of Tamaya I want to see which
> configuration providers are activated and in which order they appear. At the
> moment the output is:
> {code}
> Jun 12, 2017 8:24:05 PM org.apache.tamaya.spi.ServiceContextManager
> loadDefaultServiceProvider
> INFORMATION: Using Service Context of type:
> org.apache.tamaya.core.internal.DefaultServiceContext
> Jun 12, 2017 8:24:05 PM org.apache.tamaya.ConfigurationProvider spi
> {code}
> A possible output (toString() of providers?) could be the ordinal and a short
> hint how the provider works or what services it offers.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
