[
https://issues.redhat.com/browse/WFLY-12861?page=com.atlassian.jira.plugi...
]
Paul Ferraro updated WFLY-12861:
--------------------------------
Description: Smallrye is an implementation detail of the specification and should not
be exposed to deployments. It seems the only reasons to expose io.smallrye.config to a
deployment is to allow CDI to dynamically load its portable extension, and for lazy
service loading of the ConfigProviderResolver implementation. Registering these manually
removes that requirement. (was: Smallrye is an implementation detail of the specification
and should not be exposed to deployments. It seems the only reason to expose
io.smallrye.config to a deployment is to allow CDI to dynamically load its portable
extension. Registering this manually removes that requirement.)
microprofile-config subsystem should not expose smallrye
implementation to deployments
--------------------------------------------------------------------------------------
Key: WFLY-12861
URL:
https://issues.redhat.com/browse/WFLY-12861
Project: WildFly
Issue Type: Bug
Components: MP Config
Affects Versions: 18.0.1.Final
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Priority: Major
Smallrye is an implementation detail of the specification and should not be exposed to
deployments. It seems the only reasons to expose io.smallrye.config to a deployment is to
allow CDI to dynamically load its portable extension, and for lazy service loading of the
ConfigProviderResolver implementation. Registering these manually removes that
requirement.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)