Skip to content

Failure analyser for a missing validation provider does not kick in when using the latest Jakarta Validation API #19671

@wilkinsona

Description

@wilkinsona

We look for a ValidationException with a message that starts with the following:

Unable to create a Configuration, because no Bean Validation provider could be found

When using the version 2.0.2 Jakarta variant of the API, the message is actually the following:

Unable to create a Configuration, because no Jakarta Bean Validation provider could be found. Add a provider like Hibernate Validator (RI) to your classpath.

Note the addition of Jakarta in the first sentence of the message which is absent when using the Javax variant and version 2.0.1 of the Jakarta variant.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions