Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow other extensions to define Hibernate ORM configurations #9361

Closed
Sanne opened this issue May 15, 2020 · 1 comment · Fixed by #9362
Closed

Allow other extensions to define Hibernate ORM configurations #9361

Sanne opened this issue May 15, 2020 · 1 comment · Fixed by #9362
Assignees
Labels
area/hibernate-orm Hibernate ORM area/persistence OBSOLETE, DO NOT USE kind/enhancement New feature or request
Milestone

Comments

@Sanne
Copy link
Member

Sanne commented May 15, 2020

Description
The Keycloack team is looking to reuse the Quarkus extension to boot Hibernate ORM, but needs to configure the persistence properties in various custom ways; in particular they would like to source some selected properties from a different configuration system.

I happened to have a refactoring in process of HibernateOrmProcessor, which is still evolving to make it possible to fix #8932 - but I can easily extract "the good parts" so far, which would help for Keycloack and possibly others as it exposed more finegrained build items.

Implementation ideas
I already have a proposal, extracted from larger work.

@Sanne Sanne added kind/enhancement New feature or request area/hibernate-orm Hibernate ORM labels May 15, 2020
@Sanne Sanne added this to the 1.5.0 milestone May 15, 2020
@Sanne Sanne self-assigned this May 15, 2020
@quarkusbot quarkusbot added the area/persistence OBSOLETE, DO NOT USE label May 15, 2020
@quarkusbot
Copy link

/cc @gsmet @Sanne

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/hibernate-orm Hibernate ORM area/persistence OBSOLETE, DO NOT USE kind/enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants