[jboss-remoting-issues] [JBoss JIRA] Commented: (JBREM-1014) Support injection of socket factory class name into AbstractInvoker
Ron Sigal (JIRA)
jira-events at lists.jboss.org
Fri Jul 18 03:12:52 EDT 2008
[ https://jira.jboss.org/jira/browse/JBREM-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12421793#action_12421793 ]
Ron Sigal commented on JBREM-1014:
----------------------------------
Added new parameter, org.jboss.remoting.Remoting.SOCKET_FACTORY_CLASS_NAME (actual value "socketFactoryClassName"), which to replace Remoting.SOCKET_FACTORY_NAME (which still exists).
Unit test: org.jboss.test.remoting.transport.socket.socketfactory.SocketFactoryClassNameTestCase.
> Support injection of socket factory class name into AbstractInvoker
> -------------------------------------------------------------------
>
> Key: JBREM-1014
> URL: https://jira.jboss.org/jira/browse/JBREM-1014
> Project: JBoss Remoting
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Affects Versions: 2.2.2.SP8
> Reporter: Ron Sigal
> Assignee: Ron Sigal
> Fix For: 2.2.2.SP9
>
>
> 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