[
https://issues.apache.org/jira/browse/CAMEL-5827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13508899#comment-13508899
]
Luca Burgazzoli commented on CAMEL-5827:
----------------------------------------
Yes this bug affects the current code but as it looks quite easy to fix in my
patch (in fact the latest one did revert the behavior), what if I open a new
jira and link it with this one?
> camel-bindy - Handle implied-decimal values
> -------------------------------------------
>
> Key: CAMEL-5827
> URL: https://issues.apache.org/jira/browse/CAMEL-5827
> Project: Camel
> Issue Type: New Feature
> Components: camel-bindy
> Reporter: Luca Burgazzoli
> Priority: Minor
> Fix For: 2.11.0
>
> Attachments: camel-bindy-implied.patch
>
>
> The communication with some legacy systems often relies on old protocols and
> formats not easy to change and among that you may have to deal with fixed
> lenght records on which decimal numbers are not represented with a decimal
> separator but the number of decimal places is defined by the protocol
> definition (e.g. COBOL copy-book).
> Example:
> @DataField(pos = 1, length = 5, precision = 2, implied-decimal-separator =
> true)
> private BigDecimal amount;
> The string "12345" maps to 123.45 in Java.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
