April 2009 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HV-45) @AssertFalse message interpolation is broken

by Olle Hallin (JIRA)

@AssertFalse message interpolation is broken -------------------------------------------- Key: HV-45 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-45 Project: Hibernate Validator Issue Type: Bug Affects Versions: 3.0.0.ga Reporter: Olle Hallin I have an Address domain object, which shall contain at least one of the fields street, zip, city and so on. A completely empty address is not valid. So I added a validator method that checks the entire object: @AssertFalse(message = "The address is empty") @Transient public boolean isEmpty() { // return true if all fields are null or empty } The InvalidValue generated when validating an empty Address contains "empty The address is empty", where the prefix "empty " is derived from the method name isEmpty(). I had expected the value "The address is empty". -- 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, 6 months

3
2
0 / 0

[Hibernate-JIRA] Created: (EJB-434) SQLException: ORA-02287 while fetching the sequence value

by Jerish Joseph (JIRA)

SQLException: ORA-02287 while fetching the sequence value ---------------------------------------------------------- Key: EJB-434 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-434 Project: Hibernate Entity Manager Issue Type: Bug Components: EntityManager Affects Versions: 3.4.0.GA Environment: 3.4.0.GA, Oracle 10g Reporter: Jerish Joseph We are getting ORA-02287 error while fetching the sequence value from database. The query executed is SELECT APP_SEQ.NEXTVAL FROM DUAL. We reveretd to an old version of hibernate-entitymanager (3.2.1.ga ) to get rid of this issue. The exception thrown with 3.4.0.GA is: Caused by: java.sql.SQLException: ORA-02287: sequence number not allowed here at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:74) at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:131) at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:204) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:455) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:413) at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:1034) at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:194) at oracle.jdbc.driver.T4CPreparedStatement.executeForDescribe(T4CPreparedStatement.java:791) at oracle.jdbc.driver.T4CPreparedStatement.executeMaybeDescribe(T4CPreparedStatement.java:866) at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1186) at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3387) at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3431) at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeQuery(OraclePreparedStatementWrapper.java:1203) at com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.pmiExecuteQuery(WSJdbcPreparedStatement.java:1011) at com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.executeQuery(WSJdbcPreparedStatement.java:661) at org.hibernate.jdbc.AbstractBatcher.getResultSet(AbstractBatcher.java:208) at org.hibernate.loader.Loader.getResultSet(Loader.java:1808) at org.hibernate.loader.Loader.doQuery(Loader.java:697) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:259) at org.hibernate.loader.Loader.doList(Loader.java:2228) ... 196 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, 6 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2401) CLOB truncation on DB2 when using 2 or 3 byte chars (UTF8)

by Simon Jongsma (JIRA)

CLOB truncation on DB2 when using 2 or 3 byte chars (UTF8) ---------------------------------------------------------- Key: HHH-2401 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2401 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.ga Environment: Hibernate 3.2.0 GA + JBoss 4.0.4.GA on Windows XP + DB2 UDB for ISeries V5R3 + IBM JT Open driver 4.9 Reporter: Simon Jongsma Priority: Minor Attachments: ClobTruncated.zip A CLOB column is used in DB2 mapped to a String in Java with the Hibernate "Text" mapping. The column in DB2 has a CCSID 1208 which means "UTF8" (= Unicode). The CLOB truncation occurs when characters are used that are UTF8 coded in more than one byte. In that the string is truncated when persisted in the database. For example the string "Granpré Molière†; 0123456789". This string has three diacritical marks in it. The é and è are coded in two bytes in UTF8 and the † in three bytes. This string will be stored as "Granpré Molière†; 012345". So "6789" is not stored. It appears as though Hibernate does not take into account that a character can be more than 1 byte in UTF8. The number of missing char's at the end is exactly: string.getBytes("UTF-8").length minus string.length() It is not a problem of DB2 or the JT Open driver: Storing and retrieving (from a Java program) the same String directly via Jdbc into the DB2 table and retrieving it, works 100% fine. So this clearly points to a problem somewhere in Hibernate. -- 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, 6 months

3
6
0 / 0

[Hibernate-JIRA] Créée: (HHH-2086) Patch for bug HHH-2076 and to be able to use <formula> in <key> for <one-to-many>

by Xavier Brénuchon (JIRA)

