[jboss-jira] [JBoss JIRA] (WFLY-12861) microprofile-config subsystem should not expose smallrye implementation to deployments

[Paul Ferraro (Jira)]

    [ https://issues.redhat.com/browse/WFLY-12861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13823639#comment-13823639 ] 

Paul Ferraro edited comment on WFLY-12861 at 12/10/19 9:55 PM:
---------------------------------------------------------------

After some analysis, smallrye-config is completely reliant on the TCCL in a number of areas, including:
* its CDI portable extension (via ConfigProvider.getConfig())
* ConfigBuilder implementation
* default Class converters

... rendering it infeasible to remove this deployment dependency without completely re-implementing much of smallrye-config.


was (Author: pferraro):
After some analysis, smallrye-config is completely reliant on the TCCL in a number of areas, including:
* its CDI portable extension (specifically via ConfigProvider.getConfig())
* ConfigBuilder implementation
* default Class converters

... rendering it infeasible to remove this deployment dependency without completely re-implementing much of smallrye-config.

> 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.  Registering these manually removes that requirement.



--
This message was sent by Atlassian Jira
(v7.13.8#713008)