February 2023 - hibernate-issues - Jboss List Archives

[JIRA] (HHH-16233) Bad error for mutable non-root entity

by 신동훈 (JIRA)

1 year, 3 months

1
0
0 / 0

[JIRA] (HHH-16233) Bad error for mutable non-root entity

by 신동훈 (JIRA)

신동훈 ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=63fc1ff... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiZWE0YTUzM2Uw... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16233?atlOrigin=eyJpIjoiZWE0YT... ) HHH-16233 ( https://hibernate.atlassian.net/browse/HHH-16233?atlOrigin=eyJpIjoiZWE0YT... ) Bad error for mutable non-root entity ( https://hibernate.atlassian.net/browse/HHH-16233?atlOrigin=eyJpIjoiZWE0YT... ) Change By: 신동훈 ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=63fc1ff... ) [immutable|https://github.com/immutable] can only be declared on the Root Entity. That An incorrect error log message is , it given about @Immutable is not wrong declared to say that a non-root entity is mutable, so you should not send the message immutableAnnotationOnNonRoot. This should only happen for non-root entities that are immutable not @Immutable attached. ( https://hibernate.atlassian.net/browse/HHH-16233#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16233#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#100217- sha1:077879e )

1 year, 3 months

1
0
0 / 0

[JIRA] (HHH-16233) Bad error for mutable non-root entity

by 신동훈 (JIRA)

신동훈 ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=63fc1ff... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiYWI3YzdkMjNm... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16233?atlOrigin=eyJpIjoiYWI3Yz... ) HHH-16233 ( https://hibernate.atlassian.net/browse/HHH-16233?atlOrigin=eyJpIjoiYWI3Yz... ) Bad error for mutable non-root entity ( https://hibernate.atlassian.net/browse/HHH-16233?atlOrigin=eyJpIjoiYWI3Yz... ) Issue Type: Bug Affects Versions: 6.1.7 Assignee: Unassigned Attachments: 스크린샷 2023-02-27 오후 12.18.23.png Components: hibernate-core Created: 26/Feb/2023 19:20 PM Environment: all Labels: core Priority: Minor Reporter: 신동훈 ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=63fc1ff... ) immutable ( https://github.com/immutable ) can only be declared on the Root Entity. That is, it is not wrong to say that a non-root entity is mutable, so you should not send the message immutableAnnotationOnNonRoot. This should only happen for non-root entities that are immutable. ( https://hibernate.atlassian.net/browse/HHH-16233#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16233#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#100217- sha1:077879e )

1 year, 3 months

1
0
0 / 0

[JIRA] (HHH-16232) CompositeUserType change in 6.0 make impossible to migrate multi-column mapping

by Sylvain Lecoy (JIRA)

Sylvain Lecoy ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiZWMzZmEwMTU5... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16232?atlOrigin=eyJpIjoiZWMzZm... ) HHH-16232 ( https://hibernate.atlassian.net/browse/HHH-16232?atlOrigin=eyJpIjoiZWMzZm... ) CompositeUserType change in 6.0 make impossible to migrate multi-column mapping ( https://hibernate.atlassian.net/browse/HHH-16232?atlOrigin=eyJpIjoiZWMzZm... ) Change By: Sylvain Lecoy ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) I am working with a domain model class which is composed of an embedded object which implements the DomainEvent interface. DomainEvent can be any concrete class and is serialized by Jackson. To solve this in hibernate 5 I have used a CompositeUserType over two columns: event_body, and type_name. {code:java}public class StoredEvent { private DomainEvent event; private long eventId; private Instant occurredOn; private String typeName; }{code} In Hibernate 5 the hbm.xml mapping was very simple and straightforward: {code:xml}<?xml version="1.0"?> <!DOCTYPE hibernate-mapping PUBLIC "-//Hibernate/Hibernate Mapping DTD 3.0//EN" "http://www.hibernate.org/dtd/hibernate-mapping-3.0.dtd"> <hibernate-mapping default-access="field" default-cascade="all"> <class name="event.StoredEvent" table="stored_event" lazy="true"> <id name="eventId" type="long" column="event_id" unsaved-value="-1"> <generator class="identity" /> </id> <property name="event" type="port.adapter.persistence.hibernate.DomainEventUserType"> <column name="event_body"/> <column name="type_name"/> </property> <property name="typeName" column="type_name" insert="false" update="false"/> <property name="occurredOn" column="occurred_on"/> </class> </hibernate-mapping>{code} The DomainEventUserType was also more or less simple to write. Testing does work well, and I have provided a reproduced using the test-case-templates on my github: [https://github.com/itsmoonrack/hibernate-test-case-templates|https://gith...] I understand hbm.xml multiple <column/> now disallowed In 6.0 the support for basic property mappings with multiple columns was removed. The only use case for that was when a {{CompositeUserType}} was in use, which was reworked to now work on top of components. In Hibernate 6.0 I did not successfully migrated this composite user type and in fact I tried multiple strategies (implementing the new CompositeUserType) but failed successfully. I tried the following: {code:xml}<component name="event" class="port.adapter.persistence.hibernate.DomainEventUserType">  <property name="eventBody" column="event_body"/> <property name="typeName" column="type_name"/> </component>{code} but the metamodel mapper is telling me that it “*Could not locate field name [eventBody] on class [domain.model.DomainEvent]*” I also tried to embbed a component (which I don’t like because it change by domain model object, and I can’t/don’t want to do that if possible since the StoredEvent object is also used by 2 other persistence providers: Hazelcast and Couchebase using hexagonal architecture) {code:java}public class StoredEventThatMayWork { private ComponentMapped event; private long eventId; private Instant occurredOn; public StoredEventThatMayWork(final DomainEvent event) { this.event = new ComponentMapped(event, event.getClass().getName()); this.occurredOn = event.occurredOn(); } public static class ComponentMapped { private DomainEvent eventBody; private String typeName; public ComponentMapped(final DomainEvent event, final String typeName) { this.eventBody = event; this.typeName = typeName; } } }{code} but it did not worked either: *Could not determine recommended JdbcType for* {{domain.model.DomainEvent}} Either there is something I did not understood, either this functionality has been broken starting from 6.0, and I am currently blocked by this. Any way of having this fonctionality working for 6.0 ? I have provided three tests classes: * hibernate-orm-5/ORMUnitTestCase which does work as expected * hibernate-orm-6/ORMUnitTestCase which yield *Could not locate field name [eventBody] on class [domain.model.DomainEvent]* * hibernate-orm-6/ORMUnitTestCaseThatMayWork with the component approach but yields *Could not determine recommended JdbcType for* {{domain.model.DomainEvent}} see reproduced test case here: [https://github.com/itsmoonrack/hibernate-test-case-templates/tree/main/or...] Any help would be greatly appreciated, if its not a bug, then it might be a documentation bug to provide a migration path. I would be happy to write such a documentation if missing. ( https://hibernate.atlassian.net/browse/HHH-16232#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16232#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#100217- sha1:077879e )

1 year, 3 months

1
0
0 / 0

[JIRA] (HHH-16232) CompositeUserType change in 6.0 make impossible to migrate multi-column mapping

by Sylvain Lecoy (JIRA)

1 year, 3 months

1
0
0 / 0

[JIRA] (HHH-16232) CompositeUserType change in 6.0 make impossible to migrate multi-column mapping

by Sylvain Lecoy (JIRA)

Sylvain Lecoy ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiOTRmZTBiNzA4... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16232?atlOrigin=eyJpIjoiOTRmZT... ) HHH-16232 ( https://hibernate.atlassian.net/browse/HHH-16232?atlOrigin=eyJpIjoiOTRmZT... ) CompositeUserType change in 6.0 make impossible to migrate multi-column mapping ( https://hibernate.atlassian.net/browse/HHH-16232?atlOrigin=eyJpIjoiOTRmZT... ) Change By: Sylvain Lecoy ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) I am working with a domain model class which is composed of an embedded object which implements the DomainEvent interface. DomainEvent can be any concrete class and is serialized by Jackson. To solve this in hibernate 5 I have used a CompositeUserType over two columns: event_body, and type_name. {code:java}public class StoredEvent { private DomainEvent event; private long eventId; private Instant occurredOn; private String typeName; }{code} In Hibernate 5 the hbm.xml mapping was very simple and straightforward: {code:xml}<?xml version="1.0"?> <!DOCTYPE hibernate-mapping PUBLIC "-//Hibernate/Hibernate Mapping DTD 3.0//EN" "http://www.hibernate.org/dtd/hibernate-mapping-3.0.dtd"> <hibernate-mapping default-access="field" default-cascade="all"> <class name="event.StoredEvent" table="stored_event" lazy="true"> <id name="eventId" type="long" column="event_id" unsaved-value="-1"> <generator class="identity" /> </id> <property name="event" type="port.adapter.persistence.hibernate.DomainEventUserType"> <column name="event_body"/> <column name="type_name"/> </property> <property name="typeName" column="type_name" insert="false" update="false"/> <property name="occurredOn" column="occurred_on"/> </class> </hibernate-mapping>{code} The DomainEventUserType was also more or less simple to write :. Testing does work well, and I have provided a reproduced using the test-case-templates on my github: [https://github.com/itsmoonrack/hibernate-test-case-templates|https://gith...] I understand hbm.xml multiple <column/> now disallowed In 6.0 the support for basic property mappings with multiple columns was removed. The only use case for that was when a {{CompositeUserType}} was in use, which was reworked to now work on top of components. In Hibernate 6.0 I did not successfully migrated this composite user type and in fact I tried multiple strategies (implementing the new CompositeUserType) but failed successfully. I tried the following: {code:xml}<component name="event" class="port.adapter.persistence.hibernate.DomainEventUserType">  <property name="eventBody" column="event_body"/> <property name="typeName" column="type_name"/> </component>{code} but the metamodel mapper is telling me that it “*Could not locate field name [eventBody] on class [domain.model.DomainEvent]*” I also tried to embbed a component {code:java}public class StoredEventThatMayWork { private ComponentMapped event; private long eventId; private Instant occurredOn; public StoredEventThatMayWork(final DomainEvent event) { this.event = new ComponentMapped(event, event.getClass().getName()); this.occurredOn = event.occurredOn(); } public static class ComponentMapped { private DomainEvent eventBody; private String typeName; public ComponentMapped(final DomainEvent event, final String typeName) { this.eventBody = event; this.typeName = typeName; } } }{code} but it did not worked either: *Could not determine recommended JdbcType for* {{domain.model.DomainEvent}} Either there is something I did not understood, either this functionality has been broken starting from 6.0, and I am currently blocked by this. Any way of having this fonctionality working for 6.0 ? I have provided three tests classes: * hibernate-orm-5/ORMUnitTestCase which does work as expected * hibernate-orm-6/ORMUnitTestCase which yield *Could not locate field name [eventBody] on class [domain.model.DomainEvent]* * hibernate-orm-6/ORMUnitTestCaseThatMayWork with the component approach but yields *Could not determine recommended JdbcType for* {{domain.model.DomainEvent}} see reproduced test case here: [https://github.com/itsmoonrack/hibernate-test-case-templates/tree/main/or...] Any help would be greatly appreciated, if its not a bug, then it might be a documentation bug to provide a migration path. I would be happy to write such a documentation if missing. ( https://hibernate.atlassian.net/browse/HHH-16232#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16232#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#100217- sha1:077879e )

1 year, 3 months

1
0
0 / 0

[JIRA] (HHH-16232) CompositeUserType change in 6.0 make impossible to migrate multi-column mapping

by Sylvain Lecoy (JIRA)

Sylvain Lecoy ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiZTI4NmQ3ZGM0... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16232?atlOrigin=eyJpIjoiZTI4Nm... ) HHH-16232 ( https://hibernate.atlassian.net/browse/HHH-16232?atlOrigin=eyJpIjoiZTI4Nm... ) CompositeUserType change in 6.0 make impossible to migrate multi-column mapping ( https://hibernate.atlassian.net/browse/HHH-16232?atlOrigin=eyJpIjoiZTI4Nm... ) Change By: Sylvain Lecoy ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) I am working with a domain model class which is composed of an embedded object which implements the DomainEvent interface. DomainEvent can be any concrete class and is serialized by Jackson. To solve this in hibernate 5 I have used a CompositeUserType over two columns: event_body, and type_name. {code:java}public class StoredEvent { private DomainEvent event; private long eventId; private Instant occurredOn; private String typeName; }{code} In Hibernate 5 the hbm.xml mapping was very simple and straightforward: {code:xml}<?xml version="1.0"?> <!DOCTYPE hibernate-mapping PUBLIC "-//Hibernate/Hibernate Mapping DTD 3.0//EN" "http://www.hibernate.org/dtd/hibernate-mapping-3.0.dtd"> <hibernate-mapping default-access="field" default-cascade="all"> <class name="event.StoredEvent" table="stored_event" lazy="true"> <id name="eventId" type="long" column="event_id" unsaved-value="-1"> <generator class="identity" /> </id> <property name="event" type="port.adapter.persistence.hibernate.DomainEventUserType"> <column name="event_body"/> <column name="type_name"/> </property> <property name="typeName" column="type_name" insert="false" update="false"/> <property name="occurredOn" column="occurred_on"/> </class> </hibernate-mapping>{code} The DomainEventUserType was also more or less simple to write: Testing does work well, and I have provided a reproduced using the test-case-templates on my github: [https://github.com/itsmoonrack/hibernate-test-case-templates|https://gith...] In Hibernate 6.0 I did not successfully migrated this composite user type and in fact I tried multiple strategies (implementing the new CompositeUserType) but failed successfully. I tried the following: {code:xml}<component name="event" class="port.adapter.persistence.hibernate.DomainEventUserType">  <property name="eventBody" column="event_body"/> <property name="typeName" column="type_name"/> </component>{code} but the metamodel mapper is telling me that it “*Could not locate field name [eventBody] on class [domain.model.DomainEvent]*” I also tried to embbed a component {code:java}public class StoredEventThatMayWork { private ComponentMapped event; private long eventId; private Instant occurredOn; public StoredEventThatMayWork(final DomainEvent event) { this.event = new ComponentMapped(event, event.getClass().getName()); this.occurredOn = event.occurredOn(); } public static class ComponentMapped { private DomainEvent eventBody; private String typeName; public ComponentMapped(final DomainEvent event, final String typeName) { this.eventBody = event; this.typeName = typeName; } } }{code} but it did not worked either: *Could not determine recommended JdbcType for* {{domain.model.DomainEvent}} Either there is something I did not understood, either this functionality has been broken starting from 6.0, and I am currently blocked by this. Any way of having this fonctionality working for 6.0 ? I have provided three tests classes: * hibernate-orm-5/ORMUnitTestCase which does work as expected * hibernate-orm-6/ORMUnitTestCase which yield *Could not locate field name [eventBody] on class [domain.model.DomainEvent]* * hibernate-orm-6/ORMUnitTestCaseThatMayWork with the component approach but yields *Could not determine recommended JdbcType for* {{domain.model.DomainEvent}} see reproduced test case here: [https://github.com/itsmoonrack/hibernate-test-case-templates/tree/main/or...] Any help would be greatly appreciated, if its not a bug, then it might be a documentation bug to provide a migration path. I would be happy to write such a documentation if missing. ( https://hibernate.atlassian.net/browse/HHH-16232#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16232#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#100217- sha1:077879e )

1 year, 3 months

1
0
0 / 0

[JIRA] (HHH-16232) CompositeUserType change in 6.0 make impossible to migrate multi-column mapping

by Sylvain Lecoy (JIRA)

Sylvain Lecoy ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNzExY2Y2NDIy... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16232?atlOrigin=eyJpIjoiNzExY2... ) HHH-16232 ( https://hibernate.atlassian.net/browse/HHH-16232?atlOrigin=eyJpIjoiNzExY2... ) CompositeUserType change in 6.0 make impossible to migrate multi-column mapping ( https://hibernate.atlassian.net/browse/HHH-16232?atlOrigin=eyJpIjoiNzExY2... ) Change By: Sylvain Lecoy ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) I am working with a domain model class which is composed of an embedded object which implements the DomainEvent interface. DomainEvent can be any concrete class and is serialized by Jackson. To solve this in hibernate 5 I have used a CompositeUserType over two columns: event_body, and type_name. {code:java}public class StoredEvent { private DomainEvent event; private long eventId; private Instant occurredOn; private String typeName; }{code} In Hibernate 5 the hbm.xml mapping was very simple and straightforward: {code:xml}<?xml version="1.0"?> <!DOCTYPE hibernate-mapping PUBLIC "-//Hibernate/Hibernate Mapping DTD 3.0//EN" "http://www.hibernate.org/dtd/hibernate-mapping-3.0.dtd"> <hibernate-mapping default-access="field" default-cascade="all"> <class name="event.StoredEvent" table="stored_event" lazy="true"> <id name="eventId" type="long" column="event_id" unsaved-value="-1"> <generator class="identity" /> </id> <property name="event" type="port.adapter.persistence.hibernate.DomainEventUserType"> <column name="event_body"/> <column name="type_name"/> </property> <property name="typeName" column="type_name" insert="false" update="false"/> <property name="occurredOn" column="occurred_on"/> </class> </hibernate-mapping>{code} The DomainEventUserType was also more or less simple to write: Testing does work well, and I have provided a reproduced using the test-case-templates on my github: [https://github.com/itsmoonrack/hibernate-test-case-templates|https://gith...] In Hibernate 6.0 I did not successfully migrated this composite user type and in fact I tried multiple strategies (implementing the new CompositeUserType) but failed successfully. I tried the following: {code:xml}<component name="event" class="port.adapter.persistence.hibernate.DomainEventUserType">  <property name="eventBody" column="event_body"/> <property name="typeName" column="type_name"/> </component>{code} but the metamodel mapper is telling me that it “*Could not locate field name [eventBody] on class [domain.model.DomainEvent]*” I also tried to embbed a component {code:java}public class StoredEventThatMayWork { private ComponentMapped event; private long eventId; private Instant occurredOn; public StoredEventThatMayWork(final DomainEvent event) { this.event = new ComponentMapped(event, event.getClass().getName()); this.occurredOn = event.occurredOn(); } public static class ComponentMapped { private DomainEvent eventBody; private String typeName; public ComponentMapped(final DomainEvent event, final String typeName) { this.eventBody = event; this.typeName = typeName; } } }{code} but it did not worked either: *Could not determine recommended JdbcType for* {{domain.model.DomainEvent}} ( https://hibernate.atlassian.net/browse/HHH-16232#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16232#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#100217- sha1:077879e )

1 year, 3 months

1
0
0 / 0

[JIRA] (HHH-16232) CompositeUserType change in 6.0 make impossible to migrate multi-column mapping

by Sylvain Lecoy (JIRA)

Sylvain Lecoy ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMTdjYThkNmM3... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16232?atlOrigin=eyJpIjoiMTdjYT... ) HHH-16232 ( https://hibernate.atlassian.net/browse/HHH-16232?atlOrigin=eyJpIjoiMTdjYT... ) CompositeUserType change in 6.0 make impossible to migrate multi-column mapping ( https://hibernate.atlassian.net/browse/HHH-16232?atlOrigin=eyJpIjoiMTdjYT... ) Issue Type: Bug Affects Versions: 6.0.0 Assignee: Unassigned Components: hibernate-core, metamodel Created: 26/Feb/2023 03:09 AM Priority: Major Reporter: Sylvain Lecoy ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) I am working with a domain model class which is composed of an embedded object which implements the DomainEvent interface. DomainEvent can be any concrete class and is serialized by Jackson. To solve this in hibernate 5 I have used a CompositeUserType over two columns: event_body, and type_name. public class StoredEvent { private DomainEvent event; private long eventId; private Instant occurredOn; private String typeName; } In Hibernate 5 the hbm.xml mapping was very simple and straightforward: <?xml version= "1.0" ?> <!DOCTYPE hibernate-mapping PUBLIC "-//Hibernate/Hibernate Mapping DTD 3.0//EN" "http://www.hibernate.org/dtd/hibernate-mapping-3.0.dtd" > <hibernate-mapping default-access= "field" default-cascade= "all" > <class name= "event.StoredEvent" table= "stored_event" lazy= "true" > <id name= "eventId" type= "long" column= "event_id" unsaved-value= "-1" > <generator class= "identity" /> </id> <property name= "event" type= "port.adapter.persistence.hibernate.DomainEventUserType" > <column name= "event_body" /> <column name= "type_name" /> </property> <property name= "typeName" column= "type_name" insert= "false" update= "false" /> <property name= "occurredOn" column= "occurred_on" /> </class> </hibernate-mapping> ( https://hibernate.atlassian.net/browse/HHH-16232#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16232#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#100217- sha1:077879e )

1 year, 3 months

1
0
0 / 0

[JIRA] (HHH-16231) Bug for 1:n with abstract entities - random console output - application stuck

by Daniel Mertins (JIRA)

Daniel Mertins ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiYTgxMmQ4N2Jm... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16231?atlOrigin=eyJpIjoiYTgxMm... ) HHH-16231 ( https://hibernate.atlassian.net/browse/HHH-16231?atlOrigin=eyJpIjoiYTgxMm... ) Bug for 1:n with abstract entities - random console output - application stuck ( https://hibernate.atlassian.net/browse/HHH-16231?atlOrigin=eyJpIjoiYTgxMm... ) Issue Type: Bug Affects Versions: 6.1.7 Assignee: Unassigned Attachments: grafik-20230226-104633.png Components: query-criteria Created: 26/Feb/2023 02:48 AM Environment: Spring Boot 3 / JPA Jakarta / Hibernate 6+ Priority: Critical Reporter: Daniel Mertins ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) I tried to setup a unit test with h2-db and the new spring boot 3. ( https://hibernate.atlassian.net/secure/attachment/50231/50231_grafik-2023... ) Starting the tests results in 100+% CPU and random console output. openjdk 17.0.5 2022-10-18 OpenJDK Runtime Environment (build 17.0.5+8-Ubuntu-2ubuntu120.04) OpenJDK 64-Bit Server VM (build 17.0.5+8-Ubuntu-2ubuntu120.04, mixed mode, sharing) There is a dependency with Collection of Abstract Entities. If i remove the Collection<Abstract> then everything work fine again. *Example-Test Repository to checkout for yourself:* https://github.com/mertins-codamic/hibernate-3-bug ( https://github.com/mertins-codamic/hibernate-3-bug ) ( https://hibernate.atlassian.net/browse/HHH-16231#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16231#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#100217- sha1:077879e )

1 year, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues February 2023