Cannot find RestProducerFactory in Registry or as a Component to use"

[barius]

I'm trying to use Rest component like this file:

hello-rest.groovy

from('rest:get:hello')
    .to('direct:hello');

from('direct:hello')
    .to('rest:get:processor?host=localhost:8080');


from('rest:get:processor')
    .to('direct:processor')
    .to('log:info');

from('direct:processor')
    .setHeader(Exchange.CONTENT_TYPE, constant('text/plain'))
    .transform().simple('Hello World');

When I run the integration in either local mode or with run --dev, it fails with

"Cannot find RestProducerFactory in Registry or as a Component to use",

The full log:
error.txt

Not sure I'm using the syntax the correct way because I'm still learning Camel.
Also tried to add external dependencies like kamel local run --dependency camel-quarkus:camel-quarkus-rest with no effect.

I've read https://camel.apache.org/camel-quarkus/2.9.x/reference/extensions/rest.html and https://camel.apache.org/components/3.16.x/rest-component.html#_component_options and tried to add configuration with
restConfiguration().host('localhost:8080').component('http'); and it also didn't work :(

System info:

macOS 12.3.1
Camel K Client 1.9.1, 
Apache Maven 3.8.5 (3599d3414f046de2324203b78ddcf9b5e4388aa0)
Java version: 17.0.3.1, vendor: Oracle Corporation, runtime: /Library/Java/JavaVirtualMachines/jdk-17.0.3.1.jdk/Contents/Home

[barius]

Rest consumer works though :)

[davsclaus]

you can add camel-http as explicit dependency

Something along the line of in the CLI args

-d camel-http

See more at
https://camel.apache.org/camel-k/1.9.x/configuration/dependencies.html

[davsclaus]

And there is also a producerComponent I think in rest-dsl as the consumer and producer can be different. I am not aware if camel-k can detect this part of the code when it scans for camel JARs to include

[barius]

@davsclaus thx :)

-d camel-http reports

Error: Unexpected type for user-provided dependency: camel-http. Additional top-level dependencies are specified with the format:
<type>:<dependency-name>
where <type> is one of {bom|camel|camel-k|camel-quarkus|mvn|github}.

Looks like the args parsing has changed but this is not a big problem.

but -d camel:camel-http hit me in the head with failure while building project: exit status 1

just randomly testing the dependencies and found that
--dependency camel-quarkus:camel-quarkus-http
kinda works (not throwing exceptions on launch at least) :)

[davsclaus]

Oh yeah I thought first it was

-d camel:http

notice that its using colon

[barius]

yeah -d camel:http works :)

[davsclaus]

Ticket to update docs: #3291