[ http://jira.jboss.com/jira/browse/JBAS-1458?page=comments#action_12315451 ] Andrew Oliver commented on JBAS-1458: -------------------------------------
Read the original bug for use case. Overall just the ability to deploy EJBContainers with no remote invoker whatsoever is the idea. Everything does local invocations (including for remote interfaces). Nothing listening on any port for remote invocations, etc. > EJB containers require JRMP invoker > ----------------------------------- > > Key: JBAS-1458 > URL: http://jira.jboss.com/jira/browse/JBAS-1458 > Project: JBoss Application Server > Type: Feature Request > Components: EJBs > Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final, JBossAS-3.2.6 Final > Reporter: Andrew Oliver > Priority: Minor > > > EJBs require the JRMP invoker even if the container-configuration is not > bound to the JRMP invoker. It should be possible to deploy EJBs that are not > remotely accessible (even if they have Remote interfaces) via any invoker > except for local. Specifying the local invoker in the proxy binding doesn't > work either. Consider standard WEB->EJB applications with no remote clients. > > While you can just block the port, it would be nice not to have to expend > resources listening on a port that is blocked. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
