If the JPA validation mode is set to CALLBACK, BV constraints such as
@NotNull, @Size etc. are not reflected in the DDL created by ORM.
Instead, in TypeSafeActivator, the BV constraints are only considered for
DDL if the validation mode is DDL or AUTO .
CALLBACK is the safe way to ensure BV is invoked by JPA (instead of
silently ignoring it if no BV provider is present), so it's the setting I
usually recommend. I think constraints should also be propagated to DDL in
this mode, so I'm wondering whether there a specific reason for the current
behaviour or wether we can change it?
I realized that we could allow users to define entities without a default
For Kotlin, which supportsdefault values, this could be beneficial.
There is some info about how we could do that in this using Objenesis in
the following Spring issue:
Let me know what you think,
WildFly would like to have a version of 5.3+, that is compatible with ORM
5.1, with regard to the org.hibernate.session changes (including mapping of
exceptions thrown, so that the same exceptions are thrown).
Is it even possible to have an extra org.hibernate.Session interface + impl
(bridge) that matches the same session included in 5.1? The impl would
delegate to the real underlying org.hibernate.Session impl classes and also
wrap thrown exceptions, so that Hibernate 5.1 native ORM apps, continue to
work without code changes
Or something like that.
I could see how some users wouldn't want to use the compatibility layer to
avoid extra overhead, so in WildFly, we would have to make that possible
What do you think?
We would need something similar in ORM 6.0+ that is also compatible with
5.1, if this is possible.
We just published 5.9.0.Final, the first stable release in the 5.9 branch.
This release brings a brand-new JSR-352 integration for mass indexing,
WildFly feature packs, and better integration to modular environments.
Check out our blog for more information about this release:
yoann(a)hibernate.org / yrodiere(a)redhat.com
Hibernate NoORM team