February 2023 - hibernate-issues - Jboss List Archives

[JIRA] (HHH-16122) Named type [class xxx] did not implement BasicType nor UserType

by Alexander Savov (JIRA)

Alexander Savov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16122 ( https://hibernate.atlassian.net/browse/HHH-16122?atlOrigin=eyJpIjoiNGIyOW... ) Re: Named type [class xxx] did not implement BasicType nor UserType ( https://hibernate.atlassian.net/browse/HHH-16122?atlOrigin=eyJpIjoiNGIyOW... ) Christian, Thanks a lot for detailed response. It really means a lot to me! ” The workaround is to not use a *type variable* for persistent attribute types. ”: Maybe this explains only the case when persisting an attribute of type “type-variable-of-Generic-MappedSuperclass” ( Enum in our case). How is that recommendation related to the original issue, where the attribute type of ServiceTaskCallback serviceTaskCallback is *not* of “type-variable-of-Generic-MappedSuperclass” and is still defined in “{{TaskServiceDocument}}Generic-MappedSuperclass“: 43 @Type(JsonBinaryType. *class* ) 44 @Column(columnDefinition = "jsonb") *45 public* {{ ServiceTaskCallback serviceTaskCallback;}} If I understand it correctly there might be two different issues when it comes to Generic MappedSuperclass class: @MappedSuperclass public static class TaskServiceDocument<E extends Enum<E>> extends MultiTenantDocument { // Issue 1: the type-variable seems problematic @Enumerated(EnumType.STRING) public E taskSubStage; // Issue 2: this is not working as issue description/repro states @Type(JsonBinaryType.class) @Column(columnDefinition = "jsonb") public ServiceTaskCallback serviceTaskCallback; } Will the fix you mentioned address both issues? Or? “In previous versions of Hibernate the type of that attribute was actually an (arbitrary) one of the possible type arguments as provided through subtypes of TaskServiceDocument. This is obviously wrong“. This might be wrong, however backward compatibility and reasonable mitigation is also a dimension to consider from client/consumer perspective when it comes to big legacy systems. Christian, is there an opportunity to have a live chat, such as zoom, to ease the communication? ( https://hibernate.atlassian.net/browse/HHH-16122#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16122#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=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100214- sha1:c33f0bb )

2 years, 10 months

1
0
0 / 0

[JIRA] (HHH-16122) Named type [class xxx] did not implement BasicType nor UserType

by Christian Beikov (JIRA)

Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16122 ( https://hibernate.atlassian.net/browse/HHH-16122?atlOrigin=eyJpIjoiNzUxNm... ) Re: Named type [class xxx] did not implement BasicType nor UserType ( https://hibernate.atlassian.net/browse/HHH-16122?atlOrigin=eyJpIjoiNzUxNm... ) The workaround is to not use a type variable for persistent attribute types. If you think about the concept of attributes and which type declares them from a JPA model perspective, the use of type variables is complicating a lot. Let me explain what happens here. For the *JPA metamodel* in Hibernate 6 there is only one attribute TaskServiceDocument#taskSubStage which has the type Enum. It doesn’t matter in the JPA metamodel what you provide as type argument in subtypes. Since TaskServiceDocument declares the attribute, we have to consider the type that is declared there. In previous versions of Hibernate the type of that attribute was actually an (arbitrary) one of the possible type arguments as provided through subtypes of TaskServiceDocument. This is obviously wrong. If you ask for the type of the TaskServiceDocument#taskSubStage attribute it must be Enum. We went to great lengths to ensure support for type variables is relatively decent, but we obviously have some edge cases that haven’t been covered by the testsuite. You’ll just have to wait for the fix ( https://github.com/hibernate/hibernate-orm/pull/6087 ) to be merged and released, or you build your own version in the meantime to continue testing. ( https://hibernate.atlassian.net/browse/HHH-16122#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16122#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=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100214- sha1:c33f0bb )

2 years, 10 months

1
0
0 / 0

[JIRA] (HHH-16122) Named type [class xxx] did not implement BasicType nor UserType

by Alexander Savov (JIRA)

Alexander Savov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16122 ( https://hibernate.atlassian.net/browse/HHH-16122?atlOrigin=eyJpIjoiMjUwMz... ) Re: Named type [class xxx] did not implement BasicType nor UserType ( https://hibernate.atlassian.net/browse/HHH-16122?atlOrigin=eyJpIjoiMjUwMz... ) Hi Christian, Is there *any workaround* that might be applied to: @MappedSuperclass public static class TaskServiceDocument<E extends Enum<E>> extends TaskServiceDocumentFix { @Enumerated(EnumType.STRING) public E taskSubStage; } cause that’s blocking our Java17 and Hibernate6 migration story. At least I can make further progress… ( https://hibernate.atlassian.net/browse/HHH-16122#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16122#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=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100214- sha1:c33f0bb )

2 years, 10 months

1
0
0 / 0

[JIRA] (HHH-16123) Invalid generated SQL query when accessing join from a treated abstract superclass path

by Marco Belladelli (JIRA)

2 years, 10 months

1
0
0 / 0

[JIRA] (HHH-16130) Unable to invoke Postgres date_trunc function via CriteriaApi

by Marco Belladelli (JIRA)

Marco Belladelli ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=637b480... ) *commented* on HHH-16130 ( https://hibernate.atlassian.net/browse/HHH-16130?atlOrigin=eyJpIjoiNDZmMj... ) Re: Unable to invoke Postgres date_trunc function via CriteriaApi ( https://hibernate.atlassian.net/browse/HHH-16130?atlOrigin=eyJpIjoiNDZmMj... ) As mentioned in this comment ( https://discourse.hibernate.org/t/how-to-use-postgres-date-trunc-via-crit... ) of the related issue’s original forum post, you can try passing something like new SqmExtractUnit<>( TemporalUnit.YEAR, ((NodeBuilder) criteriaBuilder).getIntegerType(), (NodeBuilder) criteria>Builder ) instead of criteriaBuilder.literal("year"). ( https://hibernate.atlassian.net/browse/HHH-16130#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16130#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=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100214- sha1:c33f0bb )

2 years, 10 months

1
0
0 / 0

[JIRA] (HHH-16122) Named type [class xxx] did not implement BasicType nor UserType

by Christian Beikov (JIRA)

2 years, 10 months

1
0
0 / 0

[JIRA] (HHH-16150) Hibernate ORM no longer drops the schema when using the create-drop strategy and a session factory observer throws an exception on startup

by Yoann Rodière (JIRA)

2 years, 10 months

1
0
0 / 0

[JIRA] (HHH-16150) Hibernate ORM no longer drops the schema when using the create-drop strategy and a session factory observer throws an exception on startup

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNGIwOTRlY2E1... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16150?atlOrigin=eyJpIjoiNGIwOT... ) HHH-16150 ( https://hibernate.atlassian.net/browse/HHH-16150?atlOrigin=eyJpIjoiNGIwOT... ) Hibernate ORM no longer drops the schema when using the create-drop strategy and a session factory observer throws an exception on startup ( https://hibernate.atlassian.net/browse/HHH-16150?atlOrigin=eyJpIjoiNGIwOT... ) Issue Type: Bug Affects Versions: 6.2.0.CR2 Assignee: Unassigned Components: hibernate-core Created: 07/Feb/2023 04:12 AM Fix Versions: 6.2.0 Priority: Major Reporter: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Regression in ORM 6. I think it’s specific to ORM 6.2, because I’ve never encountered this problem with ORM 6.0/6.1, but I’m not 100% sure (maybe the problem just wasn’t as visible in Hibernate Search before). The scenario: * Hibernate ORM boots. While building the session factory, it calls sessionFactoryCreated on all session factory observers. * In ORM 6.2, this means in particular calling org.hibernate.boot.internal.SessionFactoryObserverForSchemaExport#sessionFactoryCreated , which successfully creates the DB schema. * One of the next observers (say, Hibernate Search’s) throws an exception from sessionFactoryCreated (say, because the Hibernate Search mapping is invalid). * Hibernate ORM catches that exception and attempts to close the session factory. * Upon closing, the session factory calls sessionFactoryClosing on all session factory observers. * In ORM 6.2, this means in particular calling org.hibernate.boot.internal.SessionFactoryObserverForSchemaExport#sessionFactoryClosing. That last call fails with the following exception: org.hibernate.service.UnknownServiceException: Unknown service requested [org.hibernate.engine.jdbc.spi.JdbcServices] at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:212) at org.hibernate.service.internal.SessionFactoryServiceRegistryImpl.getService(SessionFactoryServiceRegistryImpl.java:100) at org.hibernate.tool.schema.internal.SchemaDropperImpl$DelayedDropActionImpl$JdbcContextDelayedDropImpl.<init>(SchemaDropperImpl.java:677) at org.hibernate.tool.schema.internal.SchemaDropperImpl$DelayedDropActionImpl.perform(SchemaDropperImpl.java:641) at org.hibernate.boot.internal.SessionFactoryObserverForSchemaExport.sessionFactoryClosing(SessionFactoryObserverForSchemaExport.java:48) at org.hibernate.internal.SessionFactoryObserverChain.sessionFactoryClosing(SessionFactoryObserverChain.java:48) at org.hibernate.internal.SessionFactoryImpl.close(SessionFactoryImpl.java:838) at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:377) In Hibernate ORM 5, things were a bit different (e.g. schema creation/drop was not done in an observer, see https://github.com/hibernate/hibernate-search/pull/3396/commits/9b18a1ed3... ( https://github.com/hibernate/hibernate-search/pull/3396/commits/9b18a1ed3... ) ), so it’s hard to pinpoint where the problem was introduced exactly; but I can say at least that we didn’t get that exception in Hibernate ORM 5 and the schema was properly dropped. I believe the problem is here: https://github.com/hibernate/hibernate-orm/blob/63715770e94f18137d9d63f7d... ( https://github.com/hibernate/hibernate-orm/blob/63715770e94f18137d9d63f7d... ) It seems odd that we close the service registry after closing each integrator? I’d expect closing the service registry to be one of the very last things we do. ( https://hibernate.atlassian.net/browse/HHH-16150#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16150#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=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100214- sha1:c33f0bb )

2 years, 10 months

1
0
0 / 0

[JIRA] (HHH-15806) Envers and Hibernate 6 and PostgreSQLEnumType

by Jay Ahn (JIRA)

Jay Ahn ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=61a6681... ) *commented* on HHH-15806 ( https://hibernate.atlassian.net/browse/HHH-15806?atlOrigin=eyJpIjoiN2RiNm... ) Re: Envers and Hibernate 6 and PostgreSQLEnumType ( https://hibernate.atlassian.net/browse/HHH-15806?atlOrigin=eyJpIjoiN2RiNm... ) It must be a blocker as we cannot upgrade our project from boot 2.x to 3.x. ( https://hibernate.atlassian.net/browse/HHH-15806#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15806#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=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100214- sha1:c33f0bb )

2 years, 10 months

1
0
0 / 0

[JIRA] (HHH-16093) UnknownTableReferenceException: Unable to determine TableReference (`PM_SERVICE_GROUP`) for `com.frontierssys.infrastructure.core.framework.persistence.model.Service.serviceMapping.{fk-target}

by Marco Belladelli (JIRA)

Marco Belladelli ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=637b480... ) *commented* on HHH-16093 ( https://hibernate.atlassian.net/browse/HHH-16093?atlOrigin=eyJpIjoiNWU1Yz... ) Re: UnknownTableReferenceException: Unable to determine TableReference (`PM_SERVICE_GROUP`) for `com.frontierssys.infrastructure.core.framework.persistence.model.Service.serviceMapping.{fk-target} ( https://hibernate.atlassian.net/browse/HHH-16093?atlOrigin=eyJpIjoiNWU1Yz... ) Hello, thanks for reporting the problem and providing a reproducer! Looks like you have a @OneToMany(mappedBy="serviceGroup") association inside your Service entity, but the mappedBy property refers to another type ( ServiceGroup ). I think it should be @OneToMany(mappedBy="service") instead. Same thing for ServiceMethod , it should be @OneToMany(mappedBy="serviceMethod"). ( https://hibernate.atlassian.net/browse/HHH-16093#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16093#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=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100214- sha1:c33f0bb )

2 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues February 2023