EJB client request processing makes use of a DeploymentRepositoryService and DeploymentRepository to discover which EE modules are deployed on a server. At present, this repository is defined locally and only reflects modules deployed on a single server.

One limitation of a local deployment repository is that, for the case of the Wildfly HTTP Client applications, a discovery request sent to a load balancer will only return the modules available on one node of the cluster - the node which the load balancer decided to forward the request to - and does not provide information about the deployments on all nodes in the cluster.

This issue concerns replacing the DeploymentRepository with a DistributedDeploymentRepository which will reflect the state of EE module deployments over all servers in a cluster. The DistributedDeploymentRepository will essentially be a map of module names to nodes in a cluster.

This will simplify discovery processing for the Wildfly HTTP Client and will greatly enhance the ability to route requests to the correct backend servers behind a load balancer.