[jboss-jira] [JBoss JIRA] Closed: (JBREM-298) Need ability to add transport specific info to invocation payload

[Ron Sigal (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBREM-298?page=all ]

Ron Sigal closed JBREM-298.
---------------------------

    Resolution: Done

This issue was resolved by creating a framework in which socket factory wrappers can be configured to inform an org.jboss.remoting.socketfactory.SocketCreationListener whenever a socket has been created.  For further discussion, see either the forum thread (http://www.jboss.com/index.html?module=bb&op=viewtopic&t=75901) or the Remoting documentation.

Unit tests:

org.jboss.test.remoting.transport.<transport>.socketfactory.<transport>CreationListenerTestCase, for <transport> = bisocket, multiplex, rmi, socket

org.jboss.test.remoting.transport.<transport>.ssl.socketfactory.SSL<transport>CreationListenerTestCase, for <transport> = bisocket, multiplex, rmi, socket

org.jboss.test.remoting.transport.http.ssl.socketfactory.HttpsCreationListenerTestCase


> Need ability to add transport specific info to invocation payload
> -----------------------------------------------------------------
>
>                 Key: JBREM-298
>                 URL: http://jira.jboss.com/jira/browse/JBREM-298
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: transport
>    Affects Versions: 1.4.0 beta
>            Reporter: Tom  Elrod
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> Specific example would be to add ssl client cert from the ssl socket to the invocation payload.

-- 
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira