March 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (ANN-713) Use an ant task to deploy the maven artifacts

by Emmanuel Bernard (JIRA)

Use an ant task to deploy the maven artifacts --------------------------------------------- Key: ANN-713 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-713 Project: Hibernate Annotations Issue Type: New Feature Reporter: Emmanuel Bernard This is what we use in Seam* (I assume you are using Maven Ant Tasks to generate your deployment): <jar jarfile="${src.jar}" basedir="${src.dir}"> <include name="**/*.java" /> <exclude name="**/test/*.java" /> <patternset refid="meta.files" /> </jar> <artifact:remoteRepository id="offline.repository.jboss.org" url="file:///${offline.repository.jboss.org}" /> <artifact:deploy file="${bin.jar}"> <pom file="${pom.file} /> <remoteRepository refId="offine.repository.jboss.org" /> <attach file="${src.jar}" classifier="sources" /> </artifact:deploy> You can then commit the results to svn * Well, actually, it's all wrapped up in macrodef's, but this is them expanded out -- 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

18 years, 1 month

1
2
0 / 0

[Hibernate-JIRA] Created: (HBX-940) Allow select all in the HQL Query Editor

by Peter Mularien (JIRA)

Allow select all in the HQL Query Editor ---------------------------------------- Key: HBX-940 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-940 Project: Hibernate Tools Issue Type: Improvement Components: eclipse Affects Versions: 3.2beta9 Environment: HHH 3.2, Oracle 10, Eclipse 3.2.2 Reporter: Peter Mularien Priority: Minor It would be wonderful if the Eclipse plugin could support Select All (Ctrl-A) in the HQL editor. I often use the HQL editor for prototyping queries, and then select all - paste into my Java class. Thanks for the consideration. -- 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

18 years, 1 month

3
2
0 / 0

[Hibernate-JIRA] Created: (EJB-278) Missing sequence or table on Oracle

by André Fernandes (JIRA)

Missing sequence or table on Oracle ----------------------------------- Key: EJB-278 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-278 Project: Hibernate Entity Manager Type: Patch Components: EntityManager Environment: JBoss 4.0.5.GA, Using JBoss SEAM and Oracle 9i, EJB/JPA annotations Reporter: André Fernandes Here we use a user "project_web" to access a "dbproject" schema. The problem is, when Hibernate looks for the sequences, it looks in the user_sequences, but my user (project_web) don't have any sequences. The solving is: when getting the sequence names (org.hibernate.dialect.Oracle9Dialect .getQuerySequencesString) use that: select SEQUENCE_NAME from all_sequences where SEQUENCE_OWNER='DBPROJECT' i.e. use the schema to look in the all_sequences. Sorry for the bad english. package org.hibernate.dialect; public class Oracle9Dialect extends Dialect { public String getQuerySequencesString() { return "select sequence_name from user_sequences"; } @GeneratedValue(generator="sqCoSeqProjeto", strategy=GenerationType.SEQUENCE) @SequenceGenerator(name="sqCoSeqProjeto", sequenceName="sq_coseqprojeto", allocationSize=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

18 years, 1 month

5
9
0 / 0

[Hibernate-JIRA] Created: (HHH-2953) Mapping DTD does not allow an idbag element inside a component element

by Adolfo Correia (JIRA)

Mapping DTD does not allow an idbag element inside a component element ---------------------------------------------------------------------- Key: HHH-2953 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2953 Project: Hibernate3 Issue Type: Bug Reporter: Adolfo Correia Priority: Minor The mapping DTD file (hibernate-mapping-3.0.dtd) currently forbids an idbag element inside a component element. I have changed the DTD file to allow idbags inside components and the mappings I made seem to work fine with Hibernate. This problem was already reported in the NHibernate Jira (http://jira.nhibernate.org/browse/NH-1044). -- 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

18 years, 1 month

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2382) DefaultLoadEventListener#onLoad throws exception when DelayedPostInsertIdentifier is set as an entity id

by Eelco Hillenius (JIRA)