Patch for bug HHH-2076 and to be able to use <formula> in <key> for <one-to-many> --------------------------------------------------------------------------------- Key: HHH-2086 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2086 Project: Hibernate3 Type: Patch Components: core Versions: 3.2.0.cr4 Reporter: Xavier Brénuchon Attachments: formula_one_to_many.patch Hello, There is a patch to correct bug HHH-2076 and make an improvement for HHH-944. In fact, theses 2 cases are linked. They need, amongst other things, a formula in the right part of outer join. This patch is simple but many class concerns (to propagate formula templates). About formula in one-to-many : You must have at least a column (not only formula), because it's not possible to have an Update order without at least a column. If it is the case, hibernate patch will raise an MappingException rightly. This patch add two TestCase : org.hibernate.test.onetoone.bidirectionnalformula. OneToOneBidirectionalFormulaTest org.hibernate.test.onetomany.formula. OneToManyFormulaTest Would it be possible to integrate this patch into Hibernate 3.2 ? -- 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, 6 months

4
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3585) Convert org.hibernate.cache.jbc2 integration to use JBoss Cache 3

by Brian Stansberry (JIRA)

Convert org.hibernate.cache.jbc2 integration to use JBoss Cache 3 ----------------------------------------------------------------- Key: HHH-3585 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3585 Project: Hibernate Core Issue Type: Task Components: caching (L2) Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 3.4 JBoss Cache 3 is the main development branch for JBC. It introduces MVCC locking, which should help the Hibernate 2LC use case. Integration with JBoss Cache 3 and use of MVCC has already been tested against the Hibernate Core 3.3.1.GA tag, on the https://svn.jboss.org/repos/hibernate/core/branches/JBOSS_CACHE_3/ branch. Task here is to port the changes (all in cache-jbosscache2 testsuite) to trunk. -- 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, 6 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-3801) Create a cache-jbosscache-legacy module

by Brian Stansberry (JIRA)

Create a cache-jbosscache-legacy module --------------------------------------- Key: HHH-3801 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3801 Project: Hibernate Core Issue Type: Sub-task Components: caching (L2) Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 3.5 Use this module to hold the 1.x integration so cache-jbosscache can hold the latest and greatest -- 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, 6 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3802) Move the up-to-date JBC integration into cache-jbosscache

by Brian Stansberry (JIRA)

Move the up-to-date JBC integration into cache-jbosscache --------------------------------------------------------- Key: HHH-3802 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3802 Project: Hibernate Core Issue Type: Sub-task Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 3.5 Use the default module for the current integration -- 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, 6 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3803) Repackage JBC integration to org.hibernate.cache.jbc

by Brian Stansberry (JIRA)

Repackage JBC integration to org.hibernate.cache.jbc ---------------------------------------------------- Key: HHH-3803 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3803 Project: Hibernate Core Issue Type: Sub-task Components: caching (L2) Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 3.5 Get rid of the "jbc2" since it's really oriented toward "jbc 2+". Leave the jbc2 package for API classes; have versions that delegate/subclass to equivalents in new jbc package. -- 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, 6 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3813) Automatic flush to the join table before a criteria query

by Maxim Gordienko (JIRA)

Automatic flush to the join table before a criteria query --------------------------------------------------------- Key: HHH-3813 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3813 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1 Environment: Hibernate Core 3.3.1.GA, H2 1.1.108 Reporter: Maxim Gordienko Attachments: criteriaflush.zip With the default flush mode Hibernate flushes query regions before queries to run SQL against actual table data. If two entity are connected using the join table and data is queried using a criteria Hibernate does not flush to the join table. It flushes to the entity tables though. The attached test case produces the SQL output Hibernate: insert into USERS (ID, NAME) values (null, ?) Hibernate: insert into ITEMS (ID, NAME) values (null, ?) Hibernate: select this_.ID as ID0_1_, this_.NAME as NAME0_1_, items3_.USER_ID as USER1_, items1_.ID as ITEM2_, items1_.ID as ID2_0_, items1_.NAME as NAME2_0_ from USERS this_ inner join USER_ITEMS items3_ on this_.ID=items3_.USER_ID inner join ITEMS items1_ on items3_.ITEM_ID=items1_.ID where items1_.NAME=? But it should flush to the USER_ITEMS table before executing the criteria query. The commented HQL query does flush to both the entity tables and the join table. The problem is in the org.hibernate.loader.criteria.CriteriaQueryTranslator.getQuerySpaces() method. It returns only the entity tables. -- 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, 6 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3492) Bug: SingleTableEntityPersister - generateSequentialSelect()

by Michael Kohlhuber (JIRA)

Bug: SingleTableEntityPersister - generateSequentialSelect() ------------------------------------------------------------ Key: HHH-3492 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3492 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.2.5 Environment: hibernate 3.2.5.ga oracle 9i Reporter: Michael Kohlhuber http://forum.hibernate.org/viewtopic.php?t=990850 -- 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, 6 months

2
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues April 2009