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.
<route id="test.exception.standard.route" autoStartup="true">
<from uri="timer://test.exception.standard.scheduler?repeatCount=1" />
<log message="start of route 
(${date:property.CamelCreatedTimestamp:yyyy-MM-dd-HH:mm:ss.SSS})" />
...
<log message="end of route 
(${date:property.CamelCreatedTimestamp:yyyy-MM-dd-HH:mm:ss.SSS})" />
</route>

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<mailto: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.

Reply via email to