DefaultLoadEventListener#onLoad throws exception when DelayedPostInsertIdentifier is set as an entity id -------------------------------------------------------------------------------------------------------- Key: HHH-2382 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2382 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.1, 3.2.2, 3.2.0.ga Reporter: Eelco Hillenius DefaultLoadEventListener#onLoad has this code: if ( idClass != null && ! idClass.isInstance( event.getEntityId() ) ) { throw new TypeMismatchException( "Provided id of the wrong type. Expected: " + idClass + ", got " + event.getEntityId().getClass()); } However, EntityIdentityInsertAction has this in it's constructor: delayedEntityKey = isDelayed ? generateDelayedEntityKey() : null; and method: private synchronized EntityKey generateDelayedEntityKey() { if ( !isDelayed ) { throw new AssertionFailure( "cannot request delayed entity-key for non-delayed post-insert-id generation" ); } return new EntityKey( new DelayedPostInsertIdentifier(), getPersister(), getSession().getEntityMode() ); } In case an insert is tried outside of an existing transaction users may run into this problem (like I did). I don't know what the best fix is. The easiest fix would be: Index: /Users/eelcohillenius/Documents/workspace/hibernate3/src/org/hibernate/event/def/DefaultLoadEventListener.java =================================================================== --- /Users/eelcohillenius/Documents/workspace/hibernate3/src/org/hibernate/event/def/DefaultLoadEventListener.java (revision 11098) +++ /Users/eelcohillenius/Documents/workspace/hibernate3/src/org/hibernate/event/def/DefaultLoadEventListener.java (working copy) @@ -5,6 +5,7 @@ import org.apache.commons.logging.Log; import org.apache.commons.logging.LogFactory; +import org.hibernate.EntityMode; import org.hibernate.HibernateException; import org.hibernate.LockMode; import org.hibernate.NonUniqueObjectException; @@ -10,7 +11,7 @@ import org.hibernate.NonUniqueObjectException; import org.hibernate.PersistentObjectException; import org.hibernate.TypeMismatchException; -import org.hibernate.EntityMode; +import org.hibernate.action.DelayedPostInsertIdentifier; import org.hibernate.cache.CacheConcurrencyStrategy; import org.hibernate.cache.CacheKey; import org.hibernate.cache.entry.CacheEntry; @@ -82,7 +83,7 @@ } else { Class idClass = persister.getIdentifierType().getReturnedClass(); - if ( idClass != null && ! idClass.isInstance( event.getEntityId() ) ) { + if ( idClass != null && ! (idClass.isInstance( event.getEntityId() ) || event.getEntityId() instanceof DelayedPostInsertIdentifier )) { throw new TypeMismatchException( "Provided id of the wrong type. Expected: " + idClass + ", got " + event.getEntityId().getClass() ); but that would look like a quick hack to me. -- 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

18 years, 1 month

2
3
0 / 0

[Hibernate-JIRA] Created: (EJB-270) Support eclipse bundleresource protocol

by Emmanuel Bernard (JIRA)

Support eclipse bundleresource protocol --------------------------------------- Key: EJB-270 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-270 Project: Hibernate Entity Manager Type: New Feature Components: EntityManager Reporter: Emmanuel Bernard Assigned to: Emmanuel Bernard As soon as someone provides me a simple eclipse project reproducing EJB-242, I am going a have a look at this bug to properly support bundleresource. I would appreciate the users to put pressure on Eclispe to fix their bug, their URL should be readable as stream and not raise NPEs -- 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

18 years, 1 month

3
8
0 / 0

[Hibernate-JIRA] Created: (ANN-676) Composite PK/FK and the alphabetical order of class names

by Immo Heikkinen (JIRA)

Composite PK/FK and the alphabetical order of class names --------------------------------------------------------- Key: ANN-676 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-676 Project: Hibernate Annotations Issue Type: Bug Components: binder Affects Versions: 3.3.0.ga Environment: Hibernate Core 3.2.5.GA , Hibernate Annotations 3.3.0.GA, Sybase ASE 15 Reporter: Immo Heikkinen Priority: Blocker Attachments: TestCaseFailure.zip, TestCaseOK.zip Original discussion on the user forum: http://forum.hibernate.org/viewtopic.php?t=980623 I am having trouble with composite primary/foreign keys and sequence of classes with bidirectional one-to-many relationship between them. I am getting strange annotation exception with annotations that seem to be perfectly ok. My conclusion is that the name of classes need to be in alphabetical order, otherwise misleading exception about the number of columns is thrown. Attachment TestCaseOK.zip contains sequence of three entity classes A, B and C, with bi-directional one-to-many association between them. This mapping works fine. Attachment TestCaseFailure.zip contains the same classes, but B and C has been changed with each other (B has been renamed to C, and C has been renamed to B.) This mapping causes the following AnnotationException: Caused by: org.hibernate.AnnotationException: A Foreign key refering C from B has the wrong number of column. should be 1 The reason for this seems to be the alphabetical order of the class names! Sequence A --> B --> C is fine but A --> C --> B is not. If you use @Table to define the database table names, it is the table names that need to be in alphabetical order. The same error can be also produced with @SecondaryTable in class/table that has composite PK. This case is more difficult since you cannot get rid of the exception, no matter how you name your classes or tables. I believe this is the same bug that appears in the comments of ANN-509 . -- 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

18 years, 1 month

4
8
0 / 0

[Hibernate-JIRA] Created: (ANN-694) Circularity check error caused by naming conflicts of tables or/and keys

by M. Lhotellerie (JIRA)

