August 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-3872) Criteria on alias causes partial collection materialization

by Adrian Moos (JIRA)

Criteria on alias causes partial collection materialization ----------------------------------------------------------- Key: HHH-3872 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3872 Project: Hibernate Core Issue Type: Bug Components: query-criteria Affects Versions: 3.3.0.CR1 Reporter: Adrian Moos I have a parent entity with a one-to-many assocation to a child entity: <hibernate-mapping package="ch.bedag.a11.ccinfo.business.entity" default-lazy="false"> <class name="Parent" table="PARENT"> <id name="id" type="long" column="ID" unsaved-value="null"> <generator class="sequence"> <param name="sequence">SEQ_T_PARENT</param> </generator> </id> <set name="children" cascade="all-delete-orphan" inverse="true"> <key column="PARENT_ID" foreign-key="CHILD_FK1"/> <one-to-many class="Child"/> </set> </class> <class name="Child" <id name="id" type="long" column="ID" unsaved-value="null"> <generator class="sequence"> <param name="sequence">SEQ_T_CHILD</param> </generator> </id> <property name="businessKey" column="BUSINESSKEY" not-null="true"/> </class> </hibernate-mapping> I then do: Criteria parentCriteria = aSession.createCriteria(Parent.class); parentCriteria.createAlias("children", "c", CriteriaSpecification.LEFT_JOIN); parentCriteria.setResultTransformer(CriteriaSpecification.DISTINCT_ROOT_ENTITY); parentCriteria.add(Restrictions.eq("c.businessKey", 123456789)); List parents = parentCriteria.list(); Expected behaviour: Since each parent in parents is a materialized entity, I'd expect its children set to contain all its children. Observed behaviour: It contains only children with matching business key. Is my expectation correct? -- 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

13 years, 8 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-4878) Add documentation about new "image" and "text" properties

by Gail Badner (JIRA)

Add documentation about new "image" and "text" properties --------------------------------------------------------- Key: HHH-4878 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4878 Project: Hibernate Core Issue Type: Improvement Components: documentation Reporter: Gail Badner Assignee: Gail Badner Fix For: 3.5 -- 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

13 years, 8 months

3
18
0 / 0

[Hibernate-JIRA] Created: (HHH-5430) Better Firebird support - temp tables, short column names

by Martin Černý (JIRA)

Better Firebird support - temp tables, short column names --------------------------------------------------------- Key: HHH-5430 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5430 Project: Hibernate Core Issue Type: Improvement Components: core Affects Versions: 3.5.3 Reporter: Martin Černý Priority: Minor Attachments: Firebird21Dialect.java, GenericLengthLimitedNamingStrategy.java, LengthLimitedComponentSafeNamingStrategy.java Sorry for not posting in some more concise format or joining the development in an official way, however I hope it still helps. In my quest to make Firebird work with my Hibernate/JPA project I have developed two helper classes that (especially the first one) might as well be incorporated in the Hibernate. First I have subclassed FirebirdDialect to make use of temporary table support in Firebird 2.1 (this had blocked some of the JPA features) Then I have subclassed NamingStrategy to create a generic strategy that forces all the database identifiers to conform to certain length. This is needed since Firebird does not work with column and table names longer than 30 chars. Although I am not certain, if this should be part of Hibernate. The class I created are attached, their utility is up to the consideration of the community -- 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

13 years, 8 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3230) getEntityName() throws org.hibernate.TransientObjectException: proxy was not associated with the session

by Howard M. Lewis Ship (JIRA)

getEntityName() throws org.hibernate.TransientObjectException: proxy was not associated with the session -------------------------------------------------------------------------------------------------------- Key: HHH-3230 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3230 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.2 Environment: Mac OS X, JDK 1.5 Reporter: Howard M. Lewis Ship I'm retrieving an entity that contains a OneToMany relationship. The master entity is retrieved, within a transaction, via Session.get(Class,Serializable). @Entity public class MapUnitSurvey extends ActiveDO { @ManyToOne(fetch = FetchType.LAZY) private VegetationType vegetationType; } @Entity public class VegetationType extends AbstractEnum { } ActiveDO and AbstractEnum are abstract base classes with @MappedSuperclass. I retrieve the vegationType: VegetationType type = survey.getVegetationType(); Then I need the type's entity name String entityName = session.getEntityName(type); This fails with the TransientObjectException. Inspecting with the debugger, I see that type is a CGLIB-enhanced proxy, and that there's a fully initialized bean in the target field of the proxy. I'll attach a screenshot of some debugging data. In summary; the entity was retrieved via a lazy fetch, appears the be correct, seems to be in the session and yet the exception occurs. I've tried to resolve this by re-fetching the object from the session, and a few other tries, with no luck. -- 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

