[jira] [Updated] (CAMEL-6253) JettyToCxfRs proxy doesn't work

["Willem Jiang (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CAMEL-6253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Willem Jiang updated CAMEL-6253:
--------------------------------

    Attachment: CAMEL-6253.patch

As we are in the middle of camel 2.11.0 release. I just attached the patch for review.
                
> JettyToCxfRs proxy doesn't work
> -------------------------------
>
>                 Key: CAMEL-6253
>                 URL: https://issues.apache.org/jira/browse/CAMEL-6253
>             Project: Camel
>          Issue Type: Bug
>    Affects Versions: 2.10.4, 2.11.0
>            Reporter: Willem Jiang
>            Assignee: Willem Jiang
>         Attachments: CAMEL-6253.patch
>
>
> I'm working a testcase which is using Jetty component and CXFRS component to proxy the rest request just like this
> {code}
> <from uri="jetty://http://localhost:{{CXFTestSupport.port5}}/CxfRsRouterTest/route?matchOnUriPrefix=true&amp;bridgeEndpoint=true"/>
>        <!-- We can remove this configure as the CXFRS producer is using the HttpAPI by default -->
>        <setHeader headerName="CamelCxfRsUsingHttpAPI">
>          <constant>True</constant>        
>        </setHeader>
>        <to uri="cxfrs://bean://rsClient"/>
> {code}
> CXFRS producer is leverage the Exchange.HTTP_PATH to setup the request URL just like the Http producer does. But the Exchange.HTTP_PATH header which is set by http component is a full request path, which is not a relative path as the CXFRS producer wants. So JettyToCxfRs proxy doesn't work.
> To Fix this issue, we need aline the definition of Exchange.HTTP_PATH across the CAMEL components, and it could save us lots of time to build up a right HTTP request url if the header just means a relative path. BTW user can get the full request path by looking up the header with Exchange.HTTP_URI.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira