[
https://issues.apache.org/jira/browse/TAMAYA-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anatole Tresch resolved TAMAYA-273.
-----------------------------------
Resolution: Fixed
* Prints out delegate and config once after SPI has been loaded.
* configjsr based branch already logs config on INFO level, when a new config
for a classloader has been created.
> 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)
