date:20200526

camel-ldif component problem

2020-05-26 Thread Daniel Johansson

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 line 5

here is the LDIF that i send as a body with
.setBody(constant(ldifString.toString())) in my route:

ldifString.append("version: 1\n"
+ "\n"
+ "dn: CN=Testobjekt3, OU=Testusers, OU=LFV_Managed,
DC=lfv, DC=se\n"
+ "changetype: modify\n"
+ "add: telephoneNumber\n"
+ "telephoneNumber: +46103033906\n"
+ "\n"
+ "dn: CN=Testobjekt5, OU=Testusers, OU=LFV_Managed,
DC=lfv, DC=se\n"
+ "changetype: modify\n"
+ "add: telephoneNumber\n"
+ "telephoneNumber: +46103033908\n"
+ "-");

i use apache camel v 2.23.2 and camel-ldif version
2.23.2.fuse-740011-redhat-1

Can you see some obvious problem? I have really tried to read the rfc and
to make it correct.
https://www.ietf.org/rfc/rfc2849.txt

Thanks
/Daniel

CamelCreatedTimestamp exchange property does not seem to be present anymore in camel 3.3.0

2020-05-26 Thread Ronny Aerts

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 do a lot of things like the one below and that is not possible 
anymore without the CamelCreatedTimestamp.



...



I know that the context of the property corresponds to "exchange.getCreated()" 
but this statement is not available in spring dsl.

I know that I can replace the "property.CamelCreatedTimestamp" by "now" but 
then the "end of route" values is not the same as the "start of route" value.

Is there any workaround available for my problem.

--
Met vriendelijke groeten / Kind regards / Cordialement / Mit besten Grüßen,

Ronny AERTS
Product Owner Integrations / Integrations Manager
e: mailto:ronny.ae...@wisetechglobal.com  |  t: +32 (0) 3 326 50 75
https://www.linkedin.com/in/ronnyaerts/
https://www.intris.be/ / https://www.wisetechglobal.com/ | Empowering and 
enabling the logistics industry globally.
This email is subject to our 
http://www.wisetechglobal.com/ConfidentialityStatement.html




Intris nv   Wapenstilstandlaan 47   B-2600 Berchem

DISCLAIMER
This is an e-mail from Intris. The information contained in this communication 
is intended solely for use by the individual or entity to whom it is addressed.
Use of this communication by others is prohibited. If the e-mail message was 
sent to you by mistake, please notify 
intris.supp...@wisetechglobal.com, 
destroy it without reading, using, copying or disclosing its contents to any 
other person.
We accept no liability for damage related to data and/or documents which are 
communicated by electronic mail.

how to use global camel context properties in camel 3.3.0 groovy external script file

2020-05-26 Thread Ronny Aerts

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” things. Until now, we used javascript for those scripting
requirements. Javascript is not supported anymore in camel3 (and newer java
versions) and therefore we will switch to groovy as scripting language.

I have several scripts where I need to access global camel context properties.
In javascript, I did a properties.resolve("tris.dlq.mailer.to") call to resolve
the properties. The
https://camel.apache.org/components/latest/languages/groovy-language.html shows
that the properties (as org.apache.camel.builder.script.PropertiesFunction) are
passed to the external groovy file but I does not seems to work. A display of
the groovy properties variables shows something like “{class=class
Script_8adfd05454ebe3bbb0f3980896103164, binding=groovy.lang.Binding@62787393}”
of type java.util.LinkedHashMap.
Examining the content of the “binding” also proves that there is no
“properties” available.

The question I have for the community is how to work with global camel context
properties in groovy.

Possible solutions could be:
1. value =
camelContext.getPropertiesComponent().resolveProperty("tris.dlq.mailer.to").get();
⇒ gives a good result
2. value = camelContext.globalOptions.get("tris.dlq.mailer.to"); ⇒ gives a good
result
3. value =
org.apache.camel.builder.Builder.simple("properties:tris.dlq.mailer.to").evaluate(exchange,
java.lang.String.class); ⇒ gives “properties:tris.dlq.mailer.to” as result and
is not good
4. value =
org.apache.camel.builder.Builder.simple("${properties:tris.dlq.mailer.to}").evaluate(exchange,
java.lang.String.class); ⇒ gives a “No such property: tris for class:
Script_56c358fac7b1c2c9df318d99c84d4670” error message.
The first option seems to be the best because it also supports default values.
--
Met vriendelijke groeten / Kind regards / Cordialement / Mit besten Grüßen,

Ronny AERTS
Product Owner Integrations / Integrations Manager
e: mailto:ronny.ae...@wisetechglobal.com | t: +32 (0) 3 326 50 75
https://www.linkedin.com/in/ronnyaerts/
https://www.intris.be/ / https://www.wisetechglobal.com/ | Empowering and
enabling the logistics industry globally.
This email is subject to our
http://www.wisetechglobal.com/ConfidentialityStatement.html

Intris nv Wapenstilstandlaan 47 B-2600 Berchem

DISCLAIMER
This is an e-mail from Intris. The information contained in this communication
is intended solely for use by the individual or entity to whom it is addressed.
Use of this communication by others is prohibited. If the e-mail message was
sent to you by mistake, please notify
intris.supp...@wisetechglobal.com,
destroy it without reading, using, copying or disclosing its contents to any
other person.
We accept no liability for damage related to data and/or documents which are
communicated by electronic mail.

Re: CamelCreatedTimestamp exchange property does not seem to be present anymore in camel 3.3.0

2020-05-26 Thread Claus Ibsen

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 Ronny Aerts
 wrote:
>
> 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 do a lot of things like the one below and that is not possible 
> anymore without the CamelCreatedTimestamp.
> 
> 
> 
> ...
> 
> 
>
> I know that the context of the property corresponds to 
> "exchange.getCreated()" but this statement is not available in spring dsl.
>
> I know that I can replace the "property.CamelCreatedTimestamp" by "now" but 
> then the "end of route" values is not the same as the "start of route" value.
>
> Is there any workaround available for my problem.
>
> --
> Met vriendelijke groeten / Kind regards / Cordialement / Mit besten Grüßen,
>
> Ronny AERTS
> Product Owner Integrations / Integrations Manager
> e: mailto:ronny.ae...@wisetechglobal.com  |  t: +32 (0) 3 326 50 75
> https://www.linkedin.com/in/ronnyaerts/
> https://www.intris.be/ / https://www.wisetechglobal.com/ | Empowering and 
> enabling the logistics industry globally.
> This email is subject to our 
> http://www.wisetechglobal.com/ConfidentialityStatement.html
>
>
>
>
> Intris nv   Wapenstilstandlaan 47   B-2600 Berchem
>
> DISCLAIMER
> This is an e-mail from Intris. The information contained in this 
> communication is intended solely for use by the individual or entity to whom 
> it is addressed.
> Use of this communication by others is prohibited. If the e-mail message was 
> sent to you by mistake, please notify 
> intris.supp...@wisetechglobal.com, 
> destroy it without reading, using, copying or disclosing its contents to any 
> other person.
> We accept no liability for damage related to data and/or documents which are 
> communicated by electronic mail.



