[esb-issues] [JBoss JIRA] Commented: (JBESB-1836) JBossRemoting CoyoteInvoker not forwarding request Path or Query params to JBossRemotingGatewayListener

[Tom Fennelly (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBESB-1836?page=comments#action_12418093 ] 
            
Tom Fennelly commented on JBESB-1836:
-------------------------------------

I got a reply from Ron on this and just thought I'd add it here anyway....

--------------------------------------------------------------------------------------------------
Hi Tom,

I just took a look at the code (and used a debugger), and I think you're right.  [There's a lot of details about HTTPClientInvoker and CoyoteInvoker that I don't know or don't remember.]  In principle, it shouldn't be necessary to add the query and path to the InvocationRequest, since the ServerInvocationHandler can get the InvokerLocator from the ServerInvoker.  Of course, it's possible for the client to add stuff to it's own version of the InvokerLocator.

On the other hand, on the client side you can add anything you want to the InvocationRequest requestPayload.  If you call  
   public Object invoke(Object param, Map metadata) throws Throwable

then the InvocationRequest requestPayload is set to metadata.  So you could call InvokerLocator.getPath() and InvokerLocator.getParameters() to get the path and query parameters and put them in the metadata map.

Does that help?

-Ron 
--------------------------------------------------------------------------------------------------

> JBossRemoting CoyoteInvoker not forwarding request Path or Query params to JBossRemotingGatewayListener
> -------------------------------------------------------------------------------------------------------
>
>                 Key: JBESB-1836
>                 URL: http://jira.jboss.com/jira/browse/JBESB-1836
>             Project: JBoss ESB
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Transports
>    Affects Versions: 4.3
>            Reporter: Tom Fennelly
>             Fix For: 4.4
>
>
> You can see this by checking the contents of the requestPayload on the InvocationRequest (supplied through the ServerInvocationHandler.invoke method).

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