[
https://issues.apache.org/jira/browse/CAMEL-19151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17700675#comment-17700675
]
Eduard Gomoliako commented on CAMEL-19151:
------------------------------------------
Yes, I find it better this way as well. I'd suggest also considering the other
similar places to have the same behavior, so it's consistent throughout the
whole system.
Let me know if you'd need a hand with that, I can prepare the relevant pull
requests.
> The 'ignoreInvalidEndpoint' option isn't relevant for a static URI for
> WireTap component
> ----------------------------------------------------------------------------------------
>
> Key: CAMEL-19151
> URL: https://issues.apache.org/jira/browse/CAMEL-19151
> Project: Camel
> Issue Type: Bug
> Components: camel-core-processor
> Affects Versions: 3.20.2
> Reporter: Eduard Gomoliako
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 3.18.6, 3.20.3, 3.21.0, 4.0-M3, 4.0
>
>
> The 'ignoreInvalidEndpoint' option for the WireTap component has no effect on
> the non-dynamic endpoints.
> The worst thing is that there is no warning that the set option is going to
> be ignored.
> I'm not sure about the design decision here, but from the user point of view
> it's confusing and not what one can expect.
>
> My use case:
> I defined a route configuration that by default does some processing of the
> intercepted messages and also sends them to a preconfigured endpoint. In my
> design this endpoint is optional and a route for it could be defined only if
> the default processing isn't enough.
> But because the endpoint URI is static and the 'ignoreInvalidEndpoint' has no
> effect, I get the messages stuck in-flight.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
