August 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (ANN-721) ManyToOne Persisting Cascade in Embeddable

by Endre Jeges (JIRA)

ManyToOne Persisting Cascade in Embeddable ------------------------------------------ Key: ANN-721 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-721 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.3.1.GA Environment: Java version: java version "1.6.0_04" Java(TM) SE Runtime Environment (build 1.6.0_04-b12) Java HotSpot(TM) Client VM (build 10.0-b19, mixed mode, sharing) Oracle Version: Oracle9i Enterprise Edition Release 9.2.0.8.0 - Production PL/SQL Release 9.2.0.8.0 - Production "CORE 9.2.0.8.0 Production" TNS for Linux: Version 9.2.0.8.0 - Production NLSRTL Version 9.2.0.8.0 - Production hibernate: 3.2.6.ga hibernate-annotations: 3.3.1.ga hibernate-commons-annotations: 3.3.0.ga hibernate-entitymanager: 3.3.1.ga Reporter: Endre Jeges Attachments: pairTest.zip Hello, I have found something that is a bit strange. For @ManyToOne association properties in an @Embeddable class the cascade PERSIST, SAVE-UPDATE option is not working well (not sure for the other cascade types), if the entities associated with ManyToOne are transient. I have created a unit test to check it and I have it attached to this issue. It is a maven2 project, and needs Oracle to run it. If I save the associated entites, then everything works fine, also the data structure is created well. I have checked the forums and found similar problems, maybe they can help more then my post: http://forum.hibernate.org/viewtopic.php?t=965238 http://forum.hibernate.org/viewtopic.php?t=976534 http://forum.hibernate.org/viewtopic.php?t=978112 http://forum.hibernate.org/viewtopic.php?t=978138 http://forum.hibernate.org/viewtopic.php?t=983766 http://forum.hibernate.org/viewtopic.php?t=983780 http://forum.hibernate.org/viewtopic.php?t=983868 Details: @Entity class CodedPairHolder { @Id private Long id; @Column(name = "CODE", nullable = false, unique = true, updatable = false, length = 256) private String code; @CollectionOfElements @JoinTable(name = "CODED_PAIR_HOLDER_PAIR_SET", joinColumns = @JoinColumn(name = "CODED_PAIR_HOLDER_ID")) private final Set<PersonPair> pairs = new HashSet<PersonPair>(0); ........ constructors getters equals hashCode } @Embeddable class PersonPair { @ManyToOne(optional = false, fetch = FetchType.LAZY, cascade = { CascadeType.PERSIST, CascadeType.MERGE, CascadeType.REFRESH }) @Cascade( { org.hibernate.annotations.CascadeType.PERSIST, org.hibernate.annotations.CascadeType.MERGE, org.hibernate.annotations.CascadeType.REFRESH, org.hibernate.annotations.CascadeType.SAVE_UPDATE, org.hibernate.annotations.CascadeType.REPLICATE, org.hibernate.annotations.CascadeType.EVICT }) @JoinColumn(name = "LEFT_PERSON_ID", nullable = false, updatable = false) private Person left; @ManyToOne(optional = false, fetch = FetchType.LAZY, cascade = { CascadeType.PERSIST, CascadeType.MERGE, CascadeType.REFRESH }) @Cascade( { org.hibernate.annotations.CascadeType.PERSIST, org.hibernate.annotations.CascadeType.MERGE, org.hibernate.annotations.CascadeType.REFRESH, org.hibernate.annotations.CascadeType.SAVE_UPDATE, org.hibernate.annotations.CascadeType.REPLICATE, org.hibernate.annotations.CascadeType.EVICT }) @JoinColumn(name = "RIGHT_PERSON_ID", nullable = false, updatable = false) private Person right; ........ constructors getters equals hashCode } @Entity class Person { @Id private Long id; @Column(name = "NAME", nullable = false, unique = true, updatable = false, length = 256) private String name; ........ constructors getters equals hashCode } The error message is: org.hibernate.TransientObjectException: object references an unsaved transient instance - save the transient instance before flushing: Person Regards, jeges -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

7
16
0 / 0

[Hibernate-JIRA] Created: (HHH-6561) resolve attribute type in binder when the entity class is not a javabean