13 years, 8 months

4
10
0 / 0

[Hibernate-JIRA] Created: (HHH-3332) Hibernate duplicate then child entity's on merge

by Rodrigo de Assumpção (JIRA)

Hibernate duplicate then child entity's on merge ------------------------------------------------ Key: HHH-3332 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3332 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.6 Environment: JDK 1.6 Oracle 9i Hibernate 3.2.6 Hibernate Annotations 3.3.1 Hibernate EntityManager 3.3.2 Standalone Running Reporter: Rodrigo de Assumpção Priority: Critical The method merge from EntityManager causes a duplication of child entity's. class Father: @OneToMany(mappedBy = "father", cascade={CascadeType.ALL}, fetch=FetchType.LAZY) private List<Child> childList; class Child: @ManyToOne @JoinColumn(name = "ID_FATHER") private Father father; class BugTest EntityManagerFactory emf = Persistence.createEntityManagerFactory("JpaTestHB"); EntityManager em = emf.createEntityManager(); Father f = (Father) em.createQuery("SELECT f FROM Father f WHERE f.id = 1").getSingleResult(); Child c = new Child(); c.setFather(f); f.getChildList().add(c); em.getTransaction().begin(); em.merge(f); em.getTransaction().commit(); The execution of BugTest Class causes tow insert's on table "child". If you change the fetch mode to EAGER (into Father class) the problem not occurs. I make the same test with Toplink, and it make a unique insert, normal. -- 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

13 years, 8 months

13
29
0 / 0

[Hibernate-JIRA] Created: (HV-272) jaxb dependencies should be dependencies with scope 'provided' instead of profile dependencies

by Hardy Ferentschik (JIRA)

jaxb dependencies should be dependencies with scope 'provided' instead of profile dependencies ---------------------------------------------------------------------------------------------- Key: HV-272 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-272 Project: Hibernate Validator Issue Type: Bug Components: build Affects Versions: 4.0.2.GA Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Priority: Minor Fix For: 4.1.0 -- 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

13 years, 8 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5359) Derived entity usecase fails when the association is bidirectional

by Hardy Ferentschik (JIRA)

Derived entity usecase fails when the association is bidirectional ------------------------------------------------------------------ Key: HHH-5359 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5359 Project: Hibernate Core Issue Type: Bug Components: entity-manager Affects Versions: 3.5.3 Reporter: Hardy Ferentschik Fix For: 3.6 See https://forum.hibernate.org/viewtopic.php?f=9&t=1005649 The exception is {noformat} org.hibernate.AnnotationException: mappedBy reference an unknown target entity property: org.hibernate.test.annotations.derivedidentities.bidirectional.Dependent.emp in org.hibernate.test.annotations.derivedidentities.bidirectional.Employee.dependents at org.hibernate.cfg.annotations.CollectionBinder.bindStarToManySecondPass(CollectionBinder.java:655) at org.hibernate.cfg.annotations.CollectionBinder$1.secondPass(CollectionBinder.java:619) at org.hibernate.cfg.CollectionSecondPass.doSecondPass(CollectionSecondPass.java:66) at org.hibernate.cfg.Configuration.secondPassCompile(Configuration.java:1221) at org.hibernate.cfg.AnnotationConfiguration.secondPassCompile(AnnotationConfiguration.java:383) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1377) at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:954) at org.hibernate.test.annotations.TestCase.buildConfiguration(TestCase.java:114) at org.hibernate.test.annotations.HibernateTestCase.setUp(HibernateTestCase.java:133) at org.hibernate.test.annotations.HibernateTestCase.runBare(HibernateTestCase.java:80) at com.intellij.junit3.JUnit3IdeaTestRunner.doRun(JUnit3IdeaTestRunner.java:108) at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:64) {noformat} The mapping is as follows: {code} @Entity public class Employee { @Id long empId; String empName; @OneToMany(mappedBy = "emp", fetch = FetchType.LAZY) private Set<Dependent> dependents; } {code} {code} @Entity //(a)IdClass(DependentId.class) public class Dependent implements Serializable { @Id @ManyToOne Employee emp; String name; } {code} It does not work with @IdClass either. -- 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

