Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
Unknown
Description
We should look at dropping the support for time pattern in long values which are used for milli seconds, eg
1000 = 1s
30000 = 30s
60000 = 1h
The shothand requires a regexp parser for those syntax patterns. And if we drop this then the type converter for String -> Long just becomes plain simple and therefore faster.
An alternative is to have some kind of marker on @UriParam that indicate this option is a long value but it accepts the time pattern too, and then have generated type converter configurer to handle this specially.
This requires to markup those from all the components, eg timer, scheduler and so on.
Attachments
Issue Links
- is related to
-
CAMEL-14572 camel-core - Optimize type converter for some basic convertions
- Resolved