August 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (EJB-287) Upload 3.3.1.GA to the Maven repository

by Aleksei Valikov (JIRA)

Upload 3.3.1.GA to the Maven repository --------------------------------------- Key: EJB-287 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-287 Project: Hibernate Entity Manager Issue Type: Improvement Components: EntityManager Affects Versions: 3.3.1.GA Reporter: Aleksei Valikov Priority: Minor Attachments: hibernate-entitymanager-3.3.1.ga.pom Would you please upload the entity manager as well as dependent artifacts to the Maven repository? This is quite important for Maven builds. Dependent artifacts are: hibernate-commons-annotations (3.0.0.ga) hibernate-validator (3.0.0.ga) jboss-archive-browsing (2.0.2.alpha) Below are the commands I used to deploy these artifacts, I hope this helps. I also attach the POM file for the entity manager. I hope you could reuse it in further versions. Thank you! mvn deploy:deploy-file -DgroupId=org.hibernate -DartifactId=hibernate-entitymanager -Dversion=3.3.1.ga -Dpackaging=jar -Dfile=hibernate-entitymanager-3.3.1.ga.jar -DpomFile=hibernate-entitymanager-3.3.1.ga.pom -Durl=file://C:/Projects/p2.external/maven2-repository/www/repository mvn deploy:deploy-file -DgroupId=org.hibernate -DartifactId=hibernate-commons-annotations -Dversion=3.0.0.ga -Dpackaging=jar -Dfile=hibernate-commons-annotations-3.0.0.ga.jar -Durl=file://C:/Projects/p2.external/maven2-repository/www/repository mvn deploy:deploy-file -DgroupId=org.hibernate -DartifactId=hibernate-validator -Dversion=3.0.0.ga -Dpackaging=jar -Dfile=hibernate-validator-3.0.0.ga.jar -Durl=file://C:/Projects/p2.external/maven2-repository/www/repository mvn deploy:deploy-file -DgroupId=jboss -DartifactId=jboss-archive-browsing -Dversion=2.0.2.alpha -Dpackaging=jar -Dfile=jboss-archive-browsing-2.0.2.alpha.jar -Durl=file://C:/Projects/p2.external/maven2-repository/www/repository -- 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
10
0 / 0

[Hibernate-JIRA] Created: (HHH-3177) SetMaxResults with db2 database problem

by Irena (JIRA)

SetMaxResults with db2 database problem --------------------------------------- Key: HHH-3177 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3177 Project: Hibernate3 Issue Type: Bug Components: core Environment: hibernate3.2.0.ga, DB2 8.2.1 Reporter: Irena Trying to do simple thing: List<Subject> subjects = (List<Subject>) currSession.createQuery("from Subject").setMaxResults(10).list(); this prings fallowing: WARN JDBCExceptionReporter:71 - SQL Error: -104, SQLState: 42601 ERROR JDBCExceptionReporter:72 - DB2 SQL error: SQLCODE: -104, SQLSTATE: 42601, SQLERRMC: 10;select top ;. WARN JDBCExceptionReporter:71 - SQL Error: -727, SQLState: 56098 ERROR JDBCExceptionReporter:72 - DB2 SQL error: SQLCODE: -727, SQLSTATE: 56098, SQLERRMC: 2;-104;42601;10|select top |. WARN JDBCExceptionReporter:71 - SQL Error: -727, SQLState: 56098 ERROR JDBCExceptionReporter:72 - DB2 SQL error: SQLCODE: -727, SQLSTATE: 56098, SQLERRMC: 2;-104;42601;10|select top |. Exception in thread "main" org.hibernate.exception.SQLGrammarException: could not execute query at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:67) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) at org.hibernate.loader.Loader.doList(Loader.java:2147) at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2028) at org.hibernate.loader.Loader.list(Loader.java:2023) at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:393) at org.hibernate.hql.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:338) at org.hibernate.engine.query.HQLQueryPlan.performList(HQLQueryPlan.java:172) at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1121) at org.hibernate.impl.QueryImpl.list(QueryImpl.java:79) at ru.nbch.quality.logic.ReportProcessor.main(ReportProcessor.java:66) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.intellij.rt.execution.application.AppMain.main(AppMain.java:90) Caused by: com.ibm.db2.jcc.b.SqlException: DB2 SQL error: SQLCODE: -104, SQLSTATE: 42601, SQLERRMC: 10;select top ;. at com.ibm.db2.jcc.b.id.e(id.java:1640) at com.ibm.db2.jcc.b.id.a(id.java:1229) at com.ibm.db2.jcc.c.fb.h(fb.java:149) at com.ibm.db2.jcc.c.fb.a(fb.java:43) at com.ibm.db2.jcc.c.s.a(s.java:30) at com.ibm.db2.jcc.c.wb.g(wb.java:152) at com.ibm.db2.jcc.b.id.n(id.java:1209) at com.ibm.db2.jcc.b.jd.eb(jd.java:1779) at com.ibm.db2.jcc.b.jd.a(jd.java:2232) at com.ibm.db2.jcc.b.jd.V(jd.java:505) at com.ibm.db2.jcc.b.jd.executeQuery(jd.java:488) at com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeQuery(NewProxyPreparedStatement.java:76) at org.hibernate.jdbc.AbstractBatcher.getResultSet(AbstractBatcher.java:186) at org.hibernate.loader.Loader.getResultSet(Loader.java:1668) at org.hibernate.loader.Loader.doQuery(Loader.java:662) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:224) at org.hibernate.loader.Loader.doList(Loader.java:2144) ... 13 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

