[jboss-jira] [JBoss JIRA] (WFLY-13422) Make org.jboss.as.remoting optional from naming extension module; others too if possible

[Yeray Borges Santana (Jira)]

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

Yeray Borges Santana commented on WFLY-13422:
---------------------------------------------

{{org.wildfly.http-client.naming}} is required not only by {{RemoteNamingServerService}} but also by {{org.jboss.as.naming.InitialContext}}, which is created by {{InitialContextFactory}}, which is indeed a public class with a public method. I would say taht removes the possibility to make it optional.

> Make org.jboss.as.remoting optional from naming extension module; others too if possible
> ----------------------------------------------------------------------------------------
>
>                 Key: WFLY-13422
>                 URL: https://issues.redhat.com/browse/WFLY-13422
>             Project: WildFly
>          Issue Type: Enhancement
>          Components: Naming
>            Reporter: Brian Stansberry
>            Assignee: Yeray Borges Santana
>            Priority: Major
>
> The org.jboss.as.naming module's dependency on org.jboss.as.remoting is only needed if the "service=remote-naming" child resource is used. So it should be made optional with RemoteNamingResourceDefinition registering an additional package.
> This is part of an overall effort to eliminate non-optional dependencies on the org.jboss.as.remoting module. Both because depending on extension modules has a code smell but specifically because org.jboss.as.remoting module brings in fairly large dependency tree.
> I believe there may be other module dependencies that could be made optional as part of this same work, e.g. org.jboss.remoting and org.wildfly.http-client.naming. Maybe others.



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