February 2009 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (BVAL-12) <T> in ValidatorContext<T> Validator<T> and InvalidConstraint<T> are inadequately considered unique

by Emmanuel Bernard (JIRA)

<T> in ValidatorContext<T> Validator<T> and InvalidConstraint<T> are inadequately considered unique --------------------------------------------------------------------------------------------------- Key: BVAL-12 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-12 Project: Bean Validation Issue Type: Sub-task Components: ri-general Reporter: Emmanuel Bernard Assignee: Hardy Ferentschik In ValidatorImpl.validate() T Generic of ValidatorContext<T> and InvalidConstraint<T> are likely to be different than the Validator<T> A context can be created in a validator (T are equal). but the same context (a clone really) can be passed to a sub validator. Ts are then different. I believe it's the same for InvalidConstraints. An IC created by a subvalidator<U> will craete IC<U>, you will need to convert them in IC<T> when coming to the root validator<T>. So we need something like private <U> List<InvalidConstraintImpl<T>> validate(ValidationContext<U> context, List<String> groups) { } same for similar methods. -- 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, 9 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3233) Integer overflow in TableHiLoGenerator

by Hauke Rabe (JIRA)

Integer overflow in TableHiLoGenerator --------------------------------------- Key: HHH-3233 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3233 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.2 Reporter: Hauke Rabe The TableGenerator use for id generation the type INTEGER. The subclass TableHiLoGenerator use these id for multiplication with the maxLo value. But if you mutiply two int and assign the result to a long you can get an integer overflow. The TableGenerator should work with long values, or must be able to configure. -- 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, 9 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2983) Properties of a Map key not consistently populated before being put into the Map

by Dobes Vandermeer (JIRA)

