April 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-2153) Not possible to overwrite System property defaults with hibernate.properties (e.g. use cglib bytecode provider in jboss)

by Armin Haaf (JIRA)

Not possible to overwrite System property defaults with hibernate.properties (e.g. use cglib bytecode provider in jboss) ------------------------------------------------------------------------------------------------------------------------ Key: HHH-2153 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2153 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.ga Environment: JBoss 4.0.4GA, hibernate 3.2.0.ga Reporter: Armin Haaf It is not possible to set the bytecode provider by hibernate.properties, because jboss ejb3.deployer sets it in System.properties. System.properties is added to the GLOBAL_PROPERTIES in Environment.class after hibernate.properties and overwrites the values in hibernate.properties. A solution would be to change the order of adding the properties to GLOBAL_PROPERTIES. First add System.properties, then add hibernate.properties, to be able to overwrite as needed -- 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, 8 months

5
10
0 / 0

[Hibernate-JIRA] Created: (HHH-2021) org.hibernate.cache.QueryKey has a fragile equals() method

by Kenny MacLeod (JIRA)

org.hibernate.cache.QueryKey has a fragile equals() method ---------------------------------------------------------- Key: HHH-2021 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2021 Project: Hibernate3 Type: Bug Components: core Versions: 3.1.3 Reporter: Kenny MacLeod Priority: Trivial This one is no great shakes, but the first line of QueryKey.equals() casts the argument to QueryKey without checking for its type. As such, the method is fragile. It should be consistent with CacheKey, which does an instanceof check before the cast. -- 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, 8 months

7
15
0 / 0

[Hibernate-JIRA] Created: (HHH-2442) ClassCastException loading from second level cache

by Marcio Moraes (JIRA)

ClassCastException loading from second level cache -------------------------------------------------- Key: HHH-2442 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2442 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.1, 3.2.2, 3.2.0.ga Environment: Linux 2.6.15-27-686 #1 SMP PREEMPT Fri Dec 8 18:00:07 UTC 2006 i686 GNU/Linux Reporter: Marcio Moraes Priority: Blocker I'm getting a error when using hibernate 3.2.2.ga with cache (JBoss-Cache) cluster. When hibernate get a entity from second level cache it confuses the arrays of values against array of types. So in some situations i got ClassCastException ... Looking up CacheEntry code at assemble method i saw: private static Object[] assemble( final Serializable[] values, final Object result, final Serializable id, final EntityPersister persister, final Interceptor interceptor, final EventSource session) throws HibernateException { //assembled state gets put in a new array (we read from cache by value!) Object[] assembledProps = TypeFactory.assemble( values, persister.getPropertyTypes(), session, result ); The issue is values (Serializeble[]) is in wrong order compared with persister.getPropertyTypes() (Type[]). If only one cache instance is running it doesnt occurs ... I am using Linux. Att, Márcio Moraes -- 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, 8 months

6
12
0 / 0

[Hibernate-JIRA] Created: (HHH-2926) Patch for Pre*Event inherit AbstractEvent

by Chatellier Eric (JIRA)

Patch for Pre*Event inherit AbstractEvent ----------------------------------------- Key: HHH-2926 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2926 Project: Hibernate3 Issue Type: Patch Components: core Affects Versions: 3.2.5 Environment: 3.2.5.ga; all platform Reporter: Chatellier Eric Attachments: patch.patch Pre*Event classes are only classes that don't implements AbstractEvent. Here is the patch that correct that. -- 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, 8 months

4
8
0 / 0

[Hibernate-JIRA] Created: (HHH-3247) Provide more information in TypeMismatchException message

by Szczepan Kuzniarz (JIRA)

Provide more information in TypeMismatchException message --------------------------------------------------------- Key: HHH-3247 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3247 Project: Hibernate3 Issue Type: Improvement Components: core Affects Versions: 3.2.6 Reporter: Szczepan Kuzniarz When DefaultLoadEventListener throws TypeMismatchException it provides information about expected and actual id types: "Provided id of the wrong type. Expected: " + idClass + ", got " + event.getEntityId().getClass() but it says nothing about the offending class. It is not always the class which is loaded by client (it may be one of associated classes) and sometimes it's not easy to track it down. It would be nice if DefaultLoadEventListener would report something like this: "Provided id of the wrong type for class " + persister.getEntityName() + ". Expected: " + idClass + ", got " + event.getEntityId().getClass() -- 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, 8 months

3
6
0 / 0

[Hibernate-JIRA] Created: (HHH-3141) Move to JBoss Cache 2.1.0.GA

by Brian Stansberry (JIRA)

Move to JBoss Cache 2.1.0.GA ---------------------------- Key: HHH-3141 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3141 Project: Hibernate3 Issue Type: Sub-task Components: caching (L2) Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 3.3 The current Hibernate/JBC2 integration is using JBC 2.1.0.CR4. Need to switch to the GA when it comes out. OptimisticBulkOperationsTest has a "failure expected" test that will pass with the GA; need to get rid of the failure expected bit. -- 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, 8 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HBX-974) Unable to recreate tables using Hibernate

by sridhar negi (JIRA)

Unable to recreate tables using Hibernate ------------------------------------------ Key: HBX-974 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-974 Project: Hibernate Tools Issue Type: Task Environment: Oracle 9i. Reporter: sridhar negi i m using SchemaUpdate tool of Hibernate.The problem which i m facing is that i had some tables in the database ,now i needed to delete some of the columns from some of the tables. Since UpdateSchema does not allow to delete columns ,i decided to manually drop the those tables from oracle database and recreate those tables. But i m not able to do the same. It tries to fire alter table command, even when there is no such table present in the database..The error whcih i m getting is some thing like this.. [java] alter table POOL_DETAILS add POOL_WEIGHT DOUBLE PRECISION [java] 52085 DEBUG [main] hbm2ddl.SchemaUpdate - execute alter table POOL_DETAILS add POOL_WEIGHT DOUBLE PRECISION [java] 52147 ERROR [main] hbm2ddl.SchemaUpdate - execute Unsuccessful: alter table POOL_DETAILS add POOL_WEIGHT DOUBLE PRECISION [java] 52147 ERROR [main] hbm2ddl.SchemaUpdate - execute ORA-00942: table or view does not exist -- 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, 8 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HBX-954) Failing detection of Sequences?

by Vincent Latombe (JIRA)

Failing detection of Sequences? ------------------------------- Key: HBX-954 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-954 Project: Hibernate Tools Issue Type: Bug Environment: Hibernate3 as provided by Seam 1.2.1GA (dunno which subversion) Oracle 10g Reporter: Vincent Latombe Here is my problem : I used reverse engineering to get an entity from a table in a database. I got my entity then I wanted to add a generation for the Id. Fine, I add HIBERNATE_SEQUENCE which is needed then I add the annotation to my entity. I get this : @Id @Column(name = "ID", precision = 22, scale = 0) @GeneratedValue(strategy=GenerationType.SEQUENCE) @NotNull public long getId() { return this.id; } Nothing really difficult. Then I try to deploy my ejb using the validate strategy of hbm2ddl. And it fails because it can't find the sequence ([DatabaseMetadata] table not found: TESTSEAM.hibernate_sequence)... Ok strange. Then I switch to the update strategy... Now I get something interesting. 14:40:12,843 INFO [DatabaseMetadata] table not found: TESTSEAM.hibernate_sequence 14:40:12,843 INFO [DatabaseMetadata] table not found: hibernate_sequence 14:40:12,875 ERROR [SchemaUpdate] Unsuccessful: create sequence TESTSEAM.hibernate_sequence 14:40:12,875 ERROR [SchemaUpdate] ORA-00955: ce nom d'objet existe dÚjÓ 14:40:12,875 INFO [SchemaUpdate] schema update complete It seems that DatabaseMetadata try to lookup a table instead of a sequence, so it can't detect the already existing sequence. So then it tries to create the sequence but it already exists. Any clue? -- 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, 8 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2958) Incomplete/non-informative javadocs for events system

by Jacob L E Blain Christen (JIRA)

Incomplete/non-informative javadocs for events system ----------------------------------------------------- Key: HHH-2958 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2958 Project: Hibernate3 Issue Type: Task Components: documentation Affects Versions: 3.2.5, 3.2.4.sp1, 3.2.4, 3.2.3, 3.2.2, 3.2.1, 3.2.0.ga, 3.2.0.cr5, 3.2.0.cr4, 3.2.0.cr3, 3.2.0.cr2, 3.2.0 cr1, 3.1.3, 3.2.0.alpha2, 3.2.0.alpha1, 3.1.2, 3.1.1, 3.1, 3.1 rc3, 3.1 rc2, 3.1 rc 1, 3.1 beta 2, 3.1 beta 1, 3.0.5 Reporter: Jacob L E Blain Christen Priority: Minor See also HHH-1942. As per the documentation at http://www.hibernate.org/hib_docs/v3/api/org/hibernate/event/PreUpdateEve... (as an example) and HHH-1942 I most definately do not consider <pre><code>org.hibernate.event Interface PreUpdateEventListener All Superinterfaces: Serializable All Known Implementing Classes: JACCPreUpdateEventListener public interface PreUpdateEventListener extends Serializable Called before updating the datastore Author: Gavin King Method Summary boolean onPreUpdate(PreUpdateEvent event) Method Detail onPreUpdate public boolean onPreUpdate(PreUpdateEvent event)</code></pre> to be "documented" in any meaningful sense. It would be terrific if the event system javadocs as a whole were on par with the quality of the core hibernate javadocs. -- 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, 8 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2419) Link wiki articles in reference

by Diego Pires Plentz (JIRA)

Link wiki articles in reference ------------------------------- Key: HHH-2419 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2419 Project: Hibernate3 Type: Improvement Reporter: Diego Pires Plentz For example, "Open Session in View" should link to http://hibernate.org/43.html. It helps the users to find relevant information - and google, to index the files ;-) -- 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, 8 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 April 2008