-- 
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

RE: CamelCreatedTimestamp exchange property does not seem to be present anymore in camel 3.3.0

2020-05-26 Thread Ronny Aerts

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 exchange.getProperty("CamelCreatedTimestamp") return a null.

--
Met vriendelijke groeten / Kind regards / Cordialement / Mit besten Grüßen,

Ronny AERTS
Product Owner Integrations / Integrations Manager




e: ronny.ae...@wisetechglobal.com  |  t: +32 (0) 3 326 50 75
 https://www.linkedin.com/in/ronnyaerts/
intris.be / wisetechglobal.com | Empowering and enabling the logistics industry 
globally.
This email is subject to our Confidentiality Statement


-Original Message-
From: Claus Ibsen 
Sent: Tuesday, 26 May 2020 16:07
To: users@camel.apache.org
Subject: Re: CamelCreatedTimestamp exchange property does not seem to be 
present anymore in camel 3.3.0

Hi

Its called exchangeProperty in the simple language - the old property name was 
deprecated also for 2.x.

3.x
https://urldefense.com/v3/__https://camel.apache.org/components/latest/languages/simple-language.html__;!!Na5NE8kfbMIR6Ys!6ke8h_4LiSin2gHySqFVPoznhQUTsWZChIq-IQPoVOnFzKBJXxAKaZn0_iB_IDheA7NFN8g$

2.x
https://urldefense.com/v3/__https://camel.apache.org/components/2.x/languages/simple-language.html__;!!Na5NE8kfbMIR6Ys!6ke8h_4LiSin2gHySqFVPoznhQUTsWZChIq-IQPoVOnFzKBJXxAKaZn0_iB_IDhepyDCZkM$

On Tue, May 26, 2020 at 3:14 PM Ronny Aerts  
wrote:
>
> 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 do a lot of things like the one below and that is not possible 
> anymore without the CamelCreatedTimestamp.
>   uri="timer://test.exception.standard.scheduler?repeatCount=1" />  message="start of route
> (${date:property.CamelCreatedTimestamp:-MM-dd-HH:mm:ss.SSS})" /> ...
> 
> 
>
> I know that the context of the property corresponds to 
> "exchange.getCreated()" but this statement is not available in spring dsl.
>
> I know that I can replace the "property.CamelCreatedTimestamp" by "now" but 
> then the "end of route" values is not the same as the "start of route" value.
>
> Is there any workaround available for my problem.
>
> --
> Met vriendelijke groeten / Kind regards / Cordialement / Mit besten
> Grüßen,
>
> Ronny AERTS
> Product Owner Integrations / Integrations Manager
> e: mailto:ronny.ae...@wisetechglobal.com  |  t: +32 (0) 3 326 50 75
> https://urldefense.com/v3/__https://www.linkedin.com/in/ronnyaerts/__;
> !!Na5NE8kfbMIR6Ys!6ke8h_4LiSin2gHySqFVPoznhQUTsWZChIq-IQPoVOnFzKBJXxAK
> aZn0_iB_IDhe5aI4ils$ https://www.intris.be/ /
> https://www.wisetechglobal.com/ | Empowering and enabling the logistics 
> industry globally.
> This email is subject to our
> http://www.wisetechglobal.com/ConfidentialityStatement.html
>
>
>
>
> Intris nv   Wapenstilstandlaan 47   B-2600 Berchem
>
> DISCLAIMER
> This is an e-mail from Intris. The information contained in this 
> communication is intended solely for use by the individual or entity to whom 
> it is addressed.
> Use of this communication by others is prohibited. If the e-mail message was 
> sent to you by mistake, please notify 
> intris.supp...@wisetechglobal.com, 
> destroy it without reading, using, copying or disclosing its contents to any 
> other person.
> We accept no liability for damage related to data and/or documents which are 
> communicated by electronic mail.



--
Claus Ibsen
-
https://urldefense.com/v3/__http://davsclaus.com__;!!Na5NE8kfbMIR6Ys!6ke8h_4LiSin2gHySqFVPoznhQUTsWZChIq-IQPoVOnFzKBJXxAKaZn0_iB_IDheiuhjSRY$
  @davsclaus Camel in Action 2: 
https://urldefense.com/v3/__https://www.manning.com/ibsen2__;!!Na5NE8kfbMIR6Ys!6ke8h_4LiSin2gHySqFVPoznhQUTsWZChIq-IQPoVOnFzKBJXxAKaZn0_iB_IDhesl4LW74$


Intris nv   Wapenstilstandlaan 47   B-2600 Berchem

DISCLAIMER
This is an e-mail from Intris. The information contained in this communication 
is intended solely for use by the individual or entity to whom it is addressed.
Use of this communication by others is prohibited. If the e-mail message was 
sent to you by mistake, please notify 
intris.supp...@wisetechglobal.com, 
destroy it without reading, using, copying or disclosing its contents to any 
other person.
We accept no liability for damage related to data and/or documents which are 
communicated by electronic mail.

how to use global camel context properties in camel 3.3.0 groovy external script file

2020-05-26 Thread Ronny Aerts

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.

The question I have for the community is how to work with global camel context
properties in groovy.

Intris nv Wapenstilstandlaan 47 B-2600 Berchem

how to use global camel context properties in camel 3.3.0 groovy external script file

2020-05-26 Thread Ronny Aerts

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" things. Until now, we used javascript for those scripting 
requirements. Javascript is not supported anymore in camel3 (and newer java 
versions) and therefore we will switch to groovy as scripting language.

I have several scripts where I need to access global camel context properties. 
In javascript, I did a properties.resolve("tris.dlq.mailer.to") call to resolve 
the properties. The groovy language 
documentation
 shows that the properties (as 
org.apache.camel.builder.script.PropertiesFunction) are passed to the external 
groovy file but I does not seems to work. A display of the groovy properties 
variables shows something like "{class=class 
Script_8adfd05454ebe3bbb0f3980896103164, binding=groovy.lang.Binding@62787393}" 
of type java.util.LinkedHashMap.
Examining the content of the "binding" also proves that there is no 
"properties" available.