by Strong Liu (JIRA)

resolve attribute type in binder when the entity class is not a javabean ------------------------------------------------------------------------ Key: HHH-6561 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6561 Project: Hibernate Core Issue Type: Improvement Components: metamodel Reporter: Strong Liu Assignee: Strong Liu -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
3
0 / 0

[Hibernate-JIRA] Created: (HHH-6558) Bind @org.hibernate.annotations.Source

by Strong Liu (JIRA)

Bind @org.hibernate.annotations.Source -------------------------------------- Key: HHH-6558 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6558 Project: Hibernate Core Issue Type: Sub-task Components: metamodel Reporter: Strong Liu Assignee: Strong Liu -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-2738) Eager fetch support for StatelessSession

by Christian Bauer (JIRA)

Eager fetch support for StatelessSession ---------------------------------------- Key: HHH-2738 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2738 Project: Hibernate3 Issue Type: Task Components: core Reporter: Christian Bauer class Node { @ManyToOne(fetch = FetchType.EAGER) @JoinColumn(name = "PARENT_NODE_ID", nullable = true) protected Node parent; } StatelessSession ss = getStatelessSession(); Node node = (Node) ss.get(Node.class, nodeId); [testng] org.hibernate.AssertionFailure: possible non-threadsafe access to the session [testng] at org.hibernate.engine.TwoPhaseLoad.initializeEntity(TwoPhaseLoad.java:100) [testng] at org.hibernate.loader.Loader.initializeEntitiesAndCollections(Loader.java:854) [testng] at org.hibernate.loader.Loader.doQuery(Loader.java:729) [testng] at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:236) [testng] at org.hibernate.loader.Loader.loadEntity(Loader.java:1860) [testng] at org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:48) [testng] at org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:42) [testng] at org.hibernate.persister.entity.AbstractEntityPersister.load(AbstractEntityPersister.java:3042) [testng] at org.hibernate.impl.StatelessSessionImpl.get(StatelessSessionImpl.java:158) [testng] at org.hibernate.impl.StatelessSessionImpl.get(StatelessSessionImpl.java:153) [testng] at org.hibernate.impl.StatelessSessionImpl.get(StatelessSessionImpl.java:145) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3674) Expose SchemaUpdate#haltOnError as a configuration property

by Chris Bredesen (JIRA)

Expose SchemaUpdate#haltOnError as a configuration property ----------------------------------------------------------- Key: HHH-3674 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3674 Project: Hibernate Core Issue Type: New Feature Components: documentation, metamodel Reporter: Chris Bredesen Assignee: Chris Bredesen Priority: Minor SchemaUpdate currently collects and logs any Exceptions caught during its work. While the Exceptions are logged, Hibernate is allowed to startup successfully. This feature request allows for a setting to flip this behavior such that Hibernate will not start if one or more Exceptions are encountered during SchemaUpdate (in test environments, of course). Proposed configuration option is hibernate.hbm2ddl.haltOnError -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-6067) Infinispan custom commands to solve entity/collection region better

by Galder Zamarreno (JIRA)

Infinispan custom commands to solve entity/collection region better ------------------------------------------------------------------- Key: HHH-6067 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6067 Project: Hibernate Core Issue Type: Improvement Components: caching (L2) Reporter: Galder Zamarreno Assignee: Galder Zamarreno Provide a better solution for HHH-3818 using Infinispan's new SPI to define your own commands, ISPN-256 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-4713) Avoid using same cache instance for storing CacheValue and evictAll notifications

by Galder Zamarreno (JIRA)

