We should check and see if we can remove the deprecated remote-naming and ejb classes such as:

1) wildfly-naming-client

• ./src/main/java/org/jboss/naming/remote/client/InitialContextFactory.java

2) jboss-ejb-client

• ./javax/src/main/java/org/jboss/ejb/client/legacy
  • We should check the classes in this package, and see about removing classes related to jboss-ejb-client.properties, scoped context and passing the old properties like remote.connections.* https://docs.jboss.org/author/display/EJBCLIENT/Overview%20of%20Client%20properties.html

3) jboss-ejb-client-legacy , not included in EAP but in maven, we could stop updating it in EAP 8 and just leave it with EAP 7.4

[1] is not included in EAP but in Maven, we should get rid of this if we have not already for EAP 8.0 because only a couple of customers use it and it uses old EAP 6 classes which has a lot of disadvantages such as wasting resources (memory, threads, connections, etc).

 [1] https://maven.repository.redhat.com/ga/org/jboss/jboss-ejb-client-legacy/