June 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-5229) org.hibernate.test.hql.ScrollableCollectionFetchingTest.testScrollingJoinFetchesEmptyResultSet() fails on sybase

by Strong Liu (JIRA)

org.hibernate.test.hql.ScrollableCollectionFetchingTest.testScrollingJoinFetchesEmptyResultSet() fails on sybase ---------------------------------------------------------------------------------------------------------------- Key: HHH-5229 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5229 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.2, 3.5.1 Reporter: Strong Liu Assignee: Strong Liu Fix For: 3.5.x, 3.6 {quote} Result set is IDLE as you are not currently accessing a row. Description: The application has called one of the ResultSet.getXXX column-data retrieval methods, but there is no current row; the application has not called ResultSet.next(), or ResultSet.next() returned "false" to indicate that there is no data. Action: Check that rs.next() is set to "true" before calling rs.getXXX. {quote} org.hibernate.exception.GenericJDBCException: could not perform sequential read of results (forward) at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:126) at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:114) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66) at org.hibernate.loader.Loader.loadSequentialRowsForward(Loader.java:420) at org.hibernate.impl.FetchingScrollableResultsImpl.next(FetchingScrollableResultsImpl.java:83) at org.hibernate.test.hql.ScrollableCollectionFetchingTest.testScrollingJoinFetchesEmptyResultSet(ScrollableCollectionFetchingTest.java:67) Caused by: java.sql.SQLException: JZ0R1: Result set is IDLE as you are not currently accessing a row. at com.sybase.jdbc3.jdbc.ErrorMessage.raiseError(Unknown Source) at com.sybase.jdbc3.jdbc.SybResultSet.checkIfReadableRow(Unknown Source) at com.sybase.jdbc3.jdbc.SybResultSet.getColumn(Unknown Source) at com.sybase.jdbc3.jdbc.SybResultSet.getLong(Unknown Source) at com.sybase.jdbc3.jdbc.SybResultSet.getLong(Unknown Source) at org.hibernate.type.LongType.get(LongType.java:51) at org.hibernate.type.NullableType.nullSafeGet(NullableType.java:184) at org.hibernate.type.NullableType.nullSafeGet(NullableType.java:173) at org.hibernate.loader.Loader.getKeyFromResultSet(Loader.java:1120) at org.hibernate.loader.Loader.loadSequentialRowsForward(Loader.java:409) ... 31 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

15 years, 9 months

2
7
0 / 0

[Hibernate-JIRA] Created: (HHH-3624) DialectFactory needs DB2/NT64 adding to the MAPPERS Map

by mike wray (JIRA)

DialectFactory needs DB2/NT64 adding to the MAPPERS Map ------------------------------------------------------- Key: HHH-3624 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3624 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.3.1 Reporter: mike wray Priority: Minor DialectFactory needs DB2/NT64 adding to the MAPPERS Map. ie MAPPERS.put( "DB2/NT64", new VersionInsensitiveMapper( "org.hibernate.dialect.DB2Dialect" ) ); -- 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

15 years, 9 months

5
6
0 / 0

[Hibernate-JIRA] Created: (HV-341) Reduce the amounf of Annotation.annotationType() calls since reflection calls are expensive

by Hardy Ferentschik (JIRA)

Reduce the amounf of Annotation.annotationType() calls since reflection calls are expensive ------------------------------------------------------------------------------------------- Key: HV-341 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-341 Project: Hibernate Validator Issue Type: Improvement Components: engine Affects Versions: 4.1.0.CR1 Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 4.1.0.Final -- 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

15 years, 9 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-5329) NoClassDefFoundError when using Hibernate 3.5 with J2SE 1.4 because of a wrong catch block

by Francesco Poli (JIRA)

NoClassDefFoundError when using Hibernate 3.5 with J2SE 1.4 because of a wrong catch block ------------------------------------------------------------------------------------------ Key: HHH-5329 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5329 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.3, 3.5.2, 3.5.1, 3.5.0-Final Environment: Hibernate 3.5, Java SE 1.4 or J2EE 1.3 Reporter: Francesco Poli Priority: Blocker In org.hibernate.impl.SessionFactoryImpl is done this check when looking for concurrent classes during the creation of the SessionFactory: Statistics concurrentStatistics = null; try { Class concurrentStatsClass = ReflectHelper.classForName("org.hibernate.stat.ConcurrentStatisticsImpl"); Constructor constructor = concurrentStatsClass.getConstructor(new Class[]{SessionFactoryImplementor.class}); concurrentStatistics = (Statistics) constructor.newInstance(new Object[]{this}); log.trace("JDK 1.5 concurrent classes present"); } catch (Exception noJava5) { log.trace("JDK 1.5 concurrent classes missing"); } But what is thrown is a NoClassDefFoundError, which is not an Exception. As a consequence, the catch block won't work and the error is propagated to the upper levels of the application. I suggest to modify the catch arguments to match the correct type of the thrown object. Thank you. Bye Francesco Poli -- 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

15 years, 9 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HV-340) When checking for composing constraints ignore annotations like @Target, @Documented, ...

by Hardy Ferentschik (JIRA)

