Claus Ibsen created CAMEL-27153:
-----------------------------------
Summary: camel-jbang - the check for a direct: endpoint that no
route consumes also runs in a folder under a parent project
Key: CAMEL-27153
URL: https://issues.apache.org/jira/browse/CAMEL-27153
Project: Camel
Issue Type: Bug
Components: camel-jbang
Reporter: Claus Ibsen
Assignee: Claus Ibsen
Fix For: 4.24.0
The validator and the write tools of the camel-jbang-mcp server report a
direct: or seda: endpoint that a route sends to and no route consumes
(CAMEL-24955). After a write, the note says that the route that consumes it is
not there yet, and how to add it in the same call.
The check says nothing when the folder is a part of a Maven or Gradle project,
as src/main/resources/camel is: the RouteBuilders under src/main/java are not
in the folder, so it cannot know what they consume. But the check treats a
folder as a part of a project when any parent folder has a pom.xml or a
build.gradle. So it also says nothing in a folder that camel run runs on its
own, such as the folder of an example in a repository with a pom.xml at its
root.
The local-model benchmark runs its examples in such folders
(~/workspace/camel-performance-tests has a pom.xml), so the note never came up
there. For example, in route-enrich-and-dedupe step 3 (r35), the model added a
wireTap to direct:audit and the route from direct:audit only in a later write.
In between, every order failed with "No consumers available on endpoint:
direct://audit". In r30 to r35, 6 failed step runs had errors at a send to a
direct: or seda: endpoint.
Fix: a folder is a part of a project only when it is under the src folder of
the nearest parent project. A folder elsewhere in that project is checked.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)