Properties of a Map key not consistently populated before being put into the Map -------------------------------------------------------------------------------- Key: HHH-2983 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2983 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.5 Environment: Glassfish v2 b58, PostgreSQL 8.2, running in Windows XP Reporter: Dobes Vandermeer I'm getting weird behavior where my map correctly has two entries when fetched as part of a list, and only one entry when I fetch it using EntityManager.get(). Here's an abbreviated version of the mapping for the class that contains the Map: @Entity(name="Account") public class Account implements Comparable<Account>, SecurityChecks { private Long id; private Map<Currency, Balance> balances = new HashMap<Currency, Balance>(); // Current balance in each currency public Account() { } @Id @GeneratedValue public Long getId() { return id; } public void setId(Long id) { this.id = id; } @OneToMany(cascade={CascadeType.ALL}, mappedBy="account") @MapKey(name="currency") public Map<Currency, Balance> getBalances() { return balances; } public void setBalances(Map<Currency, Balance> balances) { this.balances = balances; } } And the class that it contains: @Entity(name="Balance") @Table(uniqueConstraints={@UniqueConstraint(columnNames={ "account_id", "currency_id" })}) public class Balance implements SecurityChecks { private Long id; private Account account; private Currency currency; private long amount; @ManyToOne(cascade=CascadeType.PERSIST, optional=false) public Account getAccount() { return account; } public void setAccount(Account account) { this.account = account; } @Column(nullable=false) public long getAmount() { return amount; } public void setAmount(long amount) { this.amount = amount; } @ManyToOne(cascade=CascadeType.PERSIST, optional=false) @JoinColumn(name="currency_id") public Currency getCurrency() { return currency; } public void setCurrency(Currency currency) { this.currency = currency; } @Id @GeneratedValue public Long getId() { return id; } public void setId(Long id) { this.id = id; } } And a class that has a list of Accounts: @Entity(name="Business") public class Business implements SecurityChecks { private Long id; private String name; private List<Account> accounts = new ArrayList<Account>(); @Id @GeneratedValue public Long getId() { return id; } public void setId(Long id) { this.id = id; } @OneToMany(mappedBy="business", cascade={CascadeType.ALL}) public List<Account> getAccounts() { return accounts; } public void setAccounts(List<Account> accounts) { this.accounts = accounts; } @Column(nullable=false) public String getName() { return name; } public void setName(String name) { this.name = name; } } Here's the definition of Currency: package com.habitsoft.books.model; import javax.persistence.Entity; import javax.persistence.GeneratedValue; import javax.persistence.Id; import javax.persistence.Transient; import com.habitsoft.books.service.client.CurrencyFormatter; @Entity(name="Currency") public class Currency implements Comparable<Currency> { private Long id; private String currencyCode; private String name; private String prefix = ""; private String suffix = ""; private int decimalPlaces; @Id @GeneratedValue public Long getId() { return id; } public void setId(Long id) { this.id = id; } @Override public int hashCode() { final int PRIME = 31; int result = 1; result = PRIME * result + ((getCurrencyCode() == null) ? 0 : getCurrencyCode().hashCode()); return result; } @Override public boolean equals(Object obj) { if (this == obj) return true; if (obj == null) return false; if (getClass() != obj.getClass()) return false; final Currency other = (Currency) obj; if (getCurrencyCode() == null) { if (other.getCurrencyCode() != null) return false; } else if (!getCurrencyCode().equals(other.getCurrencyCode())) return false; return true; } public int compareTo(Currency obj) { if (this == obj) return 0; if (obj == null) return -1; final Currency other = (Currency) obj; return getCurrencyCode().compareTo(other.getCurrencyCode()); } public String getCurrencyCode() { return currencyCode; } public void setCurrencyCode(String currencyCode) { this.currencyCode = currencyCode; } public String getName() { return name; } public void setName(String name) { this.name = name; } } Here's a line of code I use to fetch the Account directly: return em.find(Account.class, accountId); Here's how I fetch the list of accounts for a business: Business business = em.find(Business.class, businessId); return business.getAccounts().subList(offset, offset+limit); What is very, very odd to me is that the Accounts returned by the first form have just a single Balance instance in the map, when there should be two, whereas the ones returned by the second form have both entries I'm expecting. Hibernate prints the following SQL queries: Hibernate: select account0_.id as id270_0_, account0_.business_id as business5_270_0_, account0_.description as descript2_270_0_, account0_.name as name270_0_, account0_.type as type270_0_ from Account account0_ where account0_.id=? Hibernate: select balances0_.account_id as account3_2_, balances0_.id as id2_, balances0_.currency_id as formula5_2_, balances0_.id as id271_1_, balances0_.account_id as account3_271_1_, balances0_.amount as amount271_1_, balances0_.currency_id as currency4_271_1_, currency1_.id as id275_0_, currency1_.currencyCode as currency2_275_0_, currency1_.decimalPlaces as decimalP3_275_0_, currency1_.name as name275_0_, currency1_.prefix as prefix275_0_, currency1_.suffix as suffix275_0_ from Balance balances0_ inner join Currency currency1_ on balances0_.currency_id=currency1_.id where balances0_.account_id=? If I execute these queries against the database manually, the correct number of results is returned, so it seems likely that hibernate is generating the correct query, but then populating the map incorrectly. I took a guess that hashCode() and equals() in Currency were the most likely cause of the issue and indeed if I change them to use id instead of currencyCode the problem goes away. So, for some odd reason hibernate is populating the id field and not the other fields, and then putting it into the Map, but only when the object is fetched directly. This seems to point to some inconsistency in the way hibernate is initializing the objects and maps, somewhere. The workaround is to not use any fields except id in hashCode() and equals() for an entity used as a map key, and to ensure you call persist() on the key objects before putting them into the map. This seems like a reasonable constraint to me, but it would be nice if the behavior was more consistent to avoid excessive head-scratching. -- 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, 9 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3779) "org.hibernate.MappingException: An audited relation to a non-audited entity" during schema-export ant task

by Joe Spears (JIRA)

"org.hibernate.MappingException: An audited relation to a non-audited entity" during schema-export ant task ----------------------------------------------------------------------------------------------------------- Key: HHH-3779 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3779 Project: Hibernate Core Issue Type: Bug Components: envers Environment: hibernate version 3.3.1, annotations 3.4.0, em 3.4.0 envers latest snapshot (svn revision 16019) Reporter: Joe Spears Attachments: HHH3740-jlspea01-a.zip This is a re-submit of symptoms described in HHH-3740. This time, however, I cannot create a schema for an audited entity that has a manyToOne to a non audited entity using the Envers ant task. When I do, I get a org.hibernate.MappingException: An audited relation to a non-audited entity xxx.xxx For example: org.hibernate.MappingException: An audited relation to a non-audited entity com.mynamespace.MyNonAuditedClass! at org.hibernate.tool.ant.HibernateToolTask.reportException(HibernateToolTask.java:226) at org.hibernate.tool.ant.HibernateToolTask.execute(HibernateToolTask.java:189) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288) 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 org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:357) at org.apache.tools.ant.Target.performTasks(Target.java:385) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329) at org.apache.tools.ant.Project.executeTarget(Project.java:1298) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) at org.apache.tools.ant.Project.executeTargets(Project.java:1181) at org.apache.tools.ant.Main.runBuild(Main.java:698) at org.apache.tools.ant.Main.startAnt(Main.java:199) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257) at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104) Caused by: org.hibernate.MappingException: An audited relation to a non-audited entity com.mynamespace.MyNonAuditedClass! at org.hibernate.envers.configuration.metadata.ToOneRelationMetadataGenerator.addToOne(ToOneRelationMetadataGenerator.java:59) at org.hibernate.envers.configuration.metadata.AuditMetadataGenerator.addValue(AuditMetadataGenerator.java:126) at org.hibernate.envers.configuration.metadata.AuditMetadataGenerator.addProperties(AuditMetadataGenerator.java:161) at org.hibernate.envers.configuration.metadata.AuditMetadataGenerator.generateSecondPass(AuditMetadataGenerator.java:348) at org.hibernate.envers.configuration.EntitiesConfigurator.configure(EntitiesConfigurator.java:96) at org.hibernate.envers.configuration.AuditConfiguration.<init>(AuditConfiguration.java:86) at org.hibernate.envers.configuration.AuditConfiguration.getFor(AuditConfiguration.java:99) at org.hibernate.envers.ant.JPAConfigurationTaskWithEnvers.doConfiguration(JPAConfigurationTaskWithEnvers.java:36) at org.hibernate.tool.ant.ConfigurationTask.getConfiguration(ConfigurationTask.java:55) at org.hibernate.tool.ant.HibernateToolTask.getConfiguration(HibernateToolTask.java:302) at org.hibernate.tool.ant.Hbm2DDLExporterTask.createExporter(Hbm2DDLExporterTask.java:51) at org.hibernate.tool.ant.ExporterTask.execute(ExporterTask.java:39) at org.hibernate.tool.ant.HibernateToolTask.execute(HibernateToolTask.java:186) ... 17 more --- Nested Exception --- org.hibernate.MappingException: An audited relation to a non-audited entity com.mynamespace.MyNonAuditedClass! at org.hibernate.envers.configuration.metadata.ToOneRelationMetadataGenerator.addToOne(ToOneRelationMetadataGenerator.java:59) at org.hibernate.envers.configuration.metadata.AuditMetadataGenerator.addValue(AuditMetadataGenerator.java:126) at org.hibernate.envers.configuration.metadata.AuditMetadataGenerator.addProperties(AuditMetadataGenerator.java:161) at org.hibernate.envers.configuration.metadata.AuditMetadataGenerator.generateSecondPass(AuditMetadataGenerator.java:348) at org.hibernate.envers.configuration.EntitiesConfigurator.configure(EntitiesConfigurator.java:96) at org.hibernate.envers.configuration.AuditConfiguration.<init>(AuditConfiguration.java:86) at org.hibernate.envers.configuration.AuditConfiguration.getFor(AuditConfiguration.java:99) at org.hibernate.envers.ant.JPAConfigurationTaskWithEnvers.doConfiguration(JPAConfigurationTaskWithEnvers.java:36) at org.hibernate.tool.ant.ConfigurationTask.getConfiguration(ConfigurationTask.java:55) at org.hibernate.tool.ant.HibernateToolTask.getConfiguration(HibernateToolTask.java:302) at org.hibernate.tool.ant.Hbm2DDLExporterTask.createExporter(Hbm2DDLExporterTask.java:51) at org.hibernate.tool.ant.ExporterTask.execute(ExporterTask.java:39) at org.hibernate.tool.ant.HibernateToolTask.execute(HibernateToolTask.java:186) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288) 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 org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:357) at org.apache.tools.ant.Target.performTasks(Target.java:385) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329) at org.apache.tools.ant.Project.executeTarget(Project.java:1298) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) at org.apache.tools.ant.Project.executeTargets(Project.java:1181) at org.apache.tools.ant.Main.runBuild(Main.java:698) at org.apache.tools.ant.Main.startAnt(Main.java:199) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257) at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104) My hope was that this issue was resolved in the current revision based on the feedback of HHH-3740, but when I compiled that revision I still got the stack-trace. re-attaching my simple, simple ant project here (as I did before I discovered I cannot reopen HHH-3740) -- 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, 9 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2574) Upload to maven2 repository

by David J. M. Karlsen (JIRA)

Upload to maven2 repository --------------------------- Key: HHH-2574 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2574 Project: Hibernate3 Issue Type: Bug Components: build Affects Versions: 3.2.3 Environment: N/A Reporter: David J. M. Karlsen Attachments: hibernate-3.2.3.ga.pom Package 3.2.3ga to http://repo1.maven.org/maven2/org/hibernate/hibernate/ (Ideally source + javadocs, but at least pom and jar). pom attached -- 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, 9 months

2
2
0 / 0

[Hibernate-JIRA] Created: (EJB-386) Deploy 3.4.0 GA to the maven2 central repo

by Steven Cummings (JIRA)

Deploy 3.4.0 GA to the maven2 central repo ------------------------------------------ Key: EJB-386 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-386 Project: Hibernate Entity Manager Issue Type: Task Components: EntityManager Affects Versions: 3.4.0.GA Reporter: Steven Cummings The JPA/Hibernate page [1] lists 3.4.0.GA as the latest version of entitymanager. Please deploy the artifacts (including source and javadoc jars) to the maven2 central repo. Thanks. [1] http://www.hibernate.org/397.html -- 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, 9 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2976) Documentation of Native SQLQuery contains errors

by Philippe Mouawad (JIRA)

Documentation of Native SQLQuery contains errors ------------------------------------------------ Key: HHH-2976 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2976 Project: Hibernate3 Issue Type: Bug Components: documentation Affects Versions: 3.2.5 Environment: Hibernate 3.x to 3.2.5 Reporter: Philippe Mouawad Priority: Minor http://www.hibernate.org/hib_docs/reference/en/html/querysql.html This code is wrong: String sql = "SELECT ID as {c.id}, NAME as {c.name}, " + "BIRTHDATE as {c.birthDate}, MOTHER_ID as {c.mother}, {mother.*} " + "FROM CAT_LOG c, CAT_LOG m WHERE {c.mother} = c.ID"; List loggedCats = sess.createSQLQuery(sql) .addEntity("cat", Cat.class) .addEntity("mother", Cat.class).list() See: HHH-2974 -- 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, 9 months