The question I have for the community is how to work with global camel context 
properties in groovy.

Possible solutions could be:

  1.  value = 
camelContext.getPropertiesComponent().resolveProperty("tris.dlq.mailer.to").get();
 ==> gives a good result
  2.  value = camelContext.globalOptions.get("tris.dlq.mailer.to"); ==> gives a 
good result
  3.  value = 
org.apache.camel.builder.Builder.simple("properties:tris.dlq.mailer.to").evaluate(exchange,
 java.lang.String.class); ==> gives "properties:tris.dlq.mailer.to" as result 
and is not good
  4.  value = 
org.apache.camel.builder.Builder.simple("${properties:tris.dlq.mailer.to}").evaluate(exchange,
 java.lang.String.class); ==> gives a "No such property: tris for class: 
Script_56c358fac7b1c2c9df318d99c84d4670" error message.
The first option seems to be the best because it also supports default values.
--
Met vriendelijke groeten / Kind regards / Cordialement / Mit besten Grüßen,

Ronny AERTS
Product Owner Integrations / Integrations Manager

[signature_1746717844]

[cid:image003.png@01D6334D.FA336960]
e: ronny.ae...@wisetechglobal.com  |  t: 
+32 (0) 3 326 50 75
[CE7884FF] https://www.linkedin.com/in/ronnyaerts/
intris.be / 
wisetechglobal.com | Empowering and enabling 
the logistics industry globally.
This email is subject to our Confidentiality 
Statement




Intris nv   Wapenstilstandlaan 47   B-2600 Berchem

DISCLAIMER
This is an e-mail from Intris. The information contained in this communication 
is intended solely for use by the individual or entity to whom it is addressed.
Use of this communication by others is prohibited. If the e-mail message was 
sent to you by mistake, please notify 
intris.supp...@wisetechglobal.com, 
destroy it without reading, using, copying or disclosing its contents to any 
other person.
We accept no liability for damage related to data and/or documents which are 
communicated by electronic mail.

Re: CamelCreatedTimestamp exchange property does not seem to be present anymore in camel 3.3.0

2020-05-26 Thread Claus Ibsen

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 java.lang.Long?
>

Ah yeah that is correct. We can make Camel support long also. You are
welcome to create a JIRA ticket.


> A groovy exchange.getProperty("CamelCreatedTimestamp") return a null.
>
> --
> Met vriendelijke groeten / Kind regards / Cordialement / Mit besten Grüßen,
>
> Ronny AERTS
> Product Owner Integrations / Integrations Manager
>
>
>
>
> e: ronny.ae...@wisetechglobal.com  |  t: +32 (0) 3 326 50 75
>  https://www.linkedin.com/in/ronnyaerts/
> intris.be / wisetechglobal.com | Empowering and enabling the logistics 
> industry globally.
> This email is subject to our Confidentiality Statement
>
>
> -Original Message-
> From: Claus Ibsen 
> Sent: Tuesday, 26 May 2020 16:07
> To: users@camel.apache.org
> Subject: Re: CamelCreatedTimestamp exchange property does not seem to be 
> present anymore in camel 3.3.0
>
> Hi
>
> Its called exchangeProperty in the simple language - the old property name 
> was deprecated also for 2.x.
>
> 3.x
> https://urldefense.com/v3/__https://camel.apache.org/components/latest/languages/simple-language.html__;!!Na5NE8kfbMIR6Ys!6ke8h_4LiSin2gHySqFVPoznhQUTsWZChIq-IQPoVOnFzKBJXxAKaZn0_iB_IDheA7NFN8g$
>
> 2.x
> https://urldefense.com/v3/__https://camel.apache.org/components/2.x/languages/simple-language.html__;!!Na5NE8kfbMIR6Ys!6ke8h_4LiSin2gHySqFVPoznhQUTsWZChIq-IQPoVOnFzKBJXxAKaZn0_iB_IDhepyDCZkM$
>
> On Tue, May 26, 2020 at 3:14 PM Ronny Aerts  
> wrote:
> >
> > 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 do a lot of things like the one below and that is not possible 
> > anymore without the CamelCreatedTimestamp.
> >   > uri="timer://test.exception.standard.scheduler?repeatCount=1" />  > message="start of route
> > (${date:property.CamelCreatedTimestamp:-MM-dd-HH:mm:ss.SSS})" /> ...
> > 
> > 
> >
> > I know that the context of the property corresponds to 
> > "exchange.getCreated()" but this statement is not available in spring dsl.
> >
> > I know that I can replace the "property.CamelCreatedTimestamp" by "now" but 
> > then the "end of route" values is not the same as the "start of route" 
> > value.
> >
> > Is there any workaround available for my problem.
> >
> > --
> > Met vriendelijke groeten / Kind regards / Cordialement / Mit besten
> > Grüßen,
> >
> > Ronny AERTS
> > Product Owner Integrations / Integrations Manager
> > e: mailto:ronny.ae...@wisetechglobal.com  |  t: +32 (0) 3 326 50 75
> > https://urldefense.com/v3/__https://www.linkedin.com/in/ronnyaerts/__;
> > !!Na5NE8kfbMIR6Ys!6ke8h_4LiSin2gHySqFVPoznhQUTsWZChIq-IQPoVOnFzKBJXxAK
> > aZn0_iB_IDhe5aI4ils$ https://www.intris.be/ /
> > https://www.wisetechglobal.com/ | Empowering and enabling the logistics 
> > industry globally.
> > This email is subject to our
> > http://www.wisetechglobal.com/ConfidentialityStatement.html
> >
> >
> >
> >
> > Intris nv   Wapenstilstandlaan 47   B-2600 Berchem
> >
> > DISCLAIMER
> > This is an e-mail from Intris. The information contained in this 
> > communication is intended solely for use by the individual or entity to 
> > whom it is addressed.
> > Use of this communication by others is prohibited. If the e-mail message 
> > was sent to you by mistake, please notify 
> > intris.supp...@wisetechglobal.com,
> >  destroy it without reading, using, copying or disclosing its contents to 
> > any other person.
> > We accept no liability for damage related to data and/or documents which 
> > are communicated by electronic mail.
>
>
>
> --
> Claus Ibsen
> -
> https://urldefense.com/v3/__http://davsclaus.com__;!!Na5NE8kfbMIR6Ys!6ke8h_4LiSin2gHySqFVPoznhQUTsWZChIq-IQPoVOnFzKBJXxAKaZn0_iB_IDheiuhjSRY$
>   @davsclaus Camel in Action 2: 
> https://urldefense.com/v3/__https://www.manning.com/ibsen2__;!!Na5NE8kfbMIR6Ys!6ke8h_4LiSin2gHySqFVPoznhQUTsWZChIq-IQPoVOnFzKBJXxAKaZn0_iB_IDhesl4LW74$
>
>
> Intris nv   Wapenstilstandlaan 47   B-2600 Berchem
>
> DISCLAIMER
> This is an e-mail from Intris. The information contained in this 
> communication is intended solely for use by the individual or entity to whom 
> it is addressed.
> Use of this communication by others is prohibited. If the e-mail message was 
> sent to you by mistake, please notify 
> intris.supp...@wisetechglobal.com, 
> destroy it without reading, using, copying or disclosing its contents to any 
> other person.
> We accept no liability for dam

