[
https://issues.apache.org/jira/browse/CAMEL-16449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dietrich Schulten updated CAMEL-16449:
--------------------------------------
Description:
It would be useful to make the current exchange available to custom
{{org.apache.camel.cloud.ServiceFilter}} implementations.
The service filter could use data from the current exchange to decide which
service instance is capable of handling the request.
It would probably also require to do something about
ServiceLoadBalancer.process because that is where the exchange would have to be
passed into the ServiceFilter.
Workaround: use a ThreadLocal to store the required data and access them from a
custom service filter.
was:
It would be useful to make the current exchange available to the
{{org.apache.camel.cloud.ServiceFilter}} interface.
The service filter could use data from the current exchange to decide which
service instance is capable of handling the request.
Workaround: use a ThreadLocal to store the required data and access them from a
custom service filter.
> Make Exchange available to ServiceFilter
> ----------------------------------------
>
> Key: CAMEL-16449
> URL: https://issues.apache.org/jira/browse/CAMEL-16449
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 3.9.0
> Reporter: Dietrich Schulten
> Priority: Major
>
> It would be useful to make the current exchange available to custom
> {{org.apache.camel.cloud.ServiceFilter}} implementations.
> The service filter could use data from the current exchange to decide which
> service instance is capable of handling the request.
> It would probably also require to do something about
> ServiceLoadBalancer.process because that is where the exchange would have to
> be passed into the ServiceFilter.
> Workaround: use a ThreadLocal to store the required data and access them from
> a custom service filter.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