5
6
0 / 0

[Hibernate-JIRA] Created: (HHH-3190) Correction in "Hibernate Core for Java"->"Reference Documentation" in chapter 7.6

by David Pinho (JIRA)

Correction in "Hibernate Core for Java"->"Reference Documentation" in chapter 7.6 --------------------------------------------------------------------------------- Key: HHH-3190 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3190 Project: Hibernate3 Issue Type: Bug Components: documentation Reporter: David Pinho Priority: Trivial In http://www.hibernate.org/hib_docs/v3/reference, the first snippet in chapter 7.6 "More complex association mappings", contains: ... <property name="effectiveEndDate" type="date"/> <property name="effectiveStateDate" type="date" not-null="true"/> Shouldn' it be effectiveStartDate instead of effectiveStateDate? -- 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, 9 months

4
6
0 / 0

[Hibernate-JIRA] Created: (HHH-3080) its just a typo

by mohammad hassan shamsi (JIRA)

its just a typo ---------------- Key: HHH-3080 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3080 Project: Hibernate3 Issue Type: Improvement Components: documentation Affects Versions: 3.2.5 Reporter: mohammad hassan shamsi Priority: Trivial document : hibernate_reference.pdf page : 27 in this sentence : Hibernate can automatically bind these ojects to the current thread of execution. objects is typed ojects. -- 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, 9 months

5
7
0 / 0

[Hibernate-JIRA] Created: (HHH-3049) Add the performance test attached to HHH-2645 to test suite

by Gail Badner (JIRA)

Add the performance test attached to HHH-2645 to test suite ----------------------------------------------------------- Key: HHH-3049 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3049 Project: Hibernate3 Issue Type: Improvement Components: testsuite Reporter: Gail Badner Assignee: Gail Badner Fix For: 3.3 The performance test attached to HHH-2645 compares the following Map implementations used by org.hibernate.tuple.EntityModeToTuplizerMapping.: Collections.synchronizedMap( new org.apache.commons.collections.SequencedHashMap() ) <= used in pre-3.2.6 org.apache.commons.collections.FastHashMap() org.hibernate.util.FastHashMap <= used in 3.2.6 java.util.concurrent.ConcurrentHashMap() <= need Java 1.5 for this new EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap() EDU.oswego.cs.dl.util.concurrent.ConcurrentReaderHashMap() This test should be added to the test suite as an integration test. Reminder: Read Paul Cowan's comment from 16/Nov/07 for corrections to the attached test. -- 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, 9 months

2
4
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 February 2009