RE: CamelCreatedTimestamp exchange property does not seem to be present anymore in camel 3.3.0

2020-05-26 Thread Ronny Aerts

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,

Ronny AERTS
Product Owner Integrations / Integrations Manager




e: ronny.ae...@wisetechglobal.com  |  t: +32 (0) 3 326 50 75
 https://www.linkedin.com/in/ronnyaerts/
intris.be / wisetechglobal.com | Empowering and enabling the logistics industry 
globally.
This email is subject to our Confidentiality Statement


-Original Message-
From: Claus Ibsen 
Sent: Tuesday, 26 May 2020 17:26
To: users@camel.apache.org
Subject: Re: CamelCreatedTimestamp exchange property does not seem to be 
present anymore in camel 3.3.0

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 java.lang.Long?
>

Ah yeah that is correct. We can make Camel support long also. You are
welcome to create a JIRA ticket.


> A groovy exchange.getProperty("CamelCreatedTimestamp") return a null.
>
> --
> Met vriendelijke groeten / Kind regards / Cordialement / Mit besten Grüßen,
>
> Ronny AERTS
> Product Owner Integrations / Integrations Manager
>
>
>
>
> e: ronny.ae...@wisetechglobal.com  |  t: +32 (0) 3 326 50 75
>  
> https://urldefense.com/v3/__https://www.linkedin.com/in/ronnyaerts/__;!!Na5NE8kfbMIR6Ys!4uRqqDXlx-3LnTkCIB5OJs-DmvPcapT4A0xanxaCNEkfsCfq9FpxcxpSj6kXDlgJq5SFTfM$
> intris.be / wisetechglobal.com | Empowering and enabling the logistics 
> industry globally.
> This email is subject to our Confidentiality Statement
>
>
> -Original Message-
> From: Claus Ibsen 
> Sent: Tuesday, 26 May 2020 16:07
> To: users@camel.apache.org
> Subject: Re: CamelCreatedTimestamp exchange property does not seem to be 
> present anymore in camel 3.3.0
>
> Hi
>
> Its called exchangeProperty in the simple language - the old property name 
> was deprecated also for 2.x.
>
> 3.x
> https://urldefense.com/v3/__https://camel.apache.org/components/latest/languages/simple-language.html__;!!Na5NE8kfbMIR6Ys!6ke8h_4LiSin2gHySqFVPoznhQUTsWZChIq-IQPoVOnFzKBJXxAKaZn0_iB_IDheA7NFN8g$
>
> 2.x
> https://urldefense.com/v3/__https://camel.apache.org/components/2.x/languages/simple-language.html__;!!Na5NE8kfbMIR6Ys!6ke8h_4LiSin2gHySqFVPoznhQUTsWZChIq-IQPoVOnFzKBJXxAKaZn0_iB_IDhepyDCZkM$
>
> On Tue, May 26, 2020 at 3:14 PM Ronny Aerts  
> wrote:
> >
> > 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 do a lot of things like the one below and that is not possible 
> > anymore without the CamelCreatedTimestamp.
> >   > uri="timer://test.exception.standard.scheduler?repeatCount=1" />  > message="start of route
> > (${date:property.CamelCreatedTimestamp:-MM-dd-HH:mm:ss.SSS})" /> ...
> > 
> > 
> >
> > I know that the context of the property corresponds to 
> > "exchange.getCreated()" but this statement is not available in spring dsl.
> >
> > I know that I can replace the "property.CamelCreatedTimestamp" by "now" but 
> > then the "end of route" values is not the same as the "start of route" 
> > value.
> >
> > Is there any workaround available for my problem.
> >
> > --
> > Met vriendelijke groeten / Kind regards / Cordialement / Mit besten
> > Grüßen,
> >
> > Ronny AERTS
> > Product Owner Integrations / Integrations Manager
> > e: mailto:ronny.ae...@wisetechglobal.com  |  t: +32 (0) 3 326 50 75
> > https://urldefense.com/v3/__https://www.linkedin.com/in/ronnyaerts/__;
> > !!Na5NE8kfbMIR6Ys!6ke8h_4LiSin2gHySqFVPoznhQUTsWZChIq-IQPoVOnFzKBJXxAK
> > aZn0_iB_IDhe5aI4ils$ https://www.intris.be/ /
> > https://www.wisetechglobal.com/ | Empowering and enabling the logistics 
> > industry globally.
> > This email is subject to our
> > http://www.wisetechglobal.com/ConfidentialityStatement.html
> >
> >
> >
> >
> > Intris nv   Wapenstilstandlaan 47   B-2600 Berchem
> >
> > DISCLAIMER
> > This is an e-mail from Intris. The information contained in this 
> > communication is intended solely for use by the individual or entity to 
> > whom it is addressed.
> > Use of this communication by others is prohibited. If the e-mail message 
> > was sent to you by mistake, please notify 
> > intris.supp...@wisetechglobal.com,
> >  destroy it without reading, using, copying or disclosing its contents to 
> > any other person.
> > We accept no liability for damage related to data and/or documents which 
> > are communicated by electronic m

Re: CamelCreatedTimestamp exchange property does not seem to be present anymore in camel 3.3.0

2020-05-26 Thread Claus Ibsen

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 need to store a new exchange property before (or
header) yourself with the timestamp that the simple date function can
use.

.setExchangeProperty("myCreated", simple("${exchange.created}"))



