On integration with Bean Validation and Jakarta Persistence

[emmanuelbernard]

Looks like applying validation on save and saveAll is defined. But ti is also defined in JPA, JPA will validate entities upon insertion or update. Describe the mechanism to avoid double callor explicit in the spec that the double call is an expected behavior (maybe to do validation in sync vs async?)

[keilw]

While the Persistence Spec discusses "3.6. Bean Validation" there is no dependency in JPA to Validation.

Same should be with Validation or Persistence here.
Discuss them in the spec where appropriate, but there shouldn't be a hard dependency to either Persistence or Validation in the Data API (at least not in the "core" part)

[otaviojava]

We do the same; it will work as the capability or extension of the specification if the vendor wants it to do so.
You can check this session here:

https://github.com/jakartaee/data/blob/main/spec/src/main/asciidoc/jakarta-ee.adoc

[njr-11]

Pull #231 , which is currently in progress, covers Jakarta Validation, and does so in a way that does not introduce API dependencies on Jakarta Validation. I'm intending to get some updates for CrudRepository in there as well, once another pull merges. If either of you have comments, please add them to #231 .

[otaviojava]

We were closing this issue once we had a PR fixing this point.
Thank you for the feedback, and feel free to reopen this PR as many times that make sense or create a new one.