April 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HBX-1119) Hibernate tools tasks(hbm2java) generates info logs as standard error logs (shows red in eclipse) instead of standard out

by vivek meghanathan (JIRA)

Hibernate tools tasks(hbm2java) generates info logs as standard error logs (shows red in eclipse) instead of standard out ------------------------------------------------------------------------------------------------------------------------- Key: HBX-1119 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1119 Project: Hibernate Tools Issue Type: Bug Components: hbm2java Affects Versions: 3.2.0.GA Environment: Hibernate 3.2.0 GA Reporter: vivek meghanathan Hibernate tools tasks(hbm2java) generates info logs as standard error logs (shows red in eclipse) instead of standard out. Please have a look. -- 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, 3 months

1
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3475) Support not-found="ignore" for <any> mappings

by Felix Gnass (JIRA)

Support not-found="ignore" for <any> mappings --------------------------------------------- Key: HHH-3475 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3475 Project: Hibernate Core Issue Type: Improvement Components: core Affects Versions: 3.3.0.SP1 Reporter: Felix Gnass Priority: Minor It would be useful if the <any> element would support the not-found="ignore|exception" setting. Due to the nature of any-mappings it's impossible to use on-delete cascades at the database layer, so it's very likely that ObjectNotFoundExceptions occur. Currently the only work-around to gracefully handle such situations seems to be the implementation of a custom EntityNotFoundDelegate that doesn't throw an exception. -- 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, 3 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-4474) NullPointerException in AuditEventListener#generateBidirectionalCollectionChangeWorkUnits onPostInsert...

by Daniel Bleisteiner (JIRA)

NullPointerException in AuditEventListener#generateBidirectionalCollectionChangeWorkUnits onPostInsert... --------------------------------------------------------------------------------------------------------- Key: HHH-4474 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4474 Project: Hibernate Core Issue Type: Bug Components: envers Environment: <version>1.2.0.GA-hibernate-3.3</version> Reporter: Daniel Bleisteiner Attachments: stacktrace.txt I get the exception attached as file after creating an entity. The mapping works on my development machine... a test server throws that exception. I've tried to search for eny differences in the tables but can't find any so far. The last time a similar error occured I was missing the versioned entry in the version table - these have been filled with the lowest revision available (the same way on my machine as on the test server). So I'm stuck... I have no access to the related source either... maybe this would help! -- 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, 3 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3992) SQLServer "contains" boolean predicate not handled in HQL

by Scott Van Wart (JIRA)

SQLServer "contains" boolean predicate not handled in HQL --------------------------------------------------------- Key: HHH-3992 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3992 Project: Hibernate Core Issue Type: Improvement Components: query-hql Affects Versions: 3.3.2, 3.3.1 Environment: Hibernate core 3.3.1, JDK 1.6, SQLServer 2003 Reporter: Scott Van Wart The following HQL: select pp from Product pp where CONTAINS( pp.keywords, :keywords ) Will throw this exception: org.hibernate.hql.ast.QuerySyntaxException: unexpected AST node: ( near line 1, column 33 [select pp from Product pp where CONTAINS( pp.keywords, :keywords )] at org.hibernate.hql.ast.QuerySyntaxException.convert(QuerySyntaxException.java:54) at org.hibernate.hql.ast.QuerySyntaxException.convert(QuerySyntaxException.java:47) at org.hibernate.hql.ast.ErrorCounter.throwQueryException(ErrorCounter.java:82) at org.hibernate.hql.ast.QueryTranslatorImpl.analyze(QueryTranslatorImpl.java:258) at org.hibernate.hql.ast.QueryTranslatorImpl.doCompile(QueryTranslatorImpl.java:183) at org.hibernate.hql.ast.QueryTranslatorImpl.compile(QueryTranslatorImpl.java:134) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:101) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:80) at org.hibernate.engine.query.QueryPlanCache.getHQLQueryPlan(QueryPlanCache.java:94) at org.hibernate.impl.AbstractSessionImpl.getHQLQueryPlan(AbstractSessionImpl.java:156) at org.hibernate.impl.AbstractSessionImpl.createQuery(AbstractSessionImpl.java:135) at org.hibernate.impl.SessionImpl.createQuery(SessionImpl.java:1650) I tried changing it to this: select pp from Product pp where CONTAINS( pp.keywords, :keywords ) = TRUE But then SQL Server doesn't like it (it produces SQL like "CONTAINS(pkgproduct0_.keywords, ?)=1": org.hibernate.exception.SQLGrammarException: could not execute query using scroll Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Incorrect syntax near '='. -- 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, 3 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3002) database field name 'version' causes ClassCastException while building session factory

by Patrick Burke (JIRA)

database field name 'version' causes ClassCastException while building session factory -------------------------------------------------------------------------------------- Key: HHH-3002 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3002 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.5 Environment: Hibernate 3.2.5, Java 1.6.0_03, MySQL 5.0.41 Reporter: Patrick Burke Attachments: out.hib4 When a database table contains a field named 'version', like his one: DROP TABLE IF EXISTS `tester`.`software_package`; CREATE TABLE `tester`.`software_package` ( `software_id` int(11) NOT NULL auto_increment, `version` varchar(100) default NULL, `name` varchar(100) default NULL, `root_file_id` int(11) default NULL, PRIMARY KEY (`software_id`) ) ENGINE=InnoDB DEFAULT CHARSET=latin1; The following error is thrown: [java] Initial SessionFactory creation failed.java.lang.ClassCastException: org.hibernate.type.StringType cannot be cast to org.hibernate.type.VersionType [java] Exception in thread "main" java.lang.ExceptionInInitializerError [java] at util.HibernateUtil.<clinit>(Unknown Source) [java] at events.EventManager.listNodes(Unknown Source) [java] at events.EventManager.main(Unknown Source) [java] Caused by: java.lang.ClassCastException: org.hibernate.type.StringType cannot be cast to org.hibernate.type.VersionType [java] at org.hibernate.tuple.PropertyFactory.buildVersionProperty(PropertyFactory.java:84) [java] at org.hibernate.tuple.entity.EntityMetamodel.<init>(EntityMetamodel.java:168) [java] at org.hibernate.persister.entity.AbstractEntityPersister.<init>(AbstractEntityPersister.java:434) [java] at org.hibernate.persister.entity.SingleTableEntityPersister.<init>(SingleTableEntityPersister.java:109) [java] at org.hibernate.persister.PersisterFactory.createClassPersister(PersisterFactory.java:55) [java] at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:226) [java] at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1294) [java] ... 3 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

14 years, 3 months

6
7
0 / 0

[Hibernate-JIRA] Created: (HHH-4968) Cannot deactivate default BeanValidationListener independently of DDL constraints generation

by Vladimir Klyushnikov (JIRA)

Cannot deactivate default BeanValidationListener independently of DDL constraints generation -------------------------------------------------------------------------------------------- Key: HHH-4968 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4968 Project: Hibernate Core Issue Type: Bug Components: annotations Affects Versions: 3.5.0-CR-2 Environment: Hibernate 3.5.0-CR-2, Hibernate Validator 4.0.2.GA Reporter: Vladimir Klyushnikov Hi, I need to configure my custom BeanValidationListener instance through Spring, but I cannot deactivate default BeanValidationListener instance. It can be switched off only with DDL constraint generation. When I provide *DDL* value for *javax.persistence.validation.mode* it still activates default BeanValidationListener. When I provide *NONE* value it switches off both BeanValidationListener and DDL constraints. This is because of following code in *BeanValidationListener.java*: {code} public static void activateBeanValidation(EventListeners eventListeners, Properties properties) { ... if ( modes.contains( ValidationMode.NONE ) ) return; ... } {code} It should be changed to following: {code} if (!(modes.contains(ValidationMode.CALLBACK) || modes.contains( ValidationMode.AUTO))) return; {code} -- 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, 3 months

3
12
0 / 0

[Hibernate-JIRA] Created: (HHH-4036) EntityMetamodel entityNameByInheritenceClassNameMap field used inconsistently

by Jeremy Stone (JIRA)

