March 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HSEARCH-160) Truly polymorphic queries

by Emmanuel Bernard (JIRA)

Truly polymorphic queries ------------------------- Key: HSEARCH-160 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-160 Project: Hibernate Search Issue Type: New Feature Components: engine Reporter: Emmanuel Bernard Fix For: 3.1.0 Support something like ftsession.createFullTextQuery(luceneQuery, java.io.Serializable.class); -- 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, 4 months

2
4
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, 4 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-161) Native support for embedded id

by Emmanuel Bernard (JIRA)

Native support for embedded id ------------------------------ Key: HSEARCH-161 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-161 Project: Hibernate Search Issue Type: New Feature Components: mapping Reporter: Emmanuel Bernard Fix For: 3.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

17 years, 4 months

1
2
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, 5 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, 5 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, 5 months

2
6
0 / 0

[Hibernate-JIRA] Created: (ANN-527) reference a target entity (in a collection) by entity name

by Armin Haaf (JIRA)

reference a target entity (in a collection) by entity name ---------------------------------------------------------- Key: ANN-527 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-527 Project: Hibernate Annotations Type: New Feature Components: binder Reporter: Armin Haaf It is only possible to reference a targetEntity by class. @ManyToMany(targetEntity = TestImpl.class) List<Test> myList; This makes it impossible to exchange TestImpl.class implemention by another implemention by the mappings definition. It would be helpful to reference a targetEntity by name. @ManyToMany(targetEntityName = "Test") This would help a lot to implement moduls and frameworks. Another way to support this would be to search for a implementation of the collection elements (which are typically Interfaces) in the mapped entities -- 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, 5 months

5
10
0 / 0

[Hibernate-JIRA] Created: (HHH-2546) fetch="select" doesn't work when there are no mapped columns in joined except <key

by Derar Bakr (JIRA)

fetch="select" doesn't work when there are no mapped columns in joined except <key ---------------------------------------------------------------------------------- Key: HHH-2546 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2546 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.3 Environment: Windows XP Pro Reporter: Derar Bakr java.lang.StringIndexOutOfBoundsException: String index out of range: -2 at java.lang.String.substring(String.java:1768) at java.lang.String.substring(String.java:1735) at org.hibernate.persister.entity.AbstractEntityPersister.renderSelect(AbstractEntityPersister.java:2899) at org.hibernate.persister.entity.SingleTableEntityPersister.generateSequentialSelect(SingleTableEntityPersister.java:647) at org.hibernate.persister.entity.SingleTableEntityPersister.postInstantiate(SingleTableEntityPersister.java:696) .... Everything is very simple. There is stupid code in SelectFragment class, method toFragmentString, line 94. String that is being created there, contains list of fields, like a "f1, f2, f3, ..., fn". ", " is being added in every iteration, without check for it is first iteration. And in class AbstractEntityPersister., method renderSelect, line 2899, where that method is called, this first ", " is deleted using substring(2). So no check for empty string. I suggest to add check :))) I just create dynamic mappings programmatically, so create empty join subclass mappings - and in created table there are no fields by default except foreing key. -- 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, 5 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HBX-860) cfg.xml generation should have option if it should generate <mappings>

by Max Rydahl Andersen (JIRA)

cfg.xml generation should have option if it should generate <mappings> ---------------------------------------------------------------------- Key: HBX-860 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-860 Project: Hibernate Tools Type: Improvement Reporter: Max Rydahl Andersen Fix For: 3.2beta10 adding <mapping> for class when JPA does not make sense. -- 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, 5 months

2
7
0 / 0

[Hibernate-JIRA] Created: (HBX-888) Option for enable/disable schemaexport and databasemetadata introspection

by Max Rydahl Andersen (JIRA)

Option for enable/disable schemaexport and databasemetadata introspection ------------------------------------------------------------------------- Key: HBX-888 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-888 Project: Hibernate Tools Type: New Feature Components: consoleconfiguration Versions: 3.2beta10 Reporter: Max Rydahl Andersen Fix For: 3.2beta10 schemaexport might be relevant/wanted for some users to automatically run... databasemetadata introspection is probably only relevant for users that does not specify a dialect. -- 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, 5 months

1
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 March 2008