Circularity check error caused by naming conflicts of tables or/and keys ------------------------------------------------------------------------ Key: ANN-694 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-694 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.3.1.beta1 Environment: core 3.2, annotations 3.3.0.GA, entitymanager 3.3.1.GA AS400/DB2 Reporter: M. Lhotellerie Attachments: CircularityTest.zip As discussed here http://forum.hibernate.org/viewtopic.php?t=983543, a circularity check error probably caused by naming conflicts (Tables or/and keys). These examples work for tables "Acces", "Droitacces" or "Benefserv" - rename forgein key "idpkdracc" to something which doesn't begin by "idpk" - rename primary key "idpk" to something different of "i", "id", "idp" and "idpk" Also you can rename "Droitacces" to "B", but renaming others class/tables don't seem don't work @Entity public class Acces { @Id private BigInteger idpk; @ManyToOne private Droitacces idpkdracc; } //------------------------------------------------------------------ @Entity public class Droitacces { @Id private BigInteger idpk; @ManyToOne private Benefserv idpkbenef; } //------------------------------------------------------------------ @Entity public class Benefserv { @Id private BigInteger idpk; @ManyToOne private Service idpkser; } //------------------------------------------------------------------ @Entity public class Service { @Id private BigInteger idpk; } //------------------------------------------------------------------ javax.persistence.PersistenceException: org.hibernate.AnnotationException: Foreign key circularity dependency involving the following tables: Droitacces, Benefserv, Acces at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:258) at org.hibernate.ejb.HibernatePersistence.createEntityManagerFactory(HibernatePersistence.java:120) at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:51) at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:33) at test.DoTest.initTest(DoTest.java:12) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMethodRunner.java:99) at org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodRunner.java:81) at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34) at org.junit.internal.runners.TestMethodRunner.runMethod(TestMethodRunner.java:75) at org.junit.internal.runners.TestMethodRunner.run(TestMethodRunner.java:45) at org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod(TestClassMethodsRunner.java:66) at org.junit.internal.runners.TestClassMethodsRunner.run(TestClassMethodsRunner.java:35) at org.junit.internal.runners.TestClassRunner$1.runUnprotected(TestClassRunner.java:42) at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34) at org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:38) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) Caused by: org.hibernate.AnnotationException: Foreign key circularity dependency involving the following tables: Droitacces, Benefserv, Acces at org.hibernate.cfg.AnnotationConfiguration.processFkSecondPassInOrder(AnnotationConfiguration.java:458) at org.hibernate.cfg.AnnotationConfiguration.secondPassCompile(AnnotationConfiguration.java:295) at org.hibernate.cfg.Configuration.buildMappings(Configuration.java:1115) at org.hibernate.ejb.Ejb3Configuration.buildMappings(Ejb3Configuration.java:1269) at org.hibernate.ejb.EventListenerConfigurator.configure(EventListenerConfigurator.java:150) at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:888) at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:186) at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:246) ... 24 more -- 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

18 years, 1 month

5
6
0 / 0

[Hibernate-JIRA] Created: (HHH-2683) "datediff" is declared as NoArgSQLFunction in H2Dialect, but actually accepts 3 arguments.

by Dmitry Katsubo (JIRA)

"datediff" is declared as NoArgSQLFunction in H2Dialect, but actually accepts 3 arguments. ------------------------------------------------------------------------------------------ Key: HHH-2683 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2683 Project: Hibernate3 Issue Type: Bug Components: query-hql Affects Versions: 3.2.4.sp1 Reporter: Dmitry Katsubo The following line in org.hibernate.dialect.H2Dialect registerFunction("datediff", new NoArgSQLFunction("datediff", Hibernate.INTEGER)); should be read as: registerFunction("datediff", new StandardSQLFunction("datediff", Hibernate.INTEGER)); -- 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

18 years, 1 month

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3170) PersistentClass classname is not revealed in MappingException

by Paul Benedict (JIRA)

PersistentClass classname is not revealed in MappingException ------------------------------------------------------------- Key: HHH-3170 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3170 Project: Hibernate3 Issue Type: Improvement Affects Versions: 3.2.x, 3.3 Reporter: Paul Benedict A typical exception from bad configuration is: Caused by: org.hibernate.MappingException: Could not determine type for: java.util.Map, for columns: [org.hibernate.mapping.Column(name)] Recommendation: The "org.hibernate.cfg.Configuration" class should catch the exception and add the name of the offending PersistentClass. The class is held by the iterator. Line 1100 improvement: private void validate() throws MappingException { Iterator iter = classes.values().iterator(); while ( iter.hasNext() ) { PersistentClass pc = (PersistentClass) iter.next(); try { pc.validate( mapping ); } catch(MappingException e) { throw new MappingException(pc.getClassName(), e); } .... } Otherwise, I find it incredibly difficult to find the offending class without a step debugger. -- 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

18 years, 1 month

2
2
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