You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2022/09/02 10:49:00 UTC
[jira] [Resolved] (CAMEL-11521) Components with destination override via header should allow this override to be in message history / error handler
[ https://issues.apache.org/jira/browse/CAMEL-11521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-11521.
---------------------------------
Resolution: Won't Fix
> Components with destination override via header should allow this override to be in message history / error handler
> -------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-11521
> URL: https://issues.apache.org/jira/browse/CAMEL-11521
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: Claus Ibsen
> Priority: Minor
> Fix For: Future
>
>
> See this SO
> https://stackoverflow.com/questions/44963186/camel-kafka-logging-incorrect-details-in-messagehistory
> We can maybe have some kind of standard way for a component to say that its sending a message to an override destination than given in the endpoint uri, such as CamelJmsDestination, HttpUrl, HttpPath, CamelKafkaTopic etc.
> By knowing this we can make the message history, error handler aware of this and output additional information about this destination was in use.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)