[ https://issues.jboss.org/browse/WFLY-3438?page=com.atlassian.jira.plugin.... ] Richard Achmatowicz edited comment on WFLY-3438 at 6/3/14 6:22 PM: ------------------------------------------------------------------- If the Remoting Endpoint and the EJBRemoteConnectorService are indeed optional, and may be excluded from the server profile, a better way to handle this would be to check the state of the models for the Remoting and EJB subsystems at start up, see if the elements are present, and if they are both present, add them in as REQUIRED dependencies; otherwise leave them out. Also, if one of them is added in via the management interface, set the handler to force a reload so the check at start up may be performed anew. The use cases where both are left out could correspond to a single node accepting HTTP based servlet requests which accessed a local stateful session bean or a cluster of such nodes. was (Author: rachmato): If the Remoting Endpoint and the EJBRemotingConnectorService are indeed optional, and may be excluded from the server profile, a better way to handle this would be to check the state of the models for the Remoting and EJB subsystems at start up, see if the elements are present, and if they are both present, add them in as REQUIRED dependencies; otherwise leave them out. Also, if one of them is added in via the management interface, set the handler to force a reload so the check at start up may be performed anew. The use cases where both are left out could correspond to a single node accepting HTTP based servlet requests which accessed a local stateful session bean or a cluster of such nodes. -- This message was sent by Atlassian JIRA (v6.2.3#6260)