[jboss-remoting-issues] [JBoss JIRA] Commented: (JBREM-1079) Port fixes to ServletServerInvoker from branch 2.x to branch 2.2

[Ron Sigal (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBREM-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12467151#action_12467151 ] 

Ron Sigal commented on JBREM-1079:
----------------------------------

Applied changes from:

  * JBREM-675: Problems with Servlet invoker [unique ObjectName]

  * JBREM-728: Improve access to HTTP response headers

  * JBREM-809: Verify that the behavior of the HTTPUnMarshaller re stripping CR and LF characters is correct

  * JBREM-1114: Update servlet transport to support JBossMessaging

The related unit tests have been copied.

> 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