Skip to content

Improve error messages in SpEL #36756

@sbrannen

Description

@sbrannen

While processing PR #36755, I noticed that the error message for MAX_REGEX_LENGTH_EXCEEDED refers to the start position of the matches keyword instead of the start position of the the invalid regular expression.

So, we should fix the error message for invalid regular expressions in SpEL and improve other error messages as necessary.

Metadata

Metadata

Assignees

Labels

in: coreIssues in core modules (aop, beans, core, context, expression)status: backportedAn issue that has been backported to maintenance branchestype: enhancementA general enhancement

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions