[jboss-remoting-issues] [JBoss JIRA] Closed: (JBREM-1114) Update servlet transport to support JBossMessaging

[Ron Sigal (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBREM-1114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ron Sigal closed JBREM-1114.
----------------------------

    Resolution: Done


Updated Remoting Guide.

> Update servlet transport to support JBossMessaging
> --------------------------------------------------
>
>                 Key: JBREM-1114
>                 URL: https://jira.jboss.org/jira/browse/JBREM-1114
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.5.0.SP2 (Flounder) 
>            Reporter: Ron Sigal
>            Assignee: Ron Sigal
>             Fix For: 2.5.0.SP3 (Flounder)
>
>
> In working on JBMESSAGING-1131 "Add configuration for Remoting servlet transport" and JBPAPP-1274 "Fix JBoss Messaging and JBoss Remoting so that servlet transport can be used", a couple of issues arose.
> 1. If the body of the request is null, a new InvocationRequest will be created.
> 2. javax.servlet.http.HttpServletRequest.getParameterMap() returns a map with keys of type String and values of type String[].  Currently, ServletServerInvoker just extracts the String[] values and passes them along in a metadata map.  It is better, in the case of a String arrays of length one, to extract the value in the array.

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