July 2020 - hibernate-issues - Jboss List Archives

[JIRA] (HHH-12268) LazyInitializationException thrown from lazy collection when batch fetching enabled and owning entity refreshed with lock

by Gail Badner (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HV-1791) Cascading validation on list items is not invoked

by Alex Fedotov (JIRA)

Alex Fedotov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate Validator ( https://hibernate.atlassian.net/browse/HV?atlOrigin=eyJpIjoiM2RkOGMzNDlmM... ) / Bug ( https://hibernate.atlassian.net/browse/HV-1791?atlOrigin=eyJpIjoiM2RkOGMz... ) HV-1791 ( https://hibernate.atlassian.net/browse/HV-1791?atlOrigin=eyJpIjoiM2RkOGMz... ) Cascading validation on list items is not invoked ( https://hibernate.atlassian.net/browse/HV-1791?atlOrigin=eyJpIjoiM2RkOGMz... ) Issue Type: Bug Affects Versions: 6.1.5.Final Assignee: Unassigned Components: engine Created: 17/Jul/2020 09:26 AM Priority: Major Reporter: Alex Fedotov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Trying to validate a POJO with nested collection that requires item validation class TestTopLevel { public List<@Valid TestDetails> data = new ArrayList<>(); } class TestDetails { @NotEmpty public String large = ""; } TestTopLevel topLevelValue = new TestTopLevel(); TestDetails details = new TestDetails(); topLevelValue.data = new ArrayList<>(); topLevelValue.data.add(details); Both validateProperty and validateValue fail to validate the list items. violations = validator.validateProperty(topLevelValue, "data"); violations = validator.validateValue(TestTopLevel.class, "data", topLevelValue); It appears that the issue is in the validationContext.appliesTo( metaConstraint ) call. metaConstraint is correctly pointing to the "large" property of the item in the list when it gets there. However "validatedProperty" value at this point is "data" from the top level class. @Override public boolean appliesTo(MetaConstraint<?> metaConstraint) { return Objects.equals( validatedProperty, getPropertyName( metaConstraint.getLocation() ) ); } private boolean validateMetaConstraint(BaseBeanValidationContext<?> validationContext, ValueContext<?, Object> valueContext, Object parent, MetaConstraint<?> metaConstraint) { BeanValueContext.ValueState<Object> originalValueState = valueContext.getCurrentValueState(); valueContext.appendNode( metaConstraint.getLocation() ); boolean success = true; if ( isValidationRequired( validationContext, valueContext, metaConstraint ) ) { The equals check fails and the validation of the item is skipped because isValidationRequired returns false. ( https://hibernate.atlassian.net/browse/HV-1791#add-comment?atlOrigin=eyJp... ) Add Comment ( https://hibernate.atlassian.net/browse/HV-1791#add-comment?atlOrigin=eyJp... ) 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#100133- sha1:d093d11 )

3 years, 11 months

1
0
0 / 0

[JIRA] (WEBSITE-592) Broken link: http://hibernate.org/dtd/hibernate-configuration-3.0.dtd%22>

by Yoann Rodière (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (WEBSITE-592) Broken link: http://hibernate.org/dtd/hibernate-configuration-3.0.dtd%22>

by Website Form collector (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-14111) Upgrade build dependencies to tests JDK15/JDK16

by Yoann Rodière (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HSEARCH-3964) Build and run tests against JDK16

by Yoann Rodière (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-13410) "order_inserts = true" causes FK Violation when inserting with a special case of Unidirectional Relations between 4 Entities

by Gajendra Kumar (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-13410) "order_inserts = true" causes FK Violation when inserting with a special case of Unidirectional Relations between 4 Entities

by Gajendra Kumar (JIRA)

Gajendra Kumar ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-13410 ( https://hibernate.atlassian.net/browse/HHH-13410?atlOrigin=eyJpIjoiYjVlNz... ) Re: "order_inserts = true" causes FK Violation when inserting with a special case of Unidirectional Relations between 4 Entities ( https://hibernate.atlassian.net/browse/HHH-13410?atlOrigin=eyJpIjoiYjVlNz... ) This issue is due to below code in ActionQueue as nextBatchIdentifier.parent is assigned a parent. There can be multiple parents but with this code only one parent reference is being hold. for ( int j = i + 1; j < latestBatches.size(); j++ ) { BatchIdentifier nextBatchIdentifier = latestBatches.get( j ); if ( nextBatchIdentifier.hasAnyParentEntityNames( batchIdentifier ) ) { nextBatchIdentifier.parent = batchIdentifier; } if ( batchIdentifier.hasAnyChildEntityNames( nextBatchIdentifier ) ) { nextBatchIdentifier.parent = batchIdentifier; } } Fix: parent should be added to nextBatchIdentifier.parentEntityNames for ( int j = i + 1; j < latestBatches.size(); j++ ) { BatchIdentifier nextBatchIdentifier = latestBatches.get( j ); if ( nextBatchIdentifier.hasAnyParentEntityNames( batchIdentifier ) ) { nextBatchIdentifier.parent = batchIdentifier; nextBatchIdentifier.getParentEntityNames().add(batchIdentifier.getEntityName()); } if ( batchIdentifier.hasAnyChildEntityNames( nextBatchIdentifier ) ) { nextBatchIdentifier.parent = batchIdentifier; nextBatchIdentifier.getParentEntityNames().add(batchIdentifier.getEntityName()); } } I’ll create pull request soon 🙂 ( https://hibernate.atlassian.net/browse/HHH-13410#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-13410#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#100133- sha1:d093d11 )

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-14111) Upgrade build dependencies to tests JDK15/JDK16

by Yoann Rodière (JIRA)

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-14110) "no transaction is in progress" when call entity manager find() with LockModeType

by Alex Popa-Tesileanu (JIRA)

Alex Popa-Tesileanu ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5f1170d... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMmE4ZThlMzFm... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-14110?atlOrigin=eyJpIjoiMmE4ZT... ) HHH-14110 ( https://hibernate.atlassian.net/browse/HHH-14110?atlOrigin=eyJpIjoiMmE4ZT... ) "no transaction is in progress" when call entity manager find() with LockModeType ( https://hibernate.atlassian.net/browse/HHH-14110?atlOrigin=eyJpIjoiMmE4ZT... ) Issue Type: Improvement Affects Versions: 5.4.18 Assignee: Unassigned Components: hibernate-core Created: 17/Jul/2020 03:26 AM Environment: java 11, hibernate 5.4.18, JTA: narayana-jta-5.9.0, SQL Server 2016 Windows 10 Labels: hibernate jta Priority: Major Reporter: Alex Popa-Tesileanu ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5f1170d... ) When I use entity manager find() method with LockModeType inside JTA transaction boundaries, throw fowling exception: _Exception in thread "main" javax.persistence.TransactionRequiredException: no transaction is in progress at org.hibernate.internal.AbstractSharedSessionContract.checkTransactionNeededForUpdateOperation(AbstractSharedSessionContract.java:413) at org.hibernate.internal.SessionImpl.checkTransactionNeededForUpdateOperation(SessionImpl.java:3395) at org.hibernate.internal.SessionImpl.find(SessionImpl.java:3310) at org.hibernate.internal.SessionImpl.find(SessionImpl.java:3292) at ro.alsoco.tt.test.TestJPA.run(TestJPA.java:71) at ro.alsoco.tt.test.TestJPA.main(TestJPA.java:24) _ This doesn't happen when I use for example createQuery or if i call clear() or flush() before find(). After a few research I saw the majority of entity manipulation methods of EntityManager (SessionImpl or AbstractSharedSessionContract classes) execute on begining pulseTransactionCoordinator(). But find() mehod not. I don't know if there are any special reason why find method not call pulseTransactionCoordinator(), witch I saw register synchronization with JTA. For the moment I solved my problem issuing a joinTransaction() as first command after begin transaction. Also, the problem doesn't happen if i create entity manager inside the JTA transaction. But I have strong resons to create entity manager outside the transaction. It is possible to call pulseTransactionCoordinator() in find() method as bellow? Maybe in next version? _@Override public <T> T find(Class<T> entityClass, Object primaryKey, LockModeType lockModeType, Map<String, Object> properties) { checkOpen(); pulseTransactionCoordinator(); ............. _ Thank you, Alex ( https://hibernate.atlassian.net/browse/HHH-14110#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-14110#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#100133- sha1:d093d11 )

3 years, 11 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 July 2020