[
https://issues.apache.org/jira/browse/CAMEL-3386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12969030#action_12969030
]
William Tam commented on CAMEL-3386:
------------------------------------
Hi Willem,
Even the interceptor chain is created dynamically, it created based on the
service endpoint configured in the route. However, you point is well taken
that we probably don't need to maintain client cache if we can set CXF's
Exchange.ENDPOINT_ADDRESS in the Request Context to override the address. I'll
look into removing the client cache.
The new property in Camel was created with the intention that it can be reused
by other component. So, that probably will stay.
Thanks.
> Support destination address override by CxfProvider and CxfrsProvider
> ---------------------------------------------------------------------
>
> Key: CAMEL-3386
> URL: https://issues.apache.org/jira/browse/CAMEL-3386
> Project: Camel
> Issue Type: New Feature
> Components: camel-cxf
> Reporter: William Tam
> Assignee: William Tam
> Priority: Minor
> Fix For: 2.6.0
>
> Attachments: CAMEL-3386.patch
>
>
> So far, users can only send requests to REST/SOAP service endpoints that have
> been explicitly defined in Camel routes. Sometimes, it is useful to override
> the destination address at runtime (eliminating the need of adding an
> explicit route or the need of knowing about "future" service endpoint
> deployment at the configuring time). The assumption is these service
> endpoints are identical but running at different locations. This feature can
> greatly simplify the route configuration if there are tens (or hundreds) of
> identical services to be invoked.
> With the included patch, CxfProvider and CxfrsProvider will honor the
> CamelDestinationOverrideUrl header and use the value as the target address.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