EntityMetamodel entityNameByInheritenceClassNameMap field used inconsistently ----------------------------------------------------------------------------- Key: HHH-4036 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4036 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.2 Reporter: Jeremy Stone After upgrading (from 3.3.0.SP1) to 3.3.2.GA we have started getting the follow stack trace logged: org.hibernate.HibernateException: Unable to resolve entity name from Class [com.cyclone.netPrefect.admin.restriction.complex.TimeSpanRestrictionItemEntity] expected instance/subclass of [RestrictionItem] at org.hibernate.tuple.entity.PojoEntityTuplizer.determineConcreteSubclassEntityName(PojoEntityTuplizer.java:363) at org.hibernate.persister.entity.AbstractEntityPersister.getSubclassEntityPersister(AbstractEntityPersister.java:3643) at org.hibernate.impl.SessionImpl.getEntityPersister(SessionImpl.java:1375) at org.hibernate.engine.ForeignKeys.isTransient(ForeignKeys.java:203) at org.hibernate.event.def.AbstractSaveEventListener.getEntityState(AbstractSaveEventListener.java:535) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.performSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:103) ... etc, etc The com.cyclone.netPrefect.admin.restriction.complex.TimeSpanRestrictionItemEntity is mapped (with entity name TimeSpanRestrictionItem) as a joined subclass of the entity named RestrictionItem. I have had a look at the Hibernate source for 3.3.2.ga and it looks like problem is the way that the org.hibernate.tuple.entity.EntityMetamodel is using it entityNameByInheritenceClassNameMap field: * Puts to the map are based on PersistentClass.getMappedClass() as a key - a Class object * Gets from the map (in findEntityNameByEntityClass method) are using the class name Presumably (given the name of the map field) both put and get should be using the class name. -- 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, 3 months

10
20
0 / 0

[Hibernate-JIRA] Created: (HHH-5098) AssertionFailure thrown when collection contains a parameterized type

by Kahli Burke (JIRA)

AssertionFailure thrown when collection contains a parameterized type --------------------------------------------------------------------- Key: HHH-5098 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5098 Project: Hibernate Core Issue Type: Bug Components: entity-manager Affects Versions: 3.5.0-Final Reporter: Kahli Burke Attachments: patch.txt The following exception is thrown when an entity exists with a collection containing a parameterized type: ERROR [AssertionFailure] an assertion failure occured (this may indicate a bug in Hibernate): org.hibernate.annotations.common.AssertionFailure: Fail to process type argument in a generic declaration. Type: class sun.reflect.generics.reflectiveObjects.ParameterizedTypeImpl at org.hibernate.ejb.metamodel.AttributeFactory$PluralAttributeMetadataImpl.getClassFromGenericArgument(AttributeFactory.java:836) at org.hibernate.ejb.metamodel.AttributeFactory$PluralAttributeMetadataImpl.<init>(AttributeFactory.java:748) at org.hibernate.ejb.metamodel.AttributeFactory$PluralAttributeMetadataImpl.<init>(AttributeFactory.java:723) at org.hibernate.ejb.metamodel.AttributeFactory.determineAttributeMetadata(AttributeFactory.java:518) at org.hibernate.ejb.metamodel.AttributeFactory.buildAttribute(AttributeFactory.java:93) at org.hibernate.ejb.metamodel.MetadataContext.wrapUp(MetadataContext.java:183) at org.hibernate.ejb.metamodel.MetamodelImpl.buildMetamodel(MetamodelImpl.java:66) at org.hibernate.ejb.EntityManagerFactoryImpl.<init>(EntityManagerFactoryImpl.java:83) at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:883) at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:73) at org.jboss.jpa.builder.DefaultCEMFBuilder.build(DefaultCEMFBuilder.java:47) at org.jboss.jpa.deployment.PersistenceUnitDeployment.start(PersistenceUnitDeployment.java:316) For example if a field exists like: @OneToMany List<SomeEntity<SomeClass>> associatedList; I've attached a patch that includes a test case for the entity-manager project and a proposed fix. -- 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, 4 months

5
8
0 / 0

[Hibernate-JIRA] Created: (HHH-5062) In the Session.flush method has a lost of perfomance about 50% when flush a large amout of data

by Fabiano Cury (JIRA)