> --
> Met vriendelijke groeten / Kind regards / Cordialement / Mit besten Grüßen,
>
> Ronny AERTS
> Product Owner Integrations / Integrations Manager
>
>
>
>
> e: ronny.ae...@wisetechglobal.com  |  t: +32 (0) 3 326 50 75
>  https://www.linkedin.com/in/ronnyaerts/
> intris.be / wisetechglobal.com | Empowering and enabling the logistics 
> industry globally.
> This email is subject to our Confidentiality Statement
>
>
> -Original Message-
> From: Claus Ibsen 
> Sent: Tuesday, 26 May 2020 17:26
> To: users@camel.apache.org
> Subject: Re: CamelCreatedTimestamp exchange property does not seem to be 
> present anymore in camel 3.3.0
>
> 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 java.lang.Long?
> >
>
> Ah yeah that is correct. We can make Camel support long also. You are
> welcome to create a JIRA ticket.
>
>
> > A groovy exchange.getProperty("CamelCreatedTimestamp") return a null.
> >
> > --
> > Met vriendelijke groeten / Kind regards / Cordialement / Mit besten Grüßen,
> >
> > Ronny AERTS
> > Product Owner Integrations / Integrations Manager
> >
> >
> >
> >
> > e: ronny.ae...@wisetechglobal.com  |  t: +32 (0) 3 326 50 75
> >  
> > https://urldefense.com/v3/__https://www.linkedin.com/in/ronnyaerts/__;!!Na5NE8kfbMIR6Ys!4uRqqDXlx-3LnTkCIB5OJs-DmvPcapT4A0xanxaCNEkfsCfq9FpxcxpSj6kXDlgJq5SFTfM$
> > intris.be / wisetechglobal.com | Empowering and enabling the logistics 
> > industry globally.
> > This email is subject to our Confidentiality Statement
> >
> >
> > -Original Message-
> > From: Claus Ibsen 
> > Sent: Tuesday, 26 May 2020 16:07
> > To: users@camel.apache.org
> > Subject: Re: CamelCreatedTimestamp exchange property does not seem to be 
> > present anymore in camel 3.3.0
> >
> > Hi
> >
> > Its called exchangeProperty in the simple language - the old property name 
> > was deprecated also for 2.x.
> >
> > 3.x
> > https://urldefense.com/v3/__https://camel.apache.org/components/latest/languages/simple-language.html__;!!Na5NE8kfbMIR6Ys!6ke8h_4LiSin2gHySqFVPoznhQUTsWZChIq-IQPoVOnFzKBJXxAKaZn0_iB_IDheA7NFN8g$
> >
> > 2.x
> > https://urldefense.com/v3/__https://camel.apache.org/components/2.x/languages/simple-language.html__;!!Na5NE8kfbMIR6Ys!6ke8h_4LiSin2gHySqFVPoznhQUTsWZChIq-IQPoVOnFzKBJXxAKaZn0_iB_IDhepyDCZkM$
> >
> > On Tue, May 26, 2020 at 3:14 PM Ronny Aerts 
> >  wrote:
> > >
> > > 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 do a lot of things like the one below and that is not 
> > > possible anymore without the CamelCreatedTimestamp.
> > >   > > uri="timer://test.exception.standard.scheduler?repeatCount=1" />  > > message="start of route
> > > (${date:property.CamelCreatedTimestamp:-MM-dd-HH:mm:ss.SSS})" /> ...
> > > 
> > > 
> > >
> > > I know that the context of the property corresponds to 
> > > "exchange.getCreated()" but this statement is not available in spring dsl.
> > >
> > > I know that I can replace the "property.CamelCreatedTimestamp" by "now" 
> > > but then the "end of route" values is not the same as the "start of 
> > > route" value.
> > >
> > > Is there any workaround available for my problem.
> > >
> > > --
> > > Met vriendelijke groeten / Kind regards / Cordialement / Mit besten
> > > Grüßen,
> > >
> > > Ronny AERTS
> > > Product Owner Integrations / Integrations Manager
> > > e: mailto:ronny.ae...@wisetechglobal.com  |  t: +32 (0) 3 326 50 75
> > > https://urldefense.com/v3/__https://www.linkedin.com/in/ronnyaerts/__;
> > > !!Na5NE8kfbMIR6Ys!6ke8h_4LiSin2gHySqFVPoznhQUTsWZChIq-IQPoVOnFzKBJXxAK
> > > aZn0_iB_IDhe5aI4ils$ https://www.intris.be/ /
> > > https://www.wisetechglobal.com/ | Empowering and enabling the logistics 
> > > industry globally.
> > > This email is subject to our
> > > http://www.wisetechglobal.com/ConfidentialityStatement.html
> > >
> > >
> > >
> > >
> > > Intris nv   Wapenstilstandlaan 47   B-2600 Berchem
> > >
> > > DISCLAIMER
> > > This is an e-mail from Intris. The information contained in this 
> > > comm

Re: CamelCreatedTimestamp exchange property does not seem to be present anymore in camel 3.3.0

2020-05-26 Thread Ronny Aerts

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.

vriendelijke groeten,
Ronny Aerts

Deze mail werd verstuurd via mijn mobiele telefoon.

From: Claus Ibsen 
Sent: Tuesday, May 26, 2020 7:19:49 PM
To: users@camel.apache.org 
Subject: Re: CamelCreatedTimestamp exchange property does not seem to be 
present anymore in camel 3.3.0

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 need to store a new exchange property before (or
header) yourself with the timestamp that the simple date function can
use.

.setExchangeProperty("myCreated", simple("${exchange.created}"))



