Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dependency autoloading is not working correctly with YAML format #2098

Closed
bouskaJ opened this issue Mar 5, 2021 · 1 comment · Fixed by #2247
Closed

Dependency autoloading is not working correctly with YAML format #2098

bouskaJ opened this issue Mar 5, 2021 · 1 comment · Fixed by #2247
Milestone

Comments

@bouskaJ
Copy link
Contributor

bouskaJ commented Mar 5, 2021

I have the following integration

- route:
    id: "yaml"
    from: 
      uri: "cron:tab"
      parameters:
        schedule: "*+*+*+*+?"
    steps:
      - set-header:
          name: "m"
          constant: "string!"
      - set-body:
          simple: "Magic${header.m}"
      - to: 
          uri: "log:info"
          parameters:
            show-all: "false"

and I am getting

[1] 2021-03-05 07:36:05,734 ERROR [org.apa.cam.qua.mai.CamelMainRuntime] (main) Failed to start application: org.apache.camel.FailedToCreateRouteException: Failed to create route yaml at: >>> To[log:info?show-all=false] <<< in route: Route(yaml)[From[cron:tab?schedule=*+*+*+*+?] -> [SetHeader[... because of No endpoint could be found for: log://info?show-all=false, please check your classpath contains the needed Camel component jar.

from the integration log. The camel-log dependency is not loaded to the integration classpath.

if you write it in the classic - from form (source code follows), dependencies are picked, so I guess it's a problem with the - route format.

- from: 
    uri: "cron:tab"
    parameters:
      schedule: "*+*+*+*+?"
    steps:
    - set-header:
        name: "m"
        constant: "string!"
    - set-body:
        simple: "Magic${header.m}"
    - to: 
        uri: "log:info"
        parameters:
          show-all: "false"
@squakez
Copy link
Contributor

squakez commented Apr 28, 2021

I am going to have a look at this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants