[
https://issues.redhat.com/browse/WFWIP-304?page=com.atlassian.jira.plugin...
]
Jeff Mesnil commented on WFWIP-304:
-----------------------------------
What's the point of this use case?
This is incorrect:
{code}
Config config = resolver.getConfig();
response.append(config.getValue("test", String.class));
resolver.releaseConfig(config);
{code}
By releasing the config here, you have release it for the *whole* deployment.
What would happen if another endpoint is using this Config object? Would its configsources
and converters be closed?
The lifecycle of a ConfigSource is underspecified. Closing a config source or a converter
when a config is released *without* a clear specification of the Config lifecycle and
resource ownership will lead to inconsistent behaviour.
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)