EL once again a hard requirement

Description

With Hibernate 5.2.4.Final the following code successfully creates a Validator, even if no EL implementation is available on the classpath:

This is because the eager EL check introduced in is avoided by using ParameterMessageInterpolator, introduced in HV-853.

But it seems to me broke this feature in commit 6bfde6e, because the EL presence check is now part of the classloading of ResourceBundleMessageInterpolator, which is an unconditional side-effect of instantiating ConfigurationImpl, which is what HibernateValidator#createGenericConfiguration does.

So with Hibernate 5.3.0.Final the code above throws this exception:

Environment

None

Assignee

Guillaume Smet

Reporter

Stephan Schroevers

Labels

None

Feedback Requested

None

Feedback Requested By

None

backPortable

None

Suitable for new contributors

None

backportDecision

None

backportReEvaluate

None

Components

Fix versions

Affects versions

Priority

Major
Configure