Tilo Villwock created TRB-94:
--------------------------------
Summary: Intake's BigDecimalValidator and the BaseValueParser
don't parse inputs the same way
Key: TRB-94
URL: https://issues.apache.org/jira/browse/TRB-94
Project: Turbine
Issue Type: Bug
Components: Turbine 2.3
Affects Versions: Core 2.3.3
Reporter: Tilo Villwock
Hello,
I don't know if this is still the case in the current development version but
the BigDecimalValidator does not check whether the parsed value has the same
length as the original input while the BaseValueParser does. This leads to
unexpected behavior because while a String like "3.21a" passes the validation
test it will not get set because the parsed length is not alike. One would
expect that the user will get notified by a message that this is not a valid
number.
The relevant lines are:
org.apache.turbine.services.intake.validator.parser.BigDecimalParser: 149
org.apache.turbine.util.parser.BaseValueParser: 653-668
Tilo
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
