[
https://issues.apache.org/jira/browse/CAMEL-3386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12969066#action_12969066
]
William Tam commented on CAMEL-3386:
------------------------------------
@Willem
I removed the client cache in CxfProducer as suggested. The client factory
bean cache in CxfrsProducer provider should probably stay. There is no easy
way to get at the request context. If we find a way, It is probably a back
door way. The factory bean cache is light weight (not caching the client
itself) and it uses SoftReference.
Committed revision 1043223.
> 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.