Avoid using same cache instance for storing CacheValue and evictAll notifications --------------------------------------------------------------------------------- Key: HHH-4713 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4713 Project: Hibernate Core Issue Type: Bug Components: caching (L2) Affects Versions: 3.5.0-Beta-2 Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 3.5 Store evictAll information in a separate infinispan cache instance in order to avoid doing stuff like this in BaseRegion.toMap which could be quite expensive in the context of SecondLevelCacheStatistics calculations: public Map toMap() { if (checkValid()) { // If copying causes issues, provide a lazily loaded Map Map map = new HashMap(); Set<Map.Entry> entries = cacheAdapter.toMap().entrySet(); for (Map.Entry entry : entries) { Object key = entry.getKey(); if (!CacheHelper.isEvictAllNotification(key)) { map.put(key, entry.getValue()); } } return map; } return Collections.EMPTY_MAP; } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

3
10
0 / 0

[Hibernate-JIRA] Created: (HHH-5348) java.lang.IllegalArgumentException: Cannot create TypedQuery for query with more than one return with AbstractEntityManager.createQuery(String jpaqlString, Class<T> resultClass) on View object

by nodje (JIRA)

java.lang.IllegalArgumentException: Cannot create TypedQuery for query with more than one return with AbstractEntityManager.createQuery(String jpaqlString, Class<T> resultClass) on View object ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ Key: HHH-5348 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5348 Project: Hibernate Core Issue Type: Bug Components: entity-manager Affects Versions: 3.5.3 Reporter: nodje I'm getting a java.lang.IllegalArgumentException: Cannot create TypedQuery for query with more than one return with a query that returns a View object. AbstractEntityManager:279, detects as many returns type as there is parameters in the View object, instead of one single result type, the View Object itself. QueryString example that fails with public <T> TypedQuery<T> createQuery(String jpaqlString, Class<T> resultClass): "select new WorkContractDto(wc.workContractStartDate, wc.workContractEndDate, wc.workContractEmployeeLastName, wc.workContractSendingStatus) from WorkContract wc where wc.workContractEmployeeLastName = ?1" -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

15
38
0 / 0

[Hibernate-JIRA] Created: (HHH-5368) Not throwing Optimistic Lock when the entity is attached

by Fernando Rubbo (JIRA)

Not throwing Optimistic Lock when the entity is attached -------------------------------------------------------- Key: HHH-5368 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5368 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.2.4.sp1 Environment: windows XP, jboss 4.3 EAP, hibernate 3.4.2.sp1 Reporter: Fernando Rubbo Priority: Minor Hi Hibernate is not throwing Optimistic Lock when the entity is attached. It happens when the business rule sets a version in the attached entity that is less than its original (from database) version value. Take the following code as an example of the bug. // inserts A A a1 = new A(); a1.setName("A1"); dao.persist(a1); dao.flush(); dao.clear(); // as expected, the piece of code below works just fine final A a2 = dao.find(A.class, new BigDecimal(1)); a2.setName("A2"); dao.merge(a2); dao.flush(); dao.clear(); // as expected, this code fails due to Optimistic Lock try{ final A a3 = dao.find(A.class, new BigDecimal(1)); dao.clear(); a3.setName("A3"); a3.setVersion(0); //database verison is 1 dao.merge(a3); dao.flush(); Assert.fail(); }catch (Exception e) { System.out.println(e.getMessage()); // ignore }finally{ dao.clear(); } // unexpectedly, the piece of code below also works.. // even with the version being less than the one in the database // Note that this happens because hibernate is holding internaly the original version of the entity. // Even when the version is manually changed it keeps using the original one. final A a3 = dao.find(A.class, new BigDecimal(1)); a3.setName("A3"); a3.setVersion(0); //database verison is 1 dao.merge(a3); dao.flush(); dao.clear(); This problem can be handled by the business rule. For example, whether the version that comes from the screen is smaller than the one from the database it could throw an Optimistic Lock exception. However, it it was not handled, hibernate must take care of this in the same way it does with detached objects. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HV-491) Add support for MOD11 Algorithm

by George Gastaldi (JIRA)

Add support for MOD11 Algorithm ------------------------------- Key: HV-491 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-491 Project: Hibernate Validator Issue Type: Improvement Components: validators Reporter: George Gastaldi It would be nice to add support for the MOD11 algorithm. It is described on http://joselop.es/mod-11 or http://en.wikipedia.org/wiki/MSI_Barcode#Mod_11_Check_Digit and it is widely used on Brazil, such as CPF (Cadastro de Pessoa Física - http://en.wikipedia.org/wiki/Cadastro_de_Pessoas_F%C3%ADsicas), CNPJ (Cadastro de Pessoa Jurídica - National Registry of Corporations) and Título de Eleitor (Voter ID card) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
20
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues August 2011