[
https://issues.redhat.com/browse/WFWIP-304?page=com.atlassian.jira.plugin...
]
Marek Kopecky commented on WFWIP-304:
-------------------------------------
bq. What would happen if another endpoint is using this Config object? Would its
configsources and converters be closed?
It was just an example that demonstrate, that releaseConfig call is possible. It was not
full customer use-case (where some synchronization would be necessary, etc.).
{quote}
However calling releaseConfig will lead to inconsistencies and unexpected behaviours. The
ConfigProviderResolver interface is in the SPI package and is meant for integration, not
for user code.
The Config API/SPI is not properly split. We have to take that into consideration when
something is technically doable but should not be recommended.
{quote}
releaseConfig and registerConfig methods are currently public in public
org.eclipse.microprofile.config.api jboss module. I'm OK with clarification in future
MP spec releases, but now we have 1.4 version.
AutoClosable behaviour from MP Config spec is not implemented
-------------------------------------------------------------
Key: WFWIP-304
URL:
https://issues.redhat.com/browse/WFWIP-304
Project: WildFly WIP
Issue Type: Bug
Reporter: Marek Kopecky
Assignee: Jeff Mesnil
Priority: Blocker
Current implementation MP Config 1.4 doesn t implement AutoCloseable behaviour on
ConfigSource and Converter classes. Developers create [MP
issue|https://github.com/eclipse/microprofile-config/issues/136], because these
specification requirements seems confusing and unclear to them. [This
issue|https://github.com/eclipse/microprofile-config/issues/136] is not approved as a bug
from MP community.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)