Vlad Mihalcea ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMWI3ZTFiZjI5... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-14020?atlOrigin=eyJpIjoiMWI3ZT... ) HHH-14020 ( https://hibernate.atlassian.net/browse/HHH-14020?atlOrigin=eyJpIjoiMWI3ZT... ) Allow Hibernate Types to have access to ServiceRegistry during initialization ( https://hibernate.atlassian.net/browse/HHH-14020?atlOrigin=eyJpIjoiMWI3ZT... ) Change By: Vlad Mihalcea ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) [HHH-13103|https://hibernate.atlassian.net/browse/HHH-13103] added support for getting access to configuration properties when instantiating a Hibernate Type. However, there are still two issues I'm facing in the \ [Hibernate Types project |[https://github.com/vladmihalcea/hibernate-types|https://github.com/vladmihalcea/hibernate-types|smart-link ] ( ][:| https://github.com/vladmihalcea/hibernate-types): ] - * the new {{TypeBootstrapContext}} only works from 5.4.13 onwards, so if I add this constructor, any prior Hibernate version will fail with a {{NoClassDeffFoundError}}. - * I need to get access to the underlying Driver Type to adjust how a certain Type handles arrays, for instance. For this reason, I propose we inject the {{ SessionFactoryImplementor ServiceRegistry }} when initializing the Type if there is a matching constructor taking this argument. ( https://hibernate.atlassian.net/browse/HHH-14020#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-14020#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=Em... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100126- sha1:acdbdcc )