February 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-2383) Generated SQL using setMaxResults/setFirstResult duplicate entities in the first page and subsequent pages in Oracle.

by Carlos Eugênio P. da Purificação (JIRA)

Generated SQL using setMaxResults/setFirstResult duplicate entities in the first page and subsequent pages in Oracle. --------------------------------------------------------------------------------------------------------------------- Key: HHH-2383 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2383 Project: Hibernate3 Type: Bug Components: query-hql Versions: 3.2.2 Environment: Hibernate 3.2.2 GA, Oracle 10 Reporter: Carlos Eugênio P. da Purificação Attachments: test.zip The generated SQL using setMaxResults/setFirstResult duplicate entities in the first page and subsequent pages. -- 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

17 years, 6 months

3
3
0 / 0

[Hibernate-JIRA] Created: (ANN-636) Add the annotations to map the User Collection Type

by jason (JIRA)

Add the annotations to map the User Collection Type --------------------------------------------------- Key: ANN-636 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-636 Project: Hibernate Annotations Issue Type: New Feature Components: binder Environment: n/a Reporter: jason I am searching a way from the Hibernate Annotation to map the user defined collection, and find out the following : Can anybody let me know what the status for this? or how i can map the user collection type by hibernate annotation, thanks Add an annotation to specify the UserCollectionType for a OneToMany or ManyToMany. The annotation is named CollectionTypeInfo, perhaps better named UserCollectionType, but I didn't know the standards for naming classes. The change to AnnotationBinder is minor and is delineated by '//dwsjoquist//' comment lines. Usage: @OneToMany(fetch = FetchType.LAZY, cascade = CascadeType.ALL) @JoinColumn(name = "id") @CollectionTypeInfo(name = "examples.MyUserCollectionType") public List<ExampleAttribute> getExampleAttributes() { -- 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

17 years, 6 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2787) Criteria Aggregate Projections do not JOIN additional tables on which restrictions apply

by Sami Dalouche (JIRA)

Criteria Aggregate Projections do not JOIN additional tables on which restrictions apply ---------------------------------------------------------------------------------------- Key: HHH-2787 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2787 Project: Hibernate3 Issue Type: Bug Components: query-criteria Affects Versions: 3.2.5 Environment: PostgreSQL Dialect Reporter: Sami Dalouche Priority: Critical Hi, When you have a Criteria Object, on which you : - Add Aggregate Projections such as rowCount() - createAlias("whatever").add(Restrictions.*..) It looks like that the "whatever" table is NOT joined, even though it is joined OK when the projections are not there. So, here is an approximate Unit test that should throw an exception (I couldn't create a complete test case since I couldn't get the unit tests to run on my machine -any link explaining this step somewhere ?): Criteria c1 = s.createCriteria(Enrolment.class) .setProjection( Projections.projectionList().add(Projections.rowCount(), "rowCount") ); Criteria studentCriteria = c1.createAlias("student", "st"); studentCriteria.add(Restrictions.eq("name", "whatevername")); It should complain saying the "st.name" alias does not exist, because the student class has not been joined. Regards, Sami Dalouche -- 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

17 years, 7 months

4
9
0 / 0

[Hibernate-JIRA] Created: (ANN-686) SubClass with EmbeddedId or IdClass containing @ManyToOne fail at startup

by Marcos Sousa (JIRA)

SubClass with EmbeddedId or IdClass containing @ManyToOne fail at startup ------------------------------------------------------------------------- Key: ANN-686 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-686 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.3.1.beta1, 3.3.0.ga Reporter: Marcos Sousa Priority: Minor I subclass Customer that has a EmbeddedId using JOIN inheritance strategy. My embeddable class has @ManyToOne relationship. Look the classes: Pesson class: @Entity @Table(name="person") public class Person { @Id private Integer personId; private String name; } Embeddable class ID. @Embeddable public class PersonPk implements Serializable { @ManyToOne(optional=false, cascade={CascadeType.PERSIST, CascadeType.REFRESH, CascadeType.REMOVE}, fetch=FetchType.EAGER) @JoinColumn(name="personId") private Person person; // ... getters and setters } CustomerClass: @Entity @Table(name="Customer") @Inheritance(strategy=InheritanceType.JOINED) public class Customer { @Id private PersonPk pk = new PersonPk(); } Regional Custumer: @Entity @Table(name="AmericanCustomer") @PrimaryKeyJoinColumn(name="personId") @IdClass(PessoaPk.class) public class AmericanCustomer extends Customer { // some american customer fields.. } This mapping throw this exception at hibernate startup: Invocation of init method failed; nested exception is java.util.NoSuchElementException Caused by: java.util.NoSuchElementException at java.util.AbstractList$Itr.next(Unknown Source) at org.hibernate.util.JoinedIterator.next(JoinedIterator.java:53) at org.hibernate.cfg.Ejb3JoinColumn.buildJoinColumn(Ejb3JoinColumn.java:210) at org.hibernate.cfg.AnnotationBinder.bindClass(AnnotationBinder.java:463) at org.hibernate.cfg.AnnotationConfiguration.processArtifactsOfType(AnnotationConfiguration.java:501) at org.hibernate.cfg.AnnotationConfiguration.secondPassCompile(AnnotationConfiguration.java:282) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1286) at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:918) -- 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

17 years, 7 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HBX-900) Support ctrl+shift+t in the Hibernate Console perspective

by Joseph Marques (JIRA)

Support ctrl+shift+t in the Hibernate Console perspective --------------------------------------------------------- Key: HBX-900 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-900 Project: Hibernate Tools Type: Bug Versions: 3.2beta8 Reporter: Joseph Marques In other perspectives, ctrl+shift+t will pop open a dialog that allows me to select some type (some class on the source path). I find myself wanting to work in the Hibernate perspective more often, but I'm hindered by the fact that I can't easily open new types with this shortcut. I took a look at "preferences > general > keys" but I didn't see anything that should prevent the shortcut from working in the Hibernate perspective. Oddly, ctrl+shift+r works in the perspective, and it seems to be set up nearly identically in the keyboard shortcuts. Is there something that I'm missing? -- 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

17 years, 7 months

3
4
0 / 0

[Hibernate-JIRA] Created: (ANN-688) Repeated columns created for single table inheritance

by Nick Heudecker (JIRA)

Repeated columns created for single table inheritance ----------------------------------------------------- Key: ANN-688 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-688 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.3.0.ga Environment: Hibernate 3.2.5ga, Postgresql Reporter: Nick Heudecker I have the following classes: @Entity @Inheritance(strategy= InheritanceType.SINGLE_TABLE) @DiscriminatorColumn(name="cltype", discriminatorType= DiscriminatorType.STRING, length=10) @DiscriminatorValue("device") public abstract class Device extends AbstractPersistent { private System system; @ManyToOne public System getSystem() { return system; } public void setSystem(System system) { this.system = system; } } @Entity @DiscriminatorValue("snmp") public class SnmpDevice extends Device { // .... additional properties defined } When I try to create the SessionFactory, I'm getting the following exception: Caused by: org.hibernate.MappingException: Repeated column in mapping for entity: model.SnmpDevice column: system_uuid (should be mapped with insert="false" update="false") at org.hibernate.mapping.PersistentClass.checkColumnDuplication(PersistentClass.java:652) at org.hibernate.mapping.PersistentClass.checkPropertyColumnDuplication(PersistentClass.java:674) at org.hibernate.mapping.PersistentClass.checkColumnDuplication(PersistentClass.java:696) at org.hibernate.mapping.PersistentClass.validate(PersistentClass.java:450) at org.hibernate.mapping.SingleTableSubclass.validate(SingleTableSubclass.java:43) at org.hibernate.cfg.Configuration.validate(Configuration.java:1102) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1287) -- 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

17 years, 7 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2937) NullPointException during flush if getSnapshot return null

by Emilio Dolce (JIRA)

NullPointException during flush if getSnapshot return null ---------------------------------------------------------- Key: HHH-2937 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2937 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.2 Environment: Windows Reporter: Emilio Dolce The method equalsSnapshot of the PersistentBag class do not check if returned snapshot is null causing a NullPointException. Please che the next condition with this: if ( sn == null || sn.size()!=bag.size() ) return false; -- 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

17 years, 7 months

3
4
0 / 0

[Hibernate-JIRA] Created: (EJB-331) StaleObjectStateException after removing two entities

by ludki (JIRA)