> --
> Met vriendelijke groeten / Kind regards / Cordialement / Mit besten Grüßen,
>
> Ronny AERTS
> Product Owner Integrations / Integrations Manager
>
>
>
>
> e: ronny.ae...@wisetechglobal.com  |  t: +32 (0) 3 326 50 75
>  
> https://urldefense.com/v3/__https://www.linkedin.com/in/ronnyaerts/__;!!Na5NE8kfbMIR6Ys!4cllVnvJ1gsqp1B0AYAwxW0ahGDtGqnjeeYFw0R9UKIQHazjGz3_2aWH39Q9mOhxZLuInqg$
> intris.be / wisetechglobal.com | Empowering and enabling the logistics 
> industry globally.
> This email is subject to our Confidentiality Statement
>
>
> -Original Message-
> From: Claus Ibsen 
> Sent: Tuesday, 26 May 2020 17:26
> To: users@camel.apache.org
> Subject: Re: CamelCreatedTimestamp exchange property does not seem to be 
> present anymore in camel 3.3.0
>
> 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 java.lang.Long?
> >
>
> Ah yeah that is correct. We can make Camel support long also. You are
> welcome to create a JIRA ticket.
>
>
> > A groovy exchange.getProperty("CamelCreatedTimestamp") return a null.
> >
> > --
> > Met vriendelijke groeten / Kind regards / Cordialement / Mit besten Grüßen,
> >
> > Ronny AERTS
> > Product Owner Integrations / Integrations Manager
> >
> >
> >
> >
> > e: ronny.ae...@wisetechglobal.com  |  t: +32 (0) 3 326 50 75
> >  
> > https://urldefense.com/v3/__https://www.linkedin.com/in/ronnyaerts/__;!!Na5NE8kfbMIR6Ys!4uRqqDXlx-3LnTkCIB5OJs-DmvPcapT4A0xanxaCNEkfsCfq9FpxcxpSj6kXDlgJq5SFTfM$
> > intris.be / wisetechglobal.com | Empowering and enabling the logistics 
> > industry globally.
> > This email is subject to our Confidentiality Statement
> >
> >
> > -Original Message-
> > From: Claus Ibsen 
> > Sent: Tuesday, 26 May 2020 16:07
> > To: users@camel.apache.org
> > Subject: Re: CamelCreatedTimestamp exchange property does not seem to be 
> > present anymore in camel 3.3.0
> >
> > Hi
> >
> > Its called exchangeProperty in the simple language - the old property name 
> > was deprecated also for 2.x.
> >
> > 3.x
> > https://urldefense.com/v3/__https://camel.apache.org/components/latest/languages/simple-language.html__;!!Na5NE8kfbMIR6Ys!6ke8h_4LiSin2gHySqFVPoznhQUTsWZChIq-IQPoVOnFzKBJXxAKaZn0_iB_IDheA7NFN8g$
> >
> > 2.x
> > https://urldefense.com/v3/__https://camel.apache.org/components/2.x/languages/simple-language.html__;!!Na5NE8kfbMIR6Ys!6ke8h_4LiSin2gHySqFVPoznhQUTsWZChIq-IQPoVOnFzKBJXxAKaZn0_iB_IDhepyDCZkM$
> >
> > On Tue, May 26, 2020 at 3:14 PM Ronny Aerts 
> >  wrote:
> > >
> > > 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 do a lot of things like the one below and that is not 
> > > possible anymore without the CamelCreatedTimestamp.
> > >   > > uri="timer://test.exception.standard.scheduler?repeatCount=1" />  > > message="start of route
> > > (${date:property.CamelCreatedTimestamp:-MM-dd-HH:mm:ss.SSS})" /> ...
> > > 
> > > 
> > >
> > > I know that the context of the property corresponds to 
> > > "exchange.getCreated()" but this statement is not available in spring dsl.
> > >
> > > I know that I can replace the "property.CamelCreatedTimestamp" by "now" 
> > > but then the "end of route" values is not the same as the "start of 
> > > route" value.
> > >
> > > Is there any workaround available for my problem.
> > >
> > > --
> > > Met vriendelijke groeten / Kind regards / Cordialement / Mit besten
> > > Grüßen,
> > >
> > > Ronny AERTS

Re: CamelCreatedTimestamp exchange property does not seem to be present anymore in camel 3.3.0

2020-05-26 Thread Claus Ibsen

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 NOT defined and handling a "long" is good but 
> > would not help in my case because getting the property returns null.
> >
>
> Yeah you would need to store a new exchange property before (or
> header) yourself with the timestamp that the simple date function can
> use.
>
> .setExchangeProperty("myCreated", simple("${exchange.created}"))
>
>
>
> > --
> > Met vriendelijke groeten / Kind regards / Cordialement / Mit besten Grüßen,
> >
> > Ronny AERTS
> > Product Owner Integrations / Integrations Manager
> >
> >
> >
> >
> > e: ronny.ae...@wisetechglobal.com  |  t: +32 (0) 3 326 50 75
> >  https://www.linkedin.com/in/ronnyaerts/
> > intris.be / wisetechglobal.com | Empowering and enabling the logistics 
> > industry globally.
> > This email is subject to our Confidentiality Statement
> >
> >
> > -Original Message-
> > From: Claus Ibsen 
> > Sent: Tuesday, 26 May 2020 17:26
> > To: users@camel.apache.org
> > Subject: Re: CamelCreatedTimestamp exchange property does not seem to be 
> > present anymore in camel 3.3.0
> >
> > 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 java.lang.Long?
> > >
> >
> > Ah yeah that is correct. We can make Camel support long also. You are
> > welcome to create a JIRA ticket.
> >
> >
> > > A groovy exchange.getProperty("CamelCreatedTimestamp") return a null.
> > >
> > > --
> > > Met vriendelijke groeten / Kind regards / Cordialement / Mit besten 
> > > Grüßen,
> > >
> > > Ronny AERTS
> > > Product Owner Integrations / Integrations Manager
> > >
> > >
> > >
> > >
> > > e: ronny.ae...@wisetechglobal.com  |  t: +32 (0) 3 326 50 75
> > >  
> > > https://urldefense.com/v3/__https://www.linkedin.com/in/ronnyaerts/__;!!Na5NE8kfbMIR6Ys!4uRqqDXlx-3LnTkCIB5OJs-DmvPcapT4A0xanxaCNEkfsCfq9FpxcxpSj6kXDlgJq5SFTfM$
> > > intris.be / wisetechglobal.com | Empowering and enabling the logistics 
> > > industry globally.
> > > This email is subject to our Confidentiality Statement
> > >
> > >
> > > -Original Message-
> > > From: Claus Ibsen 
> > > Sent: Tuesday, 26 May 2020 16:07
> > > To: users@camel.apache.org
> > > Subject: Re: CamelCreatedTimestamp exchange property does not seem to be 
> > > present anymore in camel 3.3.0
> > >
> > > Hi
> > >
> > > Its called exchangeProperty in the simple language - the old property 
> > > name was deprecated also for 2.x.
> > >
> > > 3.x
> > > https://urldefense.com/v3/__https://camel.apache.org/components/latest/languages/simple-language.html__;!!Na5NE8kfbMIR6Ys!6ke8h_4LiSin2gHySqFVPoznhQUTsWZChIq-IQPoVOnFzKBJXxAKaZn0_iB_IDheA7NFN8g$
> > >
> > > 2.x
> > > https://urldefense.com/v3/__https://camel.apache.org/components/2.x/languages/simple-language.html__;!!Na5NE8kfbMIR6Ys!6ke8h_4LiSin2gHySqFVPoznhQUTsWZChIq-IQPoVOnFzKBJXxAKaZn0_iB_IDhepyDCZkM$
> > >
> > > On Tue, May 26, 2020 at 3:14 PM Ronny Aerts 
> > >  wrote:
> > > >
> > > > 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 do a lot of things like the one below and that is 
> > > > not possible anymore without the CamelCreatedTimestamp.
> > > >   > > > uri="timer://test.exception.standard.scheduler?repeatCount=1" />  > > > message="start of route
> > > > (${date:property.CamelCreatedTimestamp:-MM-dd-HH:mm:ss.SSS})" /> ...
> > > > 
> > > > 
> > > >
> > > > I know that the context of the property corresponds to 
> > > > "exchange.getCreated()" but this statement is not available in spring 
> > > > dsl.
> > > >
> > > > I know that I can replace the "property.CamelCreatedTimestamp" by "now" 
> > > > but then the "end of route" values is not the same as the "start of 
> > > > route" value.
> > > >
> > > > Is there any workaround available for my problem.
> > > >
> > > > --
> > > > Met vriendelijke groeten / Kind regards / Cordialement / Mit besten
> > > > Grüßen,
> > > >
> > > > Ronny AERTS
> > > > Product Owner Integrations / Integrations Manager
> > > > e: mailto:ronny.ae...@wisetechglobal.com  |  t: +32 (0) 3 326 50 75
> > > > https://urldefense.com/v3/__https://www.linkedin.com/in/ronnyaerts/__;
> > > > !!Na5NE8kfbMIR6Ys!6ke8h_4LiSin2gHySqFVPoznhQUTsWZChIq-IQPoVOnFzKBJXxAK
> > > > aZn0_iB_IDhe5aI4ils$ https://www.intris.be

