Property validation should throw error for auto population of setter

Description

Consider the following component

With generated setters, validate and validateparams should throw errors if the values passed to the setter are invalid. The following example works properly and will throw errors for invalid email and for an invalid string length.

However, when using the auto populate, errors are not thrown:

Instead we just get an object back with null properties. (screenshot attached).

When auto populating with correct values that pass the required validations, the properties are set:

This suggests that the auto populate is using the validation, but it should be throwing errors for failed validations too.

Testcase attached.

Environment

None

Attachments

3

relates to

Activity

Pothys - MitrahSoft 
16 December 2020 at 07:42

Ok, I close this ticket with a fixed version 5.2.6.21-SNAPSHOT.

Rory Laitila 
15 December 2020 at 16:29

Confirmed working now, thanks for following up.

Pothys - MitrahSoft 
15 December 2020 at 15:34

, Did you see my above comment. If no means please see and report here back it will improve the status of the ticket

Pothys - MitrahSoft 
14 July 2020 at 11:19

, I hope this issue was fixed in version 5.2.6.21-SNAPSHOT onwards. Shall I close this ticket?

Brandon Brown 
1 December 2017 at 14:43

Fixed

Details

Assignee

Reporter

Priority

Fix versions

New Issue warning screen

Before you create a new Issue, please post to the mailing list first https://dev.lucee.org

Once the issue has been verified, one of the Lucee team will ask you to file an issue

Affects versions

Created 13 April 2016 at 09:20
Updated 26 April 2025 at 09:41
Resolved 16 December 2020 at 07:42