[
https://issues.redhat.com/browse/WFWIP-304?page=com.atlassian.jira.plugin...
]
Jeff Mesnil commented on WFWIP-304:
-----------------------------------
[~mkopecky] setting the priority to blocker seems too high.
First, there is no TCK tests that assert this feature.
Then, as David mentions, the lifecycle of the ConfigSource is not properly specified.
The actual issue is minor. In WildFly, the Config object is released when a deployment is
undeployed and it would only affect ConfigSource/Converters that needs to deallocate any
resources they hold between the undeployment and a server shutdown.
As the MicroProfile Expansion Pack is meant to support only single deployment, this window
does not exist.
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)