[jboss-jira] [JBoss JIRA] Created: (JBREM-636) Remove ServerInvokerCallbackHandler's dependence on initial InvocationRequest for listerner id.

[Ron Sigal (JIRA)]

Remove ServerInvokerCallbackHandler's dependence on initial InvocationRequest for listerner id.
-----------------------------------------------------------------------------------------------

                 Key: JBREM-636
                 URL: http://jira.jboss.com/jira/browse/JBREM-636
             Project: JBoss Remoting
          Issue Type: Task
      Security Level: Public (Everyone can see)
    Affects Versions:  2.2.0.Beta1 (Bluto)
            Reporter: Ron Sigal
         Assigned To: Ron Sigal
            Priority: Minor
             Fix For:  2.2.0.Beta1 (Bluto)


Currently, ServerInvokerCallbackHandler is initialized with the InvocationRequest that led to its creation, and thereafter, whenever the ServerInvokerCallbackHandler's id (which is the sessionId plus optional listenerId) is needed, the requestPayload map of the InvocationRequest is queried for the sessionId and listenerId.  The problem is that in the http transport, CoyoteInvoker creates a requestPayload map which is partially backed by the org.apache.coyote.Request, which is subject to change from invocation to invocation.

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