[TRB-94] Intake's BigDecimalValidator and the BaseValueParser don't parse inputs the same way

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Core 2.3.3
• Component/s: Turbine 2.3
• Assignee: Thomas Vandahl
• Reporter: Tilo Villwock
• Created: 21/Nov/14 11:21
• Updated: 11/Feb/18 16:47
• Resolved: 11/Feb/18 16:47

Description

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