Re: Camel & NiFi

2020-05-26 Thread Claus Ibsen

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:
>
> https://medium.com/@raymondmeester/using-camel-and-nifi-in-one-solution-c7668fafe451
>
> I thought I share it here,
>
> Raymond



-- 
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Re: Camel & NiFi

2020-05-26 Thread FabryProg

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 question to you. how to create the same resiliency level in
camel? How to save (and resume) the flow every restart?

Kind regards !!!

Fabrizio

Il Mar 26 Mag 2020, 20:32 Claus Ibsen  ha scritto:

> 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:
> >
> >
> https://medium.com/@raymondmeester/using-camel-and-nifi-in-one-solution-c7668fafe451
> >
> > I thought I share it here,
> >
> > Raymond
>
>
>
> --
> Claus Ibsen
> -
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>

Converting ProcessorDefinition to DSL and interfacing with camel k

2020-05-26 Thread Reji Mathews

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 context to start it in a jvm.

If there is a way to convert the same object into DSLs, I could possibly
think of hooking up with camel-k

Alternatively, does camel k have any interfacing to receive an object of
ProcessorDefinition object?

Cheers

Re: Converting ProcessorDefinition to DSL and interfacing with camel k

2020-05-26 Thread Willem Jiang

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 just use dumped camel route into XML and deploy it through
Camel-K.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Wed, May 27, 2020 at 9:20 AM Reji Mathews  wrote:
>
> 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 context to start it in a jvm.
>
> If there is a way to convert the same object into DSLs, I could possibly
> think of hooking up with camel-k
>
> Alternatively, does camel k have any interfacing to receive an object of
> ProcessorDefinition object?
>
> Cheers

reactive java question

2020-05-26 Thread Bing Lu

 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 starting point of 
my route, right now I have to build an exchange inside the onNext() method and 
calling methods from there instead of the normal from(...).to(...) route 
building functionality. How do I make the onnext() method as a starting point 
like from(...)?
thanks

Re: Camel & NiFi

2020-05-26 Thread Jean-Baptiste Onofre

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 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 question to you. how to create the same resiliency level in
> camel? How to save (and resume) the flow every restart?
> 
> Kind regards !!!
> 
> Fabrizio
> 
> Il Mar 26 Mag 2020, 20:32 Claus Ibsen  ha scritto:
> 
>> 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:
>>> 
>>> 
>> https://medium.com/@raymondmeester/using-camel-and-nifi-in-one-solution-c7668fafe451
>>> 
>>> I thought I share it here,
>>> 
>>> Raymond
>> 
>> 
>> 
>> --
>> Claus Ibsen
>> -
>> http://davsclaus.com @davsclaus
>> Camel in Action 2: https://www.manning.com/ibsen2
>>

Re: Converting ProcessorDefinition to DSL and interfacing with camel k

2020-05-26 Thread Claus Ibsen

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,
go grab xxxDefinition instances from somewhere,
and then build them on route(s). The Camel K operator does some
parsing of the code and if you do "strange" things it may not parse
accurately and if so then you need to be more specific of which Camel
JAR dependencies you use.

But I would also say that why... and maybe your existing app is not
suitable for these use cases.

On Wed, May 27, 2020 at 3:20 AM Reji Mathews  wrote:
>
> 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 context to start it in a jvm.
>
> If there is a way to convert the same object into DSLs, I could possibly
> think of hooking up with camel-k
>
> Alternatively, does camel k have any interfacing to receive an object of
> ProcessorDefinition object?
>
> Cheers

-- 
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Re: Camel & NiFi

2020-05-26 Thread FabryProg

Thanks.

I'll implements a mock example soon as possible.

Have a good day!

Fabrizio

Il Mer 27 Mag 2020, 06:13 Jean-Baptiste Onofre  ha scritto:

> 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 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 question to you. how to create the same resiliency level
> in
> > camel? How to save (and resume) the flow every restart?
> >
> > Kind regards !!!
> >
> > Fabrizio
> >
> > Il Mar 26 Mag 2020, 20:32 Claus Ibsen  ha
> scritto:
> >
> >> 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:
> >>>
> >>>
> >>
> https://medium.com/@raymondmeester/using-camel-and-nifi-in-one-solution-c7668fafe451
> >>>
> >>> I thought I share it here,
> >>>
> >>> Raymond
> >>
> >>
> >>
> >> --
> >> Claus Ibsen
> >> -
> >> http://davsclaus.com @davsclaus
> >> Camel in Action 2: https://www.manning.com/ibsen2
> >>
>
>

RE: CamelCreatedTimestamp exchange property does not seem to be present anymore in camel 3.3.0

2020-05-26 Thread Ronny Aerts

Hello Claus,

I saw the commits that solve my problem. Thank you for helping me out.

--
Met vriendelijke groeten / Kind regards / Cordialement / Mit besten Grüßen,

Ronny AERTS
Product Owner Integrations / Integrations Manager




