[jira] [Commented] (CAMEL-20104) camel-dynamic-router eip compnent: add option to return an exception on the exchange if a message is dropped.

["Steve Storck (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CAMEL-20104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17863041#comment-17863041 ] 

Steve Storck commented on CAMEL-20104:
--------------------------------------

[~davsclaus] I am pretty sure that I already took care of this, but I can check it out and make sure.  It'd be all right to close this.  If I see that there's something inadequate, I can always open another ticket, and if a user wants something different, we can work that out if they let us know.

> camel-dynamic-router eip compnent: add option to return an exception on the exchange if a message is dropped.
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-20104
>                 URL: https://issues.apache.org/jira/browse/CAMEL-20104
>             Project: Camel
>          Issue Type: Improvement
>          Components: eip
>            Reporter: Steve Storck
>            Assignee: Steve Storck
>            Priority: Minor
>
> {*}User Story{*}:
> As a routing participant that sends a message to the dynamic router, I need a way to know that a message that I have sent was not sent to any routing participants so that I can react/respond in an appropriate way, as deemed by my function in the system.
>  
> {*}Description{*}:
> The dynamic router eip component currently has an option for notification when a message is dropped if there are no routing participants that have registered rules that allow any of them to receive a message – it can log a message at the debug level by default, or it can be configured to log as a warning.  Since this is not ideal for notifying the sender of this issue, it would be helpful to let the message sender know that no recipients were available to receive the message.
>  
> {*}Approach{*}:
> The logging level for dropped messages is still probably useful, so that option can remain.  It would be a good idea to create another configuration option that allows the user to toggle returning an exception on the exchange when there are no appropriate routing participants to receive the message.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)