[
https://jira.jboss.org/jira/browse/JBAS-7563?page=com.atlassian.jira.plug...
]
Brian Stansberry commented on JBAS-7563:
----------------------------------------
From IRC re: WrapperDataSourceService:
<bstansberry> smarlow: is that tied to JRMP? or just to Invoker?
<bstansberry> smarlow: i.e. i suspect UnifiedInvoker is fine
<bstansberry> yeah, it takes a property named "JMXInvokerName" where
"JMXInvoker" means a legacy detached invoker that calls through the JMX bus
<bstansberry> UnifiedInvoker meets the requirements
<smarlow> well, it uses the Invoker interface but the comment mentions creating a
JRMPInvokerProxy
<bstansberry> where?
<smarlow> around line 273
<smarlow> bstansberry: line 273 of WrapperDataSourceService.java
<bstansberry> smarlow: ok, but it actually calls into GenericProxyFactory, which can
create a proxy that can deal with any legacy detached invoker
<bstansberry> a lot of code comments are from the early days when JRMP was the only
detached invoker
<smarlow> bstansberry: okay, so we should be good just updating the comment
<bstansberry> yes
Remove JRMPInvoker and JRMPInvokerHA
------------------------------------
Key: JBAS-7563
URL:
https://jira.jboss.org/jira/browse/JBAS-7563
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Other
Reporter: Brian Stansberry
Assignee: Scott Marlow
Fix For: 6.0.0.CR1
UnifiedInvoker has been the default legacy invoker since 4.2; JRMP is legacy of legacy.
--
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