e: ronny.ae...@wisetechglobal.com  |  t: +32 (0) 3 326 50 75
 https://www.linkedin.com/in/ronnyaerts/
intris.be / wisetechglobal.com | Empowering and enabling the logistics industry 
globally.
This email is subject to our Confidentiality Statement


-Original Message-
From: Claus Ibsen 
Sent: Tuesday, 26 May 2020 20:32
To: users@camel.apache.org
Subject: Re: CamelCreatedTimestamp exchange property does not seem to be 
present anymore in camel 3.3.0

Created ticket
https://urldefense.com/v3/__https://issues.apache.org/jira/browse/CAMEL-15114__;!!Na5NE8kfbMIR6Ys!59S7myqOQeKiBKA-3Gh8uVkFpzcYIUuf_pzUbxkGGMIZxxrP_VPG_eFQs_WGhsraJE0Oqp8$

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 NOT defined and handling a "long" is good but 
> > would not help in my case because getting the property returns null.
> >
>
> Yeah you would need to store a new exchange property before (or
> header) yourself with the timestamp that the simple date function can
> use.
>
> .setExchangeProperty("myCreated", simple("${exchange.created}"))
>
>
>
> > --
> > Met vriendelijke groeten / Kind regards / Cordialement / Mit besten
> > Grüßen,
> >
> > Ronny AERTS
> > Product Owner Integrations / Integrations Manager
> >
> >
> >
> >
> > e: ronny.ae...@wisetechglobal.com  |  t: +32 (0) 3 326 50 75
> > https://urldefense.com/v3/__https://www.linkedin.com/in/ronnyaerts/_
> > _;!!Na5NE8kfbMIR6Ys!59S7myqOQeKiBKA-3Gh8uVkFpzcYIUuf_pzUbxkGGMIZxxrP
> > _VPG_eFQs_WGhsraiN_bSVs$ intris.be / wisetechglobal.com | Empowering
> > and enabling the logistics industry globally.
> > This email is subject to our Confidentiality Statement
> >
> >
> > -Original Message-
> > From: Claus Ibsen 
> > Sent: Tuesday, 26 May 2020 17:26
> > To: users@camel.apache.org
> > Subject: Re: CamelCreatedTimestamp exchange property does not seem
> > to be present anymore in camel 3.3.0
> >
> > 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 java.lang.Long?
> > >
> >
> > Ah yeah that is correct. We can make Camel support long also. You
> > are welcome to create a JIRA ticket.
> >
> >
> > > A groovy exchange.getProperty("CamelCreatedTimestamp") return a null.
> > >
> > > --
> > > Met vriendelijke groeten / Kind regards / Cordialement / Mit
> > > besten Grüßen,
> > >
> > > Ronny AERTS
> > > Product Owner Integrations / Integrations Manager
> > >
> > >
> > >
> > >
> > > e: ronny.ae...@wisetechglobal.com  |  t: +32 (0) 3 326 50 75
> > > https://urldefense.com/v3/__https://www.linkedin.com/in/ronnyaerts
> > > /__;!!Na5NE8kfbMIR6Ys!4uRqqDXlx-3LnTkCIB5OJs-DmvPcapT4A0xanxaCNEkf
> > > sCfq9FpxcxpSj6kXDlgJq5SFTfM$ intris.be / wisetechglobal.com |
> > > Empowering and enabling the logistics industry globally.
> > > This email is subject to our Confidentiality Statement
> > >
> > >
> > > -Original Message-
> > > From: Claus Ibsen 
> > > Sent: Tuesday, 26 May 2020 16:07
> > > To: users@camel.apache.org
> > > Subject: Re: CamelCreatedTimestamp exchange property does not seem
> > > to be present anymore in camel 3.3.0
> > >
> > > Hi
> > >
> > > Its called exchangeProperty in the simple language - the old property 
> > > name was deprecated also for 2.x.
> > >
> > > 3.x
> > > https://urldefense.com/v3/__https://camel.apache.org/components/la
> > > test/languages/simple-language.html__;!!Na5NE8kfbMIR6Ys!6ke8h_4LiS
> > > in2gHySqFVPoznhQUTsWZChIq-IQPoVOnFzKBJXxAKaZn0_iB_IDheA7NFN8g$
> > >
> > > 2.x
> > > https://urldefense.com/v3/__https://camel.apache.org/components/2.
> > > x/languages/simple-language.html__;!!Na5NE8kfbMIR6Ys!6ke8h_4LiSin2
> > > gHySqFVPoznhQUTsWZChIq-IQPoVOnFzKBJXxAKaZn0_iB_IDhepyDCZkM$
> > >
> > > On Tue, May 26, 2020 at 3:14 PM Ronny Aerts 
> > >  wrote:
> > > >
> > > > 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 do a lot of things like the one below and that is 
> > > > not possible anymore without the CamelCreatedTimestamp.
> > > > 
> > > >  > > > uri="timer://test.exception.standard.scheduler?repeatCount=1" />
> > > >  ...
> > > >  
> > > >
> > > > I know that th

camel-ldif component problem

CamelCreatedTimestamp exchange property does not seem to be present anymore in camel 3.3.0

how to use global camel context properties in camel 3.3.0 groovy external script file

Re: CamelCreatedTimestamp exchange property does not seem to be present anymore in camel 3.3.0

RE: CamelCreatedTimestamp exchange property does not seem to be present anymore in camel 3.3.0

how to use global camel context properties in camel 3.3.0 groovy external script file

how to use global camel context properties in camel 3.3.0 groovy external script file

Re: CamelCreatedTimestamp exchange property does not seem to be present anymore in camel 3.3.0

RE: CamelCreatedTimestamp exchange property does not seem to be present anymore in camel 3.3.0

Re: CamelCreatedTimestamp exchange property does not seem to be present anymore in camel 3.3.0

Re: CamelCreatedTimestamp exchange property does not seem to be present anymore in camel 3.3.0

Re: CamelCreatedTimestamp exchange property does not seem to be present anymore in camel 3.3.0

Re: Camel & NiFi

Re: Camel & NiFi

Converting ProcessorDefinition to DSL and interfacing with camel k

Re: Converting ProcessorDefinition to DSL and interfacing with camel k

reactive java question

Re: Camel & NiFi

Re: Converting ProcessorDefinition to DSL and interfacing with camel k

Re: Camel & NiFi

RE: CamelCreatedTimestamp exchange property does not seem to be present anymore in camel 3.3.0

21 matches

Site Navigation

Mail list logo

Footer information