[
https://jira.jboss.org/jira/browse/JBAS-1458?page=com.atlassian.jira.plug...
]
Adrian Brock closed JBAS-1458.
------------------------------
Resolution: Out of Date
This issue is out-of-date, so I'm closing it.
As of 4.2.x EJB2 doesn't use the JRMP invoker,
it uses the UnifiedInvoker (JBAS-3950) which can be changed to use some other protocol
e.g. as per the feature request an "in memory transport".
The only thing that does use it is the jmx-invoker-service.xml which can be removed
or changed to use a different invoker, e.g. the "web" configuration in JBoss5
uses the
http invoker instead.
What is left of this feature request is now on JBAS-6071which would remove the legacy
invokers by default (they are only required for backwards compatibility when talking to
older versions of JBoss).
EJB containers require JRMP invoker
-----------------------------------
Key: JBAS-1458
URL:
https://jira.jboss.org/jira/browse/JBAS-1458
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: EJB2
Affects Versions: JBossAS-3.2.6 Final, JBossAS-3.2.7 Final, JBossAS-4.0.1 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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira