alaahong commented on issue #741:
URL: https://github.com/apache/fesod/issues/741#issuecomment-3666272488
Leave the comment for open discussion.
1. Both Apache Bval and Hibernate Validator might tricky on the version
e.g. hibernate validator
| Hibernate Validator Version | Minimum Java Version | Typical Supported
Java Versions | Bean / Jakarta Validation Version | Target Jakarta / Java EE |
Recommended use / notes |
|---:|:---:|:---|:---|:---|:---|
| 9.x | 17 | 17, 21, 23, 24 (and newer) | Jakarta Validation 3.1 | Jakarta
EE 11 | For new projects on Java 17+ or upgrading to Jakarta EE 11. |
| 8.x | 11 | 11, 17 (and newer) | Jakarta Validation 3.0 | Jakarta EE 10 |
For projects migrating to the Jakarta namespace with JDK ≥ 11. |
| 7.x | 8 | 8, 11, 17 | Bean Validation 2.0 / transitional to 3.0 | Jakarta
EE 9 (migration era) | Can be used on Java 8 while adapting to newer validation
APIs. |
| 6.x | 8 | 8, 11, 17 | Bean Validation 2.0 | Java EE 8 | Recommended for
legacy projects that must remain on Java 8. |
| 5.x | 6 | 6, 7, 8 | Bean Validation 1.1 | Java EE 7 | For very old legacy
environments; generally recommended to upgrade. |
2. It's also easy to work with customized validator in invoke, otherwise,
you have to leave slot in such JSR 380/349/303 implementation for additional
logic injection
e.g. skip or blocking exception row/file, this is a normal next step if any
validation failed
3. Business validator is not less than rule
e.g. in Chinese requirement, we might meet such logic --> validate row A via
B or C, any practice?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
