Hello,
When the KameletBinding concept was introduced in camel-k, if was meant to
bind two Kamelets and nothing more, but over time we have added more
capabilities, like:
- support for processing steps to transform exchanges/messages
- support to address/source from different systems so the sourc
Hello,
I'm wondering if the term "slip" in the sense of "to move or proceed
smoothly and readily" [1], which is a synonym for "binding", could
represent the intentions and features in an adequate manner. So, maybe
something along the lines of "KameletSlip" or "Slip", maybe?
One downside of this
Good afternoon. My name is Kiriil. I am Software Engineer on a Integration
project and we use Apache Camel.
We have some problem with NamedCassandraIdempotentRepository.
In my code we call the process inside the routing, then inside this process we
call the route builder which is responsibl
Hi Luca, Cameleers,
naming in IT... from the top of my head
Pipe
Processor
Conduit
Channel
Funnel
Queue
Glue
Caravan or Karavan I guess :)
None of these are particularly excellent, though we should pick a name
that describes the best but also doesn't increase the ambiguity or
cause confusion for
Maybe KameletPipe?
Il lun 16 ago 2021, 12:29 Zoran Regvart ha scritto:
> Hi Luca, Cameleers,
> naming in IT... from the top of my head
>
> Pipe
> Processor
> Conduit
> Channel
> Funnel
> Queue
> Glue
> Caravan or Karavan I guess :)
>
> None of these are particularly excellent, though we should p
Hi Luca, all,
+1 for Binding.
Users in the Kubernetes ecosystem may already be familiar with the term,
as it seems it's the choice made by projects like Knative and Service Binding,
to convey the general concept of "integrating" in their respective domain.
I find projecting that concept into the
Hi,
IMHO, we should create a Jira to add Karaf support for non existing
features.
I can work on it (using component private package or creating required
bundle).
@Gerald, can you please create a Jira about atlasmap ?
Thanks,
Regards
JB
On 13/08/2021 22:24, Gerald Kallas wrote:
Ah ok. Tx.
Hi All,
notice that camel-opentracing has downgraded the opentracing library from
0.33 to 0.31. https://issues.apache.org/jira/browse/CAMEL-15354
Is there any plan to upgrade that to 0.33?
Thanks and Regards,
Chio Chuan
Hi JB,
Sorry I am new to Karaf and Camel.
Could you explain about private package/bundle creation, and the usage of it to
make it work in Karaf?
Is it an update on both atlasmap and camel-atlasmap projects?
I saw you also commented in the Jira link below
https://issues.apache.org/jira/browse/
Hi,
It’s Karaf/OSGi specific. In OSGi, a bundle is a jar with additional headers
describing the packages that another bundle can use (because we have a graph of
class loaders in OSGi instead of a flat one).
So, when we have a Camel component, we have two options:
1. The camel component feature
10 matches
Mail list logo
