Hi Shiva,
Not sure what Producer you're talking about but you might want to check out
the isSingleton property [1] on some Producers/Endpoints which affects
instance creation (returning true will only create one).
Hope this helps,
John.
[1]
Hello Philipp! Welcome!
If I'm reading this correctly, you are setting the "queryEngine" header to
simple("${in.header.JMSDestination}" which at runtime will translate to
a org.apache.activemq.command.ActiveMQQueue object I believe. This will get
dropped by Camel [1]. You can verify this by
Sure you can check [1] for and example, thanks!
[1]
https://github.com/apache/camel/blob/b9a3117f19dd19abd2ea8b789c42c3e86fe4c488/components/camel-fhir/camel-fhir-component/src/test/java/org/apache/camel/component/fhir/FhirCustomClientConfigurationIT.java#L63
On Tue, Jun 25, 2019 at 7:42 AM
ocessor, and then break on the next
> invocation of
> https://github.com/apache/camel/blob/789f1b26cf8b5ce7e40741c1236c3e1622c3550d/components/camel-fhir/camel-fhir-component/src/main/java/org/apache/camel/component/fhir/FhirComponent.java#L52,
> we are seeing the FhirConfiguration.client field b
Hi Paw, I'm not sure why you're trying to set the custom IGenericClient
through the Camel header; I'd need more info on your requirements. If you
can link to a github project or whatnot that'd be great.
As stated, you can set the custom client in your route URI directly [1]
referencing your bean
Hello everyone,
Matej and I have been working on Windup rules [0] to help people estimate
their migration from Camel 2 to Camel 3. When the tool is run it will
generate a report listing the different issues and assign story points to
each issue. Here are some sample reports for source codes of
Hi Andriy, can you try specifying the method you want to call in you route
i.e
.bean(positionMapItem, "map") ? Thanks !
On Tue, May 19, 2020 at 8:00 PM Andriy Klymenko
wrote:
> Hi,
>
>
>
> We use Camel 2 in our project for more than 3 years.
>
> Recently we decided to migrate to *Camel 3* but
+1 for Binding
Dropping the Kamelet part makes it clearer that you can bind more
than just Kamelets.
Keeping it as "Binding" gives Kubernetes users a pretty good idea of what
it's going to do without reading the documentation.
On Mon, Aug 16, 2021 at 2:04 PM Antonin Stefanutti
wrote:
> Hi
Hi Michael,
Is your Maven repository http://localserver:8081/ accessible from the
camel-k operator pod ? Logs from the operator pod might help troubleshoot.
Alternatively, as of camel-k v1.9.0, you can use local dependencies
directly from the run command:
kamel run integration.java -d
+1 (non-binding) - tested the local dependencies stuff
Thanks Andrea for releasing!
On Tue, May 17, 2022 at 11:29 AM Andrea Cosentino wrote:
> Hello all:
>
> This is a combined vote to release Apache Camel K 1.9.2.
>
> This is a patch release fixing an issue with OLM installation and Kamelets
A good starting point is the old component
https://github.com/apache/camel/tree/camel-3.22.1/components/camel-cdi
which is an information gold mine for camel+CDI
On Wed, Feb 14, 2024 at 2:12 PM Romain Manni-Bucau
wrote:
> Hi
>
> if it helps:
>
> @ApplicationScoped
> public class CamelLifecycle
11 matches
Mail list logo