In the Session.flush method has a lost of perfomance about 50% when flush a large amout of data ----------------------------------------------------------------------------------------------- Key: HHH-5062 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5062 Project: Hibernate Core Issue Type: Improvement Components: core Affects Versions: 3.5.0-Final, 3.5.0-CR-2, 3.5.0-CR-1, 3.5.0-Beta-4, 3.5.0-Beta-3, 3.5.0-Beta-2, 3.5.0.Beta-1, 3.3.2, 3.3.1, 3.3.0.SP1, 3.3.0.GA, 3.3.0.CR2, 3.3.0.CR1, 3.2.7, 3.2.6 Environment: Linux / DB2 / version 3.2.6 and above Reporter: Fabiano Cury Attachments: issueHibernate.JPG When the flush method is called this method call the onFlush method of class DefaultFlushEventListener and then the method flushEverythingToExecutions(event). This method (flushEverythingToExecutions) call many times (loop) the method log.isDebugEnabled(). This cause a big overhead in this method. I suggest you to put an attribute in the method flushEverythingToExecutions(flushEverythingToExecutions(FlushEvent event, Boolean isDebugEnable) and verify this attribute before the loop for. Attached the print screen of profiling that help me to detect this issue. Tks. -- 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, 4 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3045) Duplicated column aliases in scalar query

by Anderson Souza (JIRA)

Duplicated column aliases in scalar query ----------------------------------------- Key: HHH-3045 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3045 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.5 Environment: Hibernate 3.2.4SP1, 3.2.5GA Oracle 10g Reporter: Anderson Souza Priority: Critical Attachments: ddl-tables.sql, dominio.zip The HQL bellow works fine, but when I add a call to a funcion in the select clause the SQL generated has duplicated aliases and it generate error on query execution, because the query is paginated. {code} select a from Area a inner join fetch a.horarioPadrao left outer join fetch a.horarioTemporario as hrtemp {code} The SQL generated for this query is: {code} select * from ( select area0_.cod_local as cod1_15_0_, horarioare1_.cod_area as cod1_6_1_, horarioare2_.cod_area as cod1_7_2_, area0_.des_local as des2_15_0_, area0_.sig_local as sig3_15_0_, area0_.flg_extinto as flg4_15_0_, horarioare1_.hr_hora_ini as hr2_6_1_, horarioare1_.hr_hora_fim as hr3_6_1_, horarioare1_.flg_fim_semana as flg4_6_1_, horarioare2_.hr_hora_ini as hr2_7_2_, horarioare2_.hr_hora_fim as hr3_7_2_, horarioare2_.flg_fim_semana as flg4_7_2_, horarioare2_.dat_ini_vigencia as dat5_7_2_, horarioare2_.dat_fim_vigencia as dat6_7_2_ from esq_fp.tb_local area0_ inner join tb_horario_local_padrao horarioare1_ on area0_.cod_local=horarioare1_.cod_area left outer join tb_horario_local_temporario horarioare2_ on area0_.cod_local=horarioare2_.cod_area where 1=1 order by area0_.sig_local ) where rownum <= ? {code} The scalar HQL query that generate duplicated column names is: {code} select a, count(*) from Area a inner join fetch a.horarioPadrao left outer join fetch a.horarioTemporario as hrtemp {code} The SQL generated is: {code} select * from ( select area0_.cod_local as col_0_0_, count(*) as col_1_0_, horarioare1_.cod_area as cod1_6_1_, horarioare2_.cod_area as cod1_7_2_, area0_.cod_local as cod1_15_0_, horarioare1_.cod_area as cod1_6_1_, horarioare2_.cod_area as cod1_7_2_, area0_.des_local as des2_15_0_, area0_.sig_local as sig3_15_0_, area0_.flg_extinto as flg4_15_0_, horarioare1_.hr_hora_ini as hr2_6_1_, horarioare1_.hr_hora_fim as hr3_6_1_, horarioare1_.flg_fim_semana as flg4_6_1_, horarioare2_.hr_hora_ini as hr2_7_2_, horarioare2_.hr_hora_fim as hr3_7_2_, horarioare2_.flg_fim_semana as flg4_7_2_, horarioare2_.dat_ini_vigencia as dat5_7_2_, horarioare2_.dat_fim_vigencia as dat6_7_2_ from esq_fp.tb_local area0_ inner join tb_horario_local_padrao horarioare1_ on area0_.cod_local=horarioare1_.cod_area left outer join tb_horario_local_temporario horarioare2_ on area0_.cod_local=horarioare2_.cod_area where 1=1 order by area0_.sig_local ) where rownum <= ? {code} As you can see the aliases cod1_6_1_ and cod1_7_2_ are repeated and this repetition breaks the paginated query, beacause the main query appears in the from clause. The HBM's and classes are attached. -- 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, 4 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues April 2010