August 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (ANN-761) Typo in documentation

by Luis Parravicini (JIRA)

Typo in documentation --------------------- Key: ANN-761 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-761 Project: Hibernate Annotations Issue Type: Bug Components: documentation Reporter: Luis Parravicini Priority: Trivial The first paragraph at http://www.hibernate.org/hib_docs/annotations/reference/en/html_single/#e... says "avility" instead of "ability". -- 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

16 years, 5 months

3
2
0 / 0

[Hibernate-JIRA] Created: (ANN-763) Hibernate fails on startup when using IdClass and one of the id-properties is an embedded object.

by Arne Limburg (JIRA)

Hibernate fails on startup when using IdClass and one of the id-properties is an embedded object. ------------------------------------------------------------------------------------------------- Key: ANN-763 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-763 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.4.0.CR2, 3.4.0.CR1, 3.3.1.GA Environment: Hibernate 3.2.6 with HSQLDB, tested with Hibernate-Annotations 3.3.1.GA and 3.4.0.CR2 Reporter: Arne Limburg To verify this I modified the entities for the CompositeIdTest: I changed the Product class to be embeddable (by annotating it with @Embeddable instead of @Entity and annotating the property with @Basic instead of @Id) and the Reference in the OrderLinePK class from @ManyToOne @JoinColumn to @Embedded. This resulted in the following exception: org.hibernate.PropertyNotFoundException: field [name] not found on org.hibernate.test.annotations.cid.OrderLine at org.hibernate.property.DirectPropertyAccessor.getField(DirectPropertyAccessor.java:122) at org.hibernate.property.DirectPropertyAccessor.getField(DirectPropertyAccessor.java:114) at org.hibernate.property.DirectPropertyAccessor.getGetter(DirectPropertyAccessor.java:137) at org.hibernate.mapping.Property.getGetter(Property.java:272) at org.hibernate.tuple.component.PojoComponentTuplizer.buildGetter(PojoComponentTuplizer.java:133) at org.hibernate.tuple.component.AbstractComponentTuplizer.<init>(AbstractComponentTuplizer.java:43) at org.hibernate.tuple.component.PojoComponentTuplizer.<init>(PojoComponentTuplizer.java:38) at org.hibernate.tuple.component.ComponentEntityModeToTuplizerMapping.<init>(ComponentEntityModeToTuplizerMapping.java:52) at org.hibernate.tuple.component.ComponentMetamodel.<init>(ComponentMetamodel.java:50) at org.hibernate.mapping.Component.buildType(Component.java:152) at org.hibernate.mapping.Component.getType(Component.java:145) at org.hibernate.tuple.PropertyFactory.buildStandardProperty(PropertyFactory.java:120) at org.hibernate.tuple.component.ComponentMetamodel.<init>(ComponentMetamodel.java:45) at org.hibernate.mapping.Component.buildType(Component.java:152) at org.hibernate.mapping.Component.getType(Component.java:145) at org.hibernate.mapping.SimpleValue.isValid(SimpleValue.java:253) at org.hibernate.mapping.Property.isValid(Property.java:185) at org.hibernate.mapping.PersistentClass.validate(PersistentClass.java:440) at org.hibernate.mapping.RootClass.validate(RootClass.java:192) at org.hibernate.cfg.Configuration.validate(Configuration.java:1108) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1293) at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:915) at org.hibernate.test.annotations.TestCase.buildSessionFactory(TestCase.java:51) at org.hibernate.test.annotations.TestCase.setUp(TestCase.java:61) at junit.framework.TestCase.runBare(TestCase.java:125) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:118) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:128) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) -- 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

16 years, 5 months

2
3
0 / 0

[Hibernate-JIRA] Resolved: (HV-15) @Past validation annotation generates incorrect DDL for Oracle 8.x

by Emmanuel Bernard (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HV-15?page=com.... ] Emmanuel Bernard resolved HV-15. -------------------------------- Resolution: Duplicate Fix Version/s: 3.1.0.CR2 Dupe of HV-65 > @Past validation annotation generates incorrect DDL for Oracle 8.x > ------------------------------------------------------------------ > > Key: HV-15 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-15 > Project: Hibernate Validator > Issue Type: Bug > Components: engine > Environment: Hibernate 3.0.5 > Oracle 8.1.7 (running on Win XP Pro) > Reporter: Aye Thu > Priority: Minor > Fix For: 3.1.0.CR2 > > > The following validation code: > @Past > public Date getBirthDate() > { > return birthDate; > } > produces the following DDL when using the OracleDialect: > create table Person (party_id number(19,0) not null, birth_date date check (birth_date < current_date), primary key (party_id)) > The "current_date" was introduced only in Oracle 9i and is not available in earlier Oracle versions and the following SQL exception is thrown: > ORA-02438: Column check constraint cannot reference other columns > According to Gavin, the current validation framework is not aware of Dialects. (http://forum.hibernate.org/viewtopic.php?t=943378) -- 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

16 years, 5 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HV-65) @Past cannot use current_date as per the ANSI SQL spec

by Emmanuel Bernard (JIRA)

@Past cannot use current_date as per the ANSI SQL spec ------------------------------------------------------ Key: HV-65 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-65 Project: Hibernate Validator Issue Type: Bug Components: validators Affects Versions: 3.1.0.CR1 Reporter: Emmanuel Bernard Priority: Minor Fix For: 3.1.0.CR2 They want to be overly protective I imagine, too bad :( -- 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

16 years, 5 months

1
1
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

16 years, 5 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

16 years, 5 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

16 years, 5 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

16 years, 5 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

16 years, 5 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-3333) build Documentation has a typo and includes a lie re:jdk version

by Andrew C. Oliver (JIRA)

build Documentation has a typo and includes a lie re:jdk version ---------------------------------------------------------------- Key: HHH-3333 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3333 Project: Hibernate3 Issue Type: Bug Components: build, documentation Affects Versions: 3.2.4.sp1 Reporter: Andrew C. Oliver Priority: Minor See here: http://hibernate.org/6.html#A6 "Compiling Hibernate Run build.xml with Ant under JDK 1.2 or later (JKD 1.4 required" Should be JDK 1.4 required However actually "or later" is an error http://opensource.atlassian.com/projects/hibernate/browse/HHH-2446 as JDK 6+ cannot be used to build. "You need to use JDK 5.0 or later" is said for Hibernate Annotations, but I cannot evaluate the statement by itself nor would it likely be very fun to have H3 compiled into JDK5 classes and H3A in JDK6... It should be corrected to prevent lots of duplicate JIRA bugs saying "I followed the instructions but H3 doesn't compile!" -- 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

16 years, 5 months

3
5
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues August 2008