17 years, 7 months

3
2
0 / 0

[Hibernate-JIRA] Created: (EJB-308) Space in path result in error durring deployment

by Max Rydahl Andersen (JIRA)

Space in path result in error durring deployment ------------------------------------------------ Key: EJB-308 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-308 Project: Hibernate Entity Manager Issue Type: Bug Components: EntityManager Affects Versions: 3.2.1 Environment: both linux and windows, JBoss EAP 4.2 or JBoss 4.2 Reporter: Max Rydahl Andersen Assignee: Emmanuel Bernard Priority: Critical 16:38:05,991 ERROR [[/test]] Exception sending context initialized event to listener instance of class org.jboss.seam.servlet.SeamListener javax.persistence.PersistenceException: java.lang.IllegalArgumentException: Unable to visit JAR file:/home/max/rh devstudio/jboss-eap/jboss-as/server/default/deploy/test.war/WEB-INF/classes. Cause: Illegal character in path at index 17: file:/home/max/rh devstudio/jboss-eap/jboss-as/server/default/deploy/test.war/WEB-INF/classes at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:252) at org.hibernate.ejb.HibernatePersistence.createEntityManagerFactory(HibernatePersistence.java:120) at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:51) at org.jboss.seam.core.EntityManagerFactory.startup(EntityManagerFactory.java:74) When testing JBoss EAP 4.2 with RHDS I we created http://jira.jboss.org/jira/browse/JBIDE-691 and this is with Hibernate Annotations 3.2.1 which should have this one fixed according what i could find (i'll link to it) -- 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
6
0 / 0

[Hibernate-JIRA] Created: (EJB-279) Entity Listener defined in orm.xml does not work

by Gary Ip (JIRA)

Entity Listener defined in orm.xml does not work ------------------------------------------------ Key: EJB-279 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-279 Project: Hibernate Entity Manager Type: Bug Components: EntityManager Versions: 3.3.0.ga Environment: Hibernate core 3.2.2.GA, Hibernate Annotations 3.3.0.GA, Hibernate Entity Manager 3.3.0.GA, Spring 2.0.3, Tomcat 5.5.20, Oracle 9i Reporter: Gary Ip A default Entity Listener defined in orm.xml (this EJB3 deployment descriptor) worked in HEM and HAN 3.2.1 but not 3.3.0 http://forums.hibernate.org/viewtopic.php?t=972352&sid=95588b2c2391806158... -- 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: (HHH-3439) Change o.h.cfg.Mappings to not require constructor

by Steve Ebersole (JIRA)

Change o.h.cfg.Mappings to not require constructor -------------------------------------------------- Key: HHH-3439 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3439 Project: Hibernate3 Issue Type: Improvement Components: metamodel Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.4 Mappings requiring passing all the mapping queues into its constructor causes interoperability issues with other components (annotations e.g.) because they generally extend Mappings to add extra information. Therefore we introduce an incompatibility whenever we add a new mapping attribute because we are currently forced to change the signature of the Mappings constructor. A better approach is to make Mappings an interface with an impl that defined as an inner class to o.h.cfg.Configuration so that it can expose access to the queues directly from there. Annotations, etc can than simply extend that Mappings impl. -- 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
5
0 / 0

