[jboss-remoting-issues] [JBoss JIRA] Closed: (JBREM-1079) Port fixes to ServletServerInvoker from branch 2.x to branch 2.2
Ron Sigal (JIRA)
jira-events at lists.jboss.org
Wed May 13 04:01:46 EDT 2009
[ https://jira.jboss.org/jira/browse/JBREM-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ron Sigal closed JBREM-1079.
----------------------------
Resolution: Done
> Port fixes to ServletServerInvoker from branch 2.x to branch 2.2
> ----------------------------------------------------------------
>
> Key: JBREM-1079
> URL: https://jira.jboss.org/jira/browse/JBREM-1079
> Project: JBoss Remoting
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Affects Versions: 2.2.2.SP11
> Reporter: Ron Sigal
> Assignee: Ron Sigal
> Fix For: 2.2.3
>
>
> The servlet transport is getting increased use, as demonstrated by JIRA issue JBPAPP-1274 "Fix JBoss Messaging and JBoss Remoting so that servlet transport can be used" and the current attention to JBMESSAGING-1131 "Add configuration for Remoting servlet transport". Some of the changes made for
> * JBREM-675 "Problems with Servlet invoker"
> * JBREM-838 "allow user to set content-type for http responses (part 2: ServletServerInvoker)"
> * JBREM-853 "ServletServerInvoker should not put null URL path in metadata map"
> should be ported to the 2.2 branch for the version of Remoting used in EAP 4.2/4.3.
--
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