[
https://issues.redhat.com/browse/WFWIP-304?page=com.atlassian.jira.plugin...
]
Jeff Mesnil commented on WFWIP-304:
-----------------------------------
Jeff Mesnil Based on "Release Notes for MicroProfile Config
1.4", new 1.4 version handles this issue 265. This issue suggests that users use
getConfig() (and similar methods) in deployments.
Calling resolver.getConfig() from a deployment is fine (this is intended if CDI injection
is not used).
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.
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)