[Hibernate-JIRA] Created: (EJB-344) API method to return callback methods

by Shane Bryzak (JIRA)

API method to return callback methods ------------------------------------- Key: EJB-344 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-344 Project: Hibernate Entity Manager Issue Type: New Feature Components: EntityManager Reporter: Shane Bryzak We need an easy way to determine the callback methods (pre-create, pre-update, etc) for a given Hibernate bean in Seam. Currently I've hacked together some nasty reflection code based on Emmanuel's advice. Related issue: http://jira.jboss.org/jira/browse/JBSEAM-2029 -- 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
7
0 / 0

[Hibernate-JIRA] Created: (HHH-3394) ScrollableResults delivers sometime wrong collections when used with a LEFT JOIN FETCH clause

by Thomas Scherm (JIRA)

ScrollableResults delivers sometime wrong collections when used with a LEFT JOIN FETCH clause --------------------------------------------------------------------------------------------- Key: HHH-3394 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3394 Project: Hibernate3 Issue Type: Bug Components: query-hql Affects Versions: 3.2.6 Environment: Windows, Java SE 6.06, Oracle 9 / 10, Hibernate 3.2.6 Reporter: Thomas Scherm Following stament is used to create a ScrollableResult from a Query. SELECT DISTINCT f FROM Fall f LEFT JOIN FETCH f.leistungen l WHERE (f.status = '2' OR f.status = '3') AND f.quartalJahr = ? It schould deliver a Faelle with prefeched sets of Leistungen. The first row is ok. All subsequent rows return exactly one leistungen. Th SQL Statement is ok, the session cache works fine and has the missing Leistungen, but they are not attached. As Workaround we removed the FETC clause and let it work with lazy loading. It works. -- 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: (HBX-1063) Any mapping not working for Eclipse Hibernate Plugin

by Marcus Ilgner (JIRA)

Any mapping not working for Eclipse Hibernate Plugin ---------------------------------------------------- Key: HBX-1063 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1063 Project: Hibernate Tools Issue Type: Bug Components: eclipse Affects Versions: 3.2.2 Reporter: Marcus Ilgner My project uses JPA with Hibernate and I have created a Hibernate Console configuration accordingly. One of my entity classes uses the @Any annotation on one of its properties. If I try to open the SessionFactory, I receive the message: org.hibernate.MappingException: property mapping has wrong number of columns However, the object works fine in the software/unit tests. -- 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
5
0 / 0

[Hibernate-JIRA] Created: (HSHARDS-51) ShardResolutionStrategyImpl needs equals() and hashCode()

by Max Ross (JIRA)

ShardResolutionStrategyImpl needs equals() and hashCode() --------------------------------------------------------- Key: HSHARDS-51 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSHARDS-51 Project: Hibernate Shards Issue Type: Bug Components: engine Reporter: Max Ross Assignee: Max Ross Priority: Minor Fix For: 3.0.0 There's basically no way to implement a cache-aware ShardResolutionStrategy until we implement equals() and hashCode() on ShardResolutionStrategyImpl. -- 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
7
0 / 0

[Hibernate-JIRA] Created: (HHH-3216) Incorrect parse result in ParameterParser

by alexandia (JIRA)

Incorrect parse result in ParameterParser ----------------------------------------- Key: HHH-3216 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3216 Project: Hibernate3 Issue Type: Bug Components: query-hql Affects Versions: 3.2.6 Environment: Hibernate 3.1.0, 3.2.6 Any type of database Reporter: alexandia A very simple hql will cause the ParameterMetadata.getOrdinalParameterDescriptor() method throw this Exception: "Remember that ordinal parameters are 1-based!" HQL: from User u where u.userName = ? and u.userType = 'call' The reason is found out to be this: ParameterParser.java public static void parse(String sqlString, Recognizer recognizer) throws QueryException { boolean hasMainOutputParameter = sqlString.indexOf( "call" ) > 0 && sqlString.indexOf( "?" ) < sqlString.indexOf( "call" ) && sqlString.indexOf( "=" ) < sqlString.indexOf( "call" ); The hql above match these conditions, so the hasMainOutputParameter is set to true. Thus the first normal ordinal parameter is bypassed, exception is thrown. Suggestion: Strenthen the checking of the hasMainOutputParameter. -- 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
3
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 August 2008