When checking for composing constraints ignore annotations like @Target, @Documented, ... ----------------------------------------------------------------------------------------- Key: HV-340 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-340 Project: Hibernate Validator Issue Type: Improvement Components: engine Affects Versions: 4.1.0.CR1 Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 4.1.0.Final See {{ConstraintDescriptorImpl}} -- 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

15 years, 9 months

1
1
0 / 0

[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

15 years, 9 months

1
3
0 / 0

[Hibernate-JIRA] Created: (HV-339) ^ not allowed in Email

by Tim (JIRA)

^ not allowed in Email ---------------------- Key: HV-339 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-339 Project: Hibernate Validator Issue Type: Bug Components: validators Affects Versions: 4.1.0.CR1 Environment: hibernate-validator-4.1.0.CR1 Reporter: Tim Assignee: Hardy Ferentschik Priority: Minor The email validator rejects emails with ^ in them. According to the rfc-2822 spec they should be allowed. http://www.faqs.org/rfcs/rfc2822.html I believe the regex is incorrect. >From file org.hibernate.validator.constraints.impl.EmailValidator (line 17) private static String ATOM = "[^\\x00-\\x1F^\\(^\\)^\\<^\\>^\\@^\\,^\\;^\\:^\\\\^\\\"^\\.^\\[^\\]^\\s]"; There should only be one ^ all the others are not needed and cause the ^ character to be invalid. I believe it should be: private static String ATOM = "[^\\x00-\\x1F\\(\\)\\<\\>\\@\\,\\;\\:\\\\\\\"\\.\\[\\]\\s]"; // ======== Test Case ========= import junit.framework.TestCase; import org.hibernate.validator.constraints.impl.EmailValidator; import org.junit.Test; public class TestEmailValidator extends TestCase { @Test public void testAccent(){ EmailValidator emailValidator = new EmailValidator(); boolean result = emailValidator.isValid("Test^Email(a)example.com", null); assertTrue(result); } } -- 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

15 years, 9 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-542) Search results not sorted properly

by Florin Haizea (JIRA)

Search results not sorted properly ---------------------------------- Key: HSEARCH-542 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-542 Project: Hibernate Search Issue Type: Bug Affects Versions: 3.2.0.Final Environment: Hibernate 3.5.1-Final, MySQL 5.1.6 Reporter: Florin Haizea Priority: Critical Attachments: ScoreIssue.zip Trying to index a simple relationship between a Person and a collection of Names. There are 2 issues: 1) The document containing the Person fields contains each name of that person TWICE. I think this may be affecting the score that the document receives. 2) The search results are not ordered correctly. If I have one person with only one name: "Sly Stallone" and other people with multiple names, out of which one contains only "Sly" or only "Stallone", the people with multiple names have a higher score than the person with only one name that matches the search perfectly. Here's the original thread that started this issue: https://forum.hibernate.org/viewtopic.php?f=9&t=1005019&sid=6f1870a4b18a0... I've attached a maven project which contains a test that fails. -- 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

15 years, 9 months

1
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5304) Deploying Hibernate 3.5 in isolated classloader in AS 5.1 fails

by Galder Zamarreno (JIRA)

Deploying Hibernate 3.5 in isolated classloader in AS 5.1 fails --------------------------------------------------------------- Key: HHH-5304 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5304 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.5.2 Reporter: Galder Zamarreno Deploying Hibernate 3.5 within an isolated deployment in AS 5.1, where Hibernate 3.3 or 3.4 runs, fails with: 3:29:34,255 INFO [PersistenceUnitDeployment] Starting persistence unit persistence.unit:unitName=InfiniSeam-ear.ear/InfiniSeam-ejb.jar#InfiniSeam 13:29:34,305 ERROR [AbstractKernelController] Error installing to Start: name=persistence.unit:unitName=InfiniSeam-ear.ear/InfiniSeam-ejb.jar#InfiniSeam state=Create java.lang.ClassCastException: org.hibernate.ejb.HibernatePersistence cannot be cast to javax.persistence.spi.PersistenceProvider Taking in account that org.hibernate.ejb.HibernatePersistence extends javax.persistence.spi.PersistenceProvider, this would appear to be an issue of the first class being loaded with a CL and the second one with a different one. Since org.hibernate.ejb.HibernatePersistence is something that's defined in the persistence.xml, there might be a change that this class is loaded from the wrong place rather than the .ear file (This is just a hunch though): <provider>org.hibernate.ejb.HibernatePersistence</provider> -- 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

15 years, 10 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-5330) Informix requires colon between catalog and table name

by Ranieri J D Severiano (JIRA)

Informix requires colon between catalog and table name ------------------------------------------------------ Key: HHH-5330 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5330 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1 Environment: Hibernate 3.3.1.GA, IBM Informix Dynamic Server Version 10.00.UC5 Reporter: Ranieri J D Severiano I have two databases in an Informix server: * payment * security Payment database has the following tables: + employee + income Security database has the following tables: + user + role If I connect to the payment database, I can select security database with the syntax below: select * from security:user where username='john.connor' But hibernate cannot generate such statement. I find the method org.hibernate.mapping.Table.qualify(String catalog, String schema, String table) which necessarily append dot (".") between catalog/schema and table name. I suggest delegate such concatenation to the 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

15 years, 10 months

2
1
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 June 2010