Decide whether DefaultValidationProviderResolver should not throw an exception when a specified provider cannot be loaded

Description

See DefaultValidationProviderResolver line 347

Environment

None

Activity

Show:
Hardy Ferentschik
August 29, 2012, 5:52 PM

changed the way the providers get loaded. Now java.util.ServiceLoader is used.

Hardy Ferentschik
August 29, 2012, 6:24 PM

Turns out ServiceLoader adopts the strategy that if a provider is not loadable, throw an exception (which is really the behavior we had). Just added a test showing this behavior, otherwise we can just close this issue as rejected imo.

Emmanuel Bernard
September 4, 2012, 6:39 PM

We stick to this behavior. No need to define it in the spec though.

Hardy Ferentschik
September 4, 2012, 9:43 PM

+1

Sanjeeb Sahoo
December 10, 2012, 7:02 AM

Instead of throwing a ValidationException, the correct thing to do is to try the next available provider, otherwise you get into issues like BVAL-343.

Fixed

Assignee

Hardy Ferentschik

Reporter

Hardy Ferentschik

Labels

None

Feedback Requested

None

Feedback Requested By

None

backPortable

None

Suitable for new contributors

None

Pull Request

None

backportDecision

None

backportReEvaluate

None

Fix versions

Priority

Major
Configure