[jboss-jira] [JBoss JIRA] (AS7-1934) EJB client context configuration and management ops

[ https://issues.jboss.org/browse/AS7-1934?page=com.atlassian.jira.plugin.s... ] jaikiran pai commented on AS7-1934: ----------------------------------- For reference, here's some of the requirements that have been brought up on the AS7 dev mailing list thread http://lists.jboss.org/pipermail/jboss-as7-dev/2011-September/003772.html {quote} Server Implementation --------------------- The EE subsystem already contains most of the required APIs for handling remote invocations. Any remotely accessible ComponentView will be registered with the remote invocation service along with its app/module/distinctName identification. A special in-VM EJB receiver will also exist and will be similarly updated with the current available component views and their modules. Management configurations will be introduced for the purpose of establishing and maintaining Remoting connections to remote servers. EJB client contexts should be created for each deployment, and a deployment descriptor should be made available to any EE deployment for the purpose of associating Remoting connections (and probably clusters etc.) with the EJB client context for that EE module. This allows each deployment to specify what remote servers it can "see", while still keeping the network configuration business in the central management model. All deployments on the server which have an EE client context will have the in-VM receiver added to it automatically, so that it can access all EJBs in the server via remote interface locally. {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira