Hi
No and that is not the purpose of Camel K.
Camel K is a closed-world and opinionated runtime that dont support
such very unusual and special use cases.
But on the other hand, whatever you can do from the configure() method
in a RouteBuilder is surfaced to the end user, so you can from there,
Hi,
You can use ActiveMQ with persistent message between routes, it creates kind of
resilience.
It’s what I’m doing with most of my users/projects. It allows to resume and
persist.
Regards
JB
> Le 26 mai 2020 à 20:54, FabryProg a écrit :
>
> Camel and NiFi..
>
> I used both in
I have to incorporate a third party api in order to use the reactive
functionality of the api. I'm using spring boot with this third party jar, and
the starting point is the onNext() method that get invoked whenever an event
occurs. My question is how do I make the onNext() method as a
I guess you just need to assemble the ProcessorDefintion into a
CamelRoute with a CamelContext to run it in a JVM.
It's not good way to use these low level Camel APIs as there are too
much details you need to explore.
As we deploy the CamelRoute through Camel-K into K8s. It's more easy
that you
This might be a little wierd question. But, I was wondering if there is a
way to convert an object of org.apache.camel.model.ProcessorDefinition
object into an equivalent camel DSLs.
I have an application which constructs ProcessorDefinition object using low
level camel api's and create a camel
Camel and NiFi..
I used both in enterprise projects.
For common people both framework could be similar BUT there is a big
difference.
Resiliency level!
NiFi saves every message to disk to reach high consistency level.
In apache camel message are fast, light but volatile.
I forward a
Created ticket
https://issues.apache.org/jira/browse/CAMEL-15114
On Tue, May 26, 2020 at 7:19 PM Claus Ibsen wrote:
>
> On Tue, May 26, 2020 at 5:36 PM Ronny Aerts
> wrote:
> >
> > Hello Claus,
> >
> > No problem to create a ticket but still the exchange property
> > CamelCreatedTimestamp is
Hi Raymond
Thanks for sharing this with the Camel community.
I am adding a link to the blog from our articles web page
On Tue, May 26, 2020 at 8:14 AM ski n wrote:
>
> Wrote a tech blog on using Camel with Apache NiFi:
>
>
Hello Claus,
I have quite some trouble accepting your solution. The migration of spring dsl
camel 2 to camel 3 is already difficult and it's hard for me to accept that I
need to add a statement in more then 2000 routes.
Especially for functionality which disappeared in the new version.
On Tue, May 26, 2020 at 5:36 PM Ronny Aerts
wrote:
>
> Hello Claus,
>
> No problem to create a ticket but still the exchange property
> CamelCreatedTimestamp is NOT defined and handling a "long" is good but would
> not help in my case because getting the property returns null.
>
Yeah you would
Hello Claus,
No problem to create a ticket but still the exchange property
CamelCreatedTimestamp is NOT defined and handling a "long" is good but would
not help in my case because getting the property returns null.
--
Met vriendelijke groeten / Kind regards / Cordialement / Mit besten Grüßen,
On Tue, May 26, 2020 at 4:34 PM Ronny Aerts
wrote:
>
> Hello Claus,
>
> Changing into
>
> results in a "java.lang.IllegalArgumentException - Cannot find java.util.Date
> object at command: exchangeProperty.CamelCreatedTimestamp".
> Is this due to the fact that the exchange.created is now a
Hello camel community,
I'm taking my first steps in migrating from camel 2.25.1 to 3.0.0. Since
(nearly) all our camel routes (more then 2000) are written using spring dsl,
this migration is a very big job.
Our spring dsl routes regularly use external file scripting for doing some
"coding"
Hello camel community,
I’m taking my first steps in migrating from camel 2.25.1 to 3.0.0. Since
(nearly) all our camel routes (more then 2000) are written using spring dsl,
this migration is a very big job.
Our spring dsl routes regularly use external file scripting for doing some
“coding”
Hello Claus,
Changing into
results in a "java.lang.IllegalArgumentException - Cannot find java.util.Date
object at command: exchangeProperty.CamelCreatedTimestamp".
Is this due to the fact that the exchange.created is now a java.lang.Long?
A groovy
Hi
Its called exchangeProperty in the simple language - the old property
name was deprecated also for 2.x.
3.x
https://camel.apache.org/components/latest/languages/simple-language.html
2.x
https://camel.apache.org/components/2.x/languages/simple-language.html
On Tue, May 26, 2020 at 3:14 PM
Hello camel community,
I’m taking my first steps in migrating from camel 2.25.1 to 3.0.0. Since
(nearly) all our camel routes (more then 2000) are written using spring dsl,
this migration is a very big job.
Our spring dsl routes regularly use external file scripting for doing some
“coding”
Hello camel community,
I’m taking my first steps in migrating from camel 2.25.1 to 3.0.0. Since
(nearly) all our camel routes (more then 2000) are written using spring dsl,
this migration is a very big job.
One of the things I notice is the missing CamelCreatedTimestamp exchange
property. We
Hi users
Hope you can help me with a problem i have with camel-ldif.When i try to
modify one object in the AD it works fine but when i have two modify
objects i get:
LdifReader.parseModify: ERR_12042_BAD_MODIFY_SEPARATOR_2 Bad state : we
should have come from a MOD_SPEC or an ATTRVAL_SPEC, at
Wrote a tech blog on using Camel with Apache NiFi:
https://medium.com/@raymondmeester/using-camel-and-nifi-in-one-solution-c7668fafe451
I thought I share it here,
Raymond
20 matches
Mail list logo
