camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arno Noordover (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-9938) TimerPatternConverter - Should be more strict
Date Mon, 23 May 2016 09:01:12 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-9938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15296121#comment-15296121
] 

Arno Noordover commented on CAMEL-9938:
---------------------------------------

I'm having fun!
I suggest we support the following convention (case insensitive):
* only numbers
* (number)h, (number)hour or (number)hours to define hours;
* (number)m, (number)min, (number)minute, (number)minutes to define minutes;
* (number)s, (number)sec, (number)second, (number)seconds to define seconds.
You are only allowed to define each of hours, minutes and seconds once.
After replacing the first occurrence of hours, minutes and seconds and passing the previous
check the length of the resulting string is checked for any remaining characters.

> TimerPatternConverter - Should be more strict
> ---------------------------------------------
>
>                 Key: CAMEL-9938
>                 URL: https://issues.apache.org/jira/browse/CAMEL-9938
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 2.17.0
>            Reporter: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.18.0
>
>
> So it would report an error if attempting to use 
> delay=5ssegegegegqergerg
> eg as today its too lenient and assume people do not make typo's. So if you type 5s then
its 5 seconds.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message