[ https://issues.jboss.org/browse/WFLY-3438?page=com.atlassian.jira.plugin.... ] Richard Achmatowicz edited comment on WFLY-3438 at 6/3/14 6:34 PM: ------------------------------------------------------------------- I've reviewed this approach and have decided to assume that the Remoting Endpoint (the so-called SYSTEM_ENDPOINT which is started up as part of the Remoting subsystem initialization) will always be present. Remoting is so fundamental, its hard to imagine the Remoting subsystem not being started in a configuration. So the solution will be to check for the existence of the EJBRemoteConnectorService, represented by the element: {noformat} <subsystem xmlns="urn:jboss:domain:ejb3:2.0"> ... <remote connector-ref="..." thread-pool-name="..."/> ... </subsystem> {noformat} and if it is present in the model, add in the two REQUIRED dependencies above; otherwise don't include them. This setup would allow a sysadmin to disable the remote connector and so effectively "turn off" remote invovations on EJBs on the node in question.. was (Author: rachmato): I've reviewed this approach and have decided to assume that the Remoting Endpoint (the so-called SYSTEM_ENDPOINT which is started up as part of the Remoting subsystem initialization) will always be present. Remoting is so fundamental, its hard to imagine the Remoting subsystem not being started in a configuration. So the solution will be to check for the existence of the EJBRemoteConnectorService, represented by the element: {noformat} <subsystem xmlns="urn:jboss:domain:ejb3:2.0"> ... <remote connector-ref="..." thread-pool-name="..."/> ... </subsystem> {noformat} and if it is present in the model, add in the two REQUIRED dependencies above; otherwise don't include them. -- This message was sent by Atlassian JIRA (v6.2.3#6260)