-
Enhancement
-
Resolution: Done
-
Major
-
None
-
None
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.
- is related to
-
WFLY-13812 RemoteNamingAdd should use a capability to access the remoting Endpoint
- Closed
- relates to
-
WFCORE-4955 Create a wildfly-network OutboundConnection interface from AbstractOutboundConnectionService; expose via capabilities
- Closed