[jboss-user] [Remoting] - Re: About the usage of path in InvokerLocator

[ron.sigal@jboss.com]

Hi Daniel,

Note that org.jboss.remoting.transport.coyote.CoyoteInvoker is designed to accept input from a client other than org.jboss.remoting.transport.http.HTTPClientInvoker.  If it receives a message that is not an InvocationRequest, it will generate an InvocationRequest on the fly, in the method 


  |    protected InvocationRequest createNewInvocationRequest(RequestMap requestMap, ResponseMap responseMap,
  |                                                           Object payload)
  |    {
  |       // will try to use the same session id if possible to track
  |       String sessionId = getSessionId(requestMap);
  |       String subSystem = (String) requestMap.get(HEADER_SUBSYSTEM);
  | 
  |       InvocationRequest request = null;
  | 
  |       boolean isLeaseQueury = checkForLeaseQuery(requestMap);
  |       if(isLeaseQueury)
  |       {
  |          addLeaseInfo(responseMap);
  |          request = new InvocationRequest(sessionId, subSystem, "$PING$", null, responseMap, null);
  |       }
  |       else
  |       {
  |          request = new InvocationRequest(sessionId, subSystem, payload,
  |                                                         requestMap, responseMap, null);
  |       }
  |       return request;
  |    }
  | 

So if you can add a HEADER_SUBSYSTEM (actual value "subsystem") header to the HTTP request, it will be treated as the subsystem.

Does that help?

-Ron

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146043#4146043

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146043