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 2023/03/15 09:33:00 UTC
[jira] [Resolved] (CAMEL-19151) The 'ignoreInvalidEndpoint' option isn't relevant for a static URI for WireTap component
[ https://issues.apache.org/jira/browse/CAMEL-19151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-19151.
---------------------------------
Resolution: Not A Bug
Invalid endpoints is supposed for dynamic uris only.
If you have static urls then they are intended to be correct and valid.
> 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
> Priority: Minor
>
> 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)