[jboss-remoting-issues] [JBoss JIRA] Updated: (JBREM-1015) CLONE [JBREM-1014] - Support injection of socket factory class name into AbstractInvoker
Ron Sigal (JIRA)
jira-events at lists.jboss.org
Fri Jul 18 02:25:52 EDT 2008
[ https://jira.jboss.org/jira/browse/JBREM-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ron Sigal updated JBREM-1015:
-----------------------------
Fix Version/s: 2.4.0.SP1
(was: 2.2.2.SP9)
Affects Version/s: 2.4.0.GA (Pinto)
(was: 2.2.2.SP8)
> CLONE [JBREM-1014] - Support injection of socket factory class name into AbstractInvoker
> ----------------------------------------------------------------------------------------
>
> Key: JBREM-1015
> URL: https://jira.jboss.org/jira/browse/JBREM-1015
> Project: JBoss Remoting
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Affects Versions: 2.4.0.GA (Pinto)
> Reporter: Ron Sigal
> Assignee: Ron Sigal
> Fix For: 2.4.0.SP1
>
>
> It is intended that org.jboss.remoting.AbstractInvoker can accept the class name of a SocketFactory, using the parameter org.jboss.remoting.Remoting.SOCKET_FACTORY_NAME (actual value "socketFactory"). Unfortunately, the parameter name "socketFactory" conflicts with the bean property of the same name. In particular, the problem is that the method
> public void setSocketFactory(SocketFactory socketFactory)
> in AbstractInvoker expects a SocketFactory instead of a String.
--
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
More information about the jboss-remoting-issues
mailing list