All issues

Do not use validation provider resolver when provider is explicitly given
BVAL-486
i am creating a java object and saving it to the mysql database in which the table name is "student"
BVAL-719
Make BVAL friendly towards Java 9 modules
BVAL-503
Support constraints at new annotation locations
BVAL-499
Retrieve method parameter names via new API in Java 8
BVAL-498
Mark BV-defined constraint types with @Repeatable
BVAL-497
@Future/@Past validators for JSR 310 data types
BVAL-496
Support JDK8's Optional class
BVAL-467
Move XML namespace to jcp.org from jboss.org
BVAL-455
"Provider org.hibernate.validator.HibernateValidator not a subtype" error during service discovery
BVAL-343
Introduce order for property constraints and allow to stop validation for first failing property constraint
BVAL-248
Separate the notion of message resolver vs message interpolator
BVAL-217
Apply constraints on the elements of an iterator
BVAL-202
Hello
BVAL-738
ConstraintViolationException links to bean field(s)
BVAL-737
Update TestNG to 6.11 for consistency with the TCK
BVAL-736
Clarify if we should change the Automatic-Module-Name
BVAL-735
Upgrade CI information of API README.md
BVAL-734
Clarify licensing section of the README?
BVAL-733
Update API CONTRIBUTING.md
BVAL-732
Clarify the situation for the XML namespaces
BVAL-731
Move specification under Eclipse (EE4J umbrella)
BVAL-730
Annotated bounded type parameter cause IllegalArgumentException
BVAL-729
@Valid and nested objects
BVAL-726
Upgrade Asciidoctor tooling
BVAL-723
Do not include the license check configuration files into the published artifact
BVAL-721
Create a specific branch for the Jakarta artifact and adjust the GAV
BVAL-720
Allow asynchronous validation
BVAL-715
If "Email element" is null, it is not described in JavaDoc whether it is valid or not.
BVAL-714
Wrong javadocs
BVAL-713
Clarify what happens when mixing inheritance and default group redefinition
BVAL-711
Clarify that behavior is undefined if legacy @Valid and type argument @Valid are given for same element
BVAL-709
Fix intermittent test failures of ValidationTest#testCachedProvidersCanBeGarbageCollected()
BVAL-707
Consider to create a new constraint for @Age
BVAL-704
Reallow null values in ConstraintViolationException second constructor
BVAL-703
Precise that the cascaded validation VE resolution algorithm is restricted to the VEs compatible with the declared type
BVAL-702
Add skew tolerance to time based constraints
BVAL-700
API changes review for Bean Validation
BVAL-699
Fix incorrect example in table 5.1
BVAL-698
Include the ref type and ref number in the reference link title
BVAL-697
Base class for ConstraintValidator implementors
BVAL-696
In the XSD, relax the order of elements where the order does not matter
BVAL-694
Make order of <constraint> and <container-element-type> consistent in XSD
BVAL-693
Misc. clarifications around container element validation
BVAL-691
Clarify getLeafBean() for container element constraints
BVAL-690
Make @ConvertGroup#from() default to Default.class
BVAL-689
Use correct license for final release
BVAL-684
Misc. clarifications around container element validation
BVAL-682
Clarify value returned by getInvalidValue() for implicitly unwrapped container constraint
BVAL-681
Constraint builder API - inContainer() should take int instead of Integer
BVAL-680
issue 1 of 659

Do not use validation provider resolver when provider is explicitly given

Description

When bootstrapping Bean Validation via Validation#byProvider(Class<?> provider), still the provider resolver is used to find a registered provider which is assignment compatible with the given class. I'm wondering why this is, can't we just instantiate the given provider type?

The current behavior requires a custom resolver in OSGi, also when explicitly bootstrapping Hibernate Validator, i.e. we already have the right provider class and don't need to find it anymore.

Environment

None

Status

Assignee

Unassigned

Reporter

Gunnar Morling

Labels

None

Worked in

None

Feedback Requested

None

Feedback Requested By

None

backPortable

None

Community Help Wanted

None

Suitable for new contributors

None

Requires Release Note

None

Pull Request

None

backportDecision

None

backportReEvaluate

None

Components

Fix versions

Priority

Blocker