StaleObjectStateException after removing two entities ----------------------------------------------------- Key: EJB-331 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-331 Project: Hibernate Entity Manager Issue Type: Bug Components: EntityManager Affects Versions: 3.3.1.GA Environment: Hibernate EntityManager 3.3.1.GA Hibernate Annotations 3.3.0.GA Hibernate Core 3.2.5 Oracle 9.2.0.7.0 Oracle JDBC driver 10.1.0.4.0 Reporter: ludki Attachments: test.zip The szenrio is very simple : we have two entities EntityA, EntityB with a relation (EntityA.eB <-> EntityB.eA) between them. The foreign key 'eB_id' is located at the table of EntityA. The Lock-Strategy of both Entities is @org.hibernate.annotations.Entity(optimisticLock = org.hibernate.annotations.OptimisticLockType.DIRTY, dynamicUpdate = true) The initial state can be reached as follows: @PersistenceContext EntityManager m; public void create() { EntityA a = new EntityA(1); // PrimaryKey = 1 EntityB b = new EntityB(1); // PrimaryKey = 1 a.eB = b; b.eA = a; m.persist(a); m.persist(b); } in a new Transaction (or after a flush) we have first to release the relation between the two Entities and then remove them. For getting the Exception it is important to remove the Entity which contains the foreign key at last: private void remove() { EntityA a = m.find(EntityA.class, 1); EntityB b = m.find(EntityB.class, 1); m.remove(b); m.remove(a); } A flush before the removes or switching the two removes will prevent the Exception. The generated (and obviously erroneous) SQL-Statements for the remove-method are listed below: update EntityA set eB_id=null where key=1 and eB_id=1 delete from EntityB where key=1 delete from EntityA where key=1 and eB_id = 1 <-- eB_id was set to null two lines ago, therefore the delete causes an EntityNotFoundException org.hibernate.StaleObjectStateException: Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect): [test.EntityA#1] at org.hibernate.persister.entity.AbstractEntityPersister.check(AbstractEntityPersister.java:1765) at org.hibernate.persister.entity.AbstractEntityPersister.delete(AbstractEntityPersister.java:2523) at org.hibernate.persister.entity.AbstractEntityPersister.delete(AbstractEntityPersister.java:2697) at org.hibernate.action.EntityDeleteAction.execute(EntityDeleteAction.java:74) at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:250) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:234) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:146) at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:298) at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27) at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1000) at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:338) at org.hibernate.ejb.AbstractEntityManagerImpl$1.beforeCompletion(AbstractEntityManagerImpl.java:516) at com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.beforeCompletion(SynchronizationImple.java:114) at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.beforeCompletion(TwoPhaseCoordinator.java:247) at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:86) at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:177) at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1389) at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:135) at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:87) at org.jboss.aspects.tx.TxPolicy.endTransaction(TxPolicy.java:175) at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:87) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:95) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77) at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:110) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:304) at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106) at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:769) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:373) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166) javax.persistence.EntityNotFoundException: Unable to find test.EntityA with id 1 at org.hibernate.ejb.Ejb3Configuration$Ejb3EntityNotFoundDelegate.handleEntityNotFound(Ejb3Configuration.java:109) at org.hibernate.impl.SessionImpl.load(SessionImpl.java:797) at org.hibernate.ejb.AbstractEntityManagerImpl.wrapStaleStateException(AbstractEntityManagerImpl.java:640) at org.hibernate.ejb.AbstractEntityManagerImpl.throwPersistenceException(AbstractEntityManagerImpl.java:600) at org.hibernate.ejb.AbstractEntityManagerImpl$1.beforeCompletion(AbstractEntityManagerImpl.java:525) at com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.beforeCompletion(SynchronizationImple.java:114) at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.beforeCompletion(TwoPhaseCoordinator.java:247) at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:86) at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:177) at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1389) at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:135) at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:87) at org.jboss.aspects.tx.TxPolicy.endTransaction(TxPolicy.java:175) at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:87) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:95) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77) at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:110) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:304) at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106) at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:769) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:373) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166) -- 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

17 years, 7 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3057) Lazy many-to-one association defined by referencedColumnName instead of primary key

by Ilhan Nisamedtinov (JIRA)

Lazy many-to-one association defined by referencedColumnName instead of primary key ----------------------------------------------------------------------------------- Key: HHH-3057 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3057 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.5 Environment: Win, Linux, Oracle10g Reporter: Ilhan Nisamedtinov I'm unable to define many-to-one LAZY end with proxy. I have described issue in the forum with following issues: http://forum.hibernate.org/viewtopic.php?t=980613&highlight= >From the following JIRA link I got instuctions about making it work lazy (by NO_PROXY and byte instrumentation): http://opensource.atlassian.com/projects/hibernate/browse/HHH-2766 With NO_PROXY option and byte-code instrumentation I got it to load LAZYly, but I was unable to initialize lazy end through HQL fetch join phrase. From forum I could'nt get instructions to get it to work: http://forum.hibernate.org/viewtopic.php?t=982053&highlight= Why is it impossible to get it to work like LAZY many-to-one ends work () properly defined through primary-key. Is it issue at all or I get smth. really wrong? Thnks, -- 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

17 years, 7 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-104) Make @DocumentId optional and rely on @Id

by Emmanuel Bernard (JIRA)

Make @DocumentId optional and rely on @Id ----------------------------------------- Key: HSEARCH-104 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-104 Project: Hibernate Search Issue Type: New Feature Components: mapping Reporter: Emmanuel Bernard Priority: Minor -- 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

17 years, 7 months

2
6
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 February 2008