You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2020/05/23 06:45:00 UTC
[jira] [Reopened] (CAMEL-14878) Timeouts and durations should use a
java.time.Duration instead of long
[ https://issues.apache.org/jira/browse/CAMEL-14878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen reopened CAMEL-14878:
---------------------------------
Not fully complete yet. time and mock endpoints are using long types for their values.
We could also have the generator configurer via @Metadata that the option supports configuring long values with this style and have its own converter - then we dont use the runtime type converter for String -> long.
And then dont need to change option to Duration but can just markup those via @Metdata(xxx = true) where xxx is some new name - for example timePattern true|false
> Timeouts and durations should use a java.time.Duration instead of long
> ----------------------------------------------------------------------
>
> Key: CAMEL-14878
> URL: https://issues.apache.org/jira/browse/CAMEL-14878
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 3.2.0
> Reporter: Guillaume Nodet
> Assignee: Guillaume Nodet
> Priority: Major
> Fix For: 3.4.0
>
>
> This would allow to use a specific syntax which has been removed in 3.2.0, such as {{3s}} instead of {{3000}}. There are also cases where a pair of properties is used (duration / unit) which could be simplified to a single {{java.time.Duration}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)