13 years, 8 months

4
13
0 / 0

[Hibernate-JIRA] Created: (HHH-5466) Create "Developer Guide"

by Steve Ebersole (JIRA)

Create "Developer Guide" ------------------------ Key: HHH-5466 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5466 Project: Hibernate Core Issue Type: Improvement Components: documentation Reporter: Steve Ebersole This is the more "action" or "story" based documentation -- 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

13 years, 8 months

2
22
0 / 0

[Hibernate-JIRA] Created: (HHH-5280) "java.lang.IllegalArgumentException: object is not an instance of declaring class" when persisting a object graph containing the same transient objetc twice.

by Benjamin Lerman (JIRA)

"java.lang.IllegalArgumentException: object is not an instance of declaring class" when persisting a object graph containing the same transient objetc twice. ------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-5280 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5280 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.2 Environment: Hibernate 3.5.2 Db: All? (At least h2 and mysql) Reporter: Benjamin Lerman Priority: Critical Attachments: hibernate-multi-parent.tgz, test.entity.TestCreate.txt I attach a maven project showing the bug. I have 3 classes, A, B, C with C have a one-to-many unidirectional relation to B and A. B have a one-to-many unidirectional relation to A. Those relations are mapped by foreign keys. The cascading properties for those relations are all save-update,persist For each of those relations, the inverse cardinality is 1 (which means A must be associated with a B and a C, and B must be associated with a C). I create an instance of C that I associate to an instance of B and an instance of A, and I associate the instance of B with the instance of A. I then try to save C, and I get the attached exception. For what I understood the problem is with the method StatefulPersistenceContext.getOwnerId: this method use a cache to retrieve the parent of the instance of A, but because A has 2 different parents (the instance of B and the instance of C), it does not retrieve the right one and try to call a method on the wrong entity. -- 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

13 years, 8 months

6
9
0 / 0

[Hibernate-JIRA] Created: (HHH-3608) DB sequence numbers are not unique when using the pooled SequenceStyleGenerator in multiple JVMs with the same DB

by Matthias Gommeringer (JIRA)

DB sequence numbers are not unique when using the pooled SequenceStyleGenerator in multiple JVMs with the same DB ----------------------------------------------------------------------------------------------------------------- Key: HHH-3608 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3608 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1, 3.3.0.SP1, 3.3.0.GA, 3.2.6 Environment: Hibernate 3.2.6, Oracle (any version) Reporter: Matthias Gommeringer Priority: Blocker Attachments: PooledOptimizerTest.java We have several Application Servers (=JVMs) running each of them using Hibernate-Objects with the SequenceStyleGenerator+pooled configured. In unpredictable time intervals it happens that hibernate assigns the same ID to two completely different objects which results in a UniqueConstraintViolation exception from the database. Here an example with a description where hibernate fails: DB-Sequence setup: start=0 increment=2 PooledOptimizer.generate() with 2 threads (first assignment of hiValue/value): JVM-1 JVM-2 value=0=callback.nextval value=2=callback.nextval hiValue=4=callback.nextval hiValue=6=callback.nextval The problem's cause is in the PooledOptimizer.generate: when it initializes the value+hiValue for the first time it invokes callback.nextValue() twice which may provide values that do not belong to each other. The reason is that between the assignment of "value" and "hiValue" another JVM can retrieve a DB sequence value from the callback which leads to an inconsistent "value" and "hiValue" relation (see example above). A fix that works for multiple JVMs would be to invoke the "callback.getNextValue()" maximum once per "optimizer.generate()" call: public synchronized Serializable generate(AccessCallback callback) { if ( hiValue < 0 ) { value = callback.getNextValue(); hiValue = value + incrementSize; } else if ( value >= hiValue ) { value = callback.getNextValue(); hiValue = value + incrementSize; } return make(value++); } I attached a testcase that prooves the described problem (you can see that the IDs "2" and "3" are assigned two times). I would be very thankful if this problem could be fixed very soon since it is a showstopper which occurs very unpredictably. -- 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

13 years, 8 months

15
40
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues August 2010