[jboss-remoting-issues] [JBoss JIRA] Closed: (JBREM-975) Make sure all fixes on 2.2 branch are applied to 2.x branch

[Ron Sigal (JIRA)]

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

Ron Sigal closed JBREM-975.
---------------------------

    Resolution: Done

The following issues have been updated with fix version 2.4.0.Beta1, which reflects when the changes were applied to branch 2.x:

[JBREM-653] - allow user to set content-type for http responses
[JBREM-732] - When server terminates and has clients, when the server comes back up clients that survived, can't connect.  Connection refused when trying to connect the control socket.
[JBREM-734] - BisocketClientInvoker constructor should get parameters from InvokerLocator as well as configuration map.
[JBREM-741] - Eliminate unnecessary log.warn() in BisocketServerInvoker
[JBREM-748] - BisocketClientInvoker should guard agains scheduling on an expired Timer
[JBREM-750] - Logger in HTTPClientInvoker should be static.
[JBREM-751] - Eliminate unnecessary "Unable to process control connection:" message from BisocketServerInvoker
[JBREM-757] - Implement quick Client.removeListener() for polled callbacks.
[JBREM-761] - NPE in BisocketServerInvoker$ControlConnectionThread

> Make sure all fixes on 2.2 branch are applied to 2.x branch
> -----------------------------------------------------------
>
>                 Key: JBREM-975
>                 URL: http://jira.jboss.com/jira/browse/JBREM-975
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.GA
>
>


-- 
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