January 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-5850) Consider calling findModified from findDirty

by Tobias Bergman (JIRA)

Consider calling findModified from findDirty -------------------------------------------- Key: HHH-5850 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5850 Project: Hibernate Core Issue Type: Improvement Reporter: Tobias Bergman The two methods AbstractEntityPersister.findModified() and AbstractEntityPersister.findDirty() seems to do exactly the same thing (code almost copy pasted, names differ). findModified calls TypeHelper.findModified() which is also a copy-pasted version of TypeHelper.findDirty(). While the methods seems to do the same why not just call findDirty() from findModified() (which eliminates the copy pasted code). -- 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

14 years, 1 month

2
2
0 / 0

[Hibernate-JIRA] Created: (METAGEN-51) C3P0 connection pool tester is not called if buildSessionFactory failed due to wrong password

by asd (JIRA)

C3P0 connection pool tester is not called if buildSessionFactory failed due to wrong password --------------------------------------------------------------------------------------------- Key: METAGEN-51 URL: http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-51 Project: Hibernate Metamodel Generator Issue Type: Bug Environment: I used Hibernate+C3P0. Here is a my config: setProperty("hibernate.connection.driver_class", "com.mysql.jdbc.Driver"); setProperty("hibernate.dialect", "org.hibernate.dialect.MySQLDialect"); setProperty("hibernate.connection.url", "jdbc:mysql://localhost:" + getDBPort() + "/emplatcore"); setProperty("hibernate.connection.username", Network.getInstance() .getMASDBAccountCred().getUserName()); setProperty("hibernate.connection.password", Network.getInstance() .getMASDBAccountCred().getPassword()); setProperty("hibernate.show_sql", "false"); setProperty("hibernate.c3p0.aquire_increment", Integer.toString(getConnectionAcquireIncrement())); setProperty("hibernate.c3p0.idle_test_period", Integer.toString(getIdleTestPeriod())); setProperty("hibernate.c3p0.timeout", Integer.toString(getIdleTimeout())); setProperty("hibernate.c3p0.max_size", Integer.toString(getMaxConnections())); setProperty("hibernate.c3p0.max_statements", Integer.toString(getStatementCache())); setProperty("hibernate.c3p0.min_size", Integer.toString(getInitialPoolSize())); setProperty( "c3p0.connectionTesterClassName", "com.nortelnetworks.mcp.ne.mediaserver.db.dao.hibernate.c3p0.MCPHibernateConnectionTester"); setProperty("c3p0.acquireRetryAttempts", Integer.toString(getAcquireRetryAttempts())); setProperty("c3p0.acquireRetryDelay", Long.toString(getAcquireRetryDelay())); Reporter: asd Assignee: Hardy Ferentschik Priority: Critical I tried to check if connect is up or down to MySQL using C3P0 connection pool tester. It works if password is correct. But password can be changed and I need to let user know that there is no connection to MySQL. I want to understand why buildSessionFactory() does not start connection tester. -- 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

14 years, 1 month

3
6
0 / 0

[Hibernate-JIRA] Created: (HHH-5851) Make UPPER or LOWER configurable when using Example.ignoreCase()

by Andreas Brunner (JIRA)

Make UPPER or LOWER configurable when using Example.ignoreCase() ---------------------------------------------------------------- Key: HHH-5851 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5851 Project: Hibernate Core Issue Type: New Feature Components: query-criteria Affects Versions: 3.6.0 Reporter: Andreas Brunner When executing a query created via the criteria api using an Example object and ignoreCase, like the following: List results = session.createCriteria(Parent.class) .add( Example.create(parent).ignoreCase() ) .list(); the resulting SQL query uses the LOWER function of the database to ignoring the case. It would be great if there would be a way to configure Hibernate to user UPPER instead of LOWER to ignore the case. -- 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

14 years, 1 month

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-5359) Derived entity usecase fails when the association is bidirectional

by Hardy Ferentschik (JIRA)

Derived entity usecase fails when the association is bidirectional ------------------------------------------------------------------ Key: HHH-5359 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5359 Project: Hibernate Core Issue Type: Bug Components: entity-manager Affects Versions: 3.5.3 Reporter: Hardy Ferentschik Fix For: 3.6 See https://forum.hibernate.org/viewtopic.php?f=9&t=1005649 The exception is {noformat} org.hibernate.AnnotationException: mappedBy reference an unknown target entity property: org.hibernate.test.annotations.derivedidentities.bidirectional.Dependent.emp in org.hibernate.test.annotations.derivedidentities.bidirectional.Employee.dependents at org.hibernate.cfg.annotations.CollectionBinder.bindStarToManySecondPass(CollectionBinder.java:655) at org.hibernate.cfg.annotations.CollectionBinder$1.secondPass(CollectionBinder.java:619) at org.hibernate.cfg.CollectionSecondPass.doSecondPass(CollectionSecondPass.java:66) at org.hibernate.cfg.Configuration.secondPassCompile(Configuration.java:1221) at org.hibernate.cfg.AnnotationConfiguration.secondPassCompile(AnnotationConfiguration.java:383) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1377) at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:954) at org.hibernate.test.annotations.TestCase.buildConfiguration(TestCase.java:114) at org.hibernate.test.annotations.HibernateTestCase.setUp(HibernateTestCase.java:133) at org.hibernate.test.annotations.HibernateTestCase.runBare(HibernateTestCase.java:80) at com.intellij.junit3.JUnit3IdeaTestRunner.doRun(JUnit3IdeaTestRunner.java:108) at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:64) {noformat} The mapping is as follows: {code} @Entity public class Employee { @Id long empId; String empName; @OneToMany(mappedBy = "emp", fetch = FetchType.LAZY) private Set<Dependent> dependents; } {code} {code} @Entity //(a)IdClass(DependentId.class) public class Dependent implements Serializable { @Id @ManyToOne Employee emp; String name; } {code} It does not work with @IdClass either. -- 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

14 years, 1 month

4
13
0 / 0

[Hibernate-JIRA] Created: (HHH-5793) Query and timestamp caches to use cluster cache loader to avoid behaving like sync repl caches

by Galder Zamarreno (JIRA)

Query and timestamp caches to use cluster cache loader to avoid behaving like sync repl caches ---------------------------------------------------------------------------------------------- Key: HHH-5793 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5793 Project: Hibernate Core Issue Type: Bug Components: caching (L2) Affects Versions: 3.6.0, 3.5.6 Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 3.6.1, 4.0.0.Alpha1 As a result of the investigation carried out for https://issues.jboss.org/browse/ISPN-832, it was found out that async caches that have state transfer configured are effectively transformed into sync caches. This is not desirable by any means, so while https://issues.jboss.org/browse/ISPN-835 is addressed, Hibernate 2LC relying on this combo are switching to using a cluster cache loader. This JIRA involves changing the default configuration and fixing some code to maintain same semantics as before. -- 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

14 years, 1 month

1
4
0 / 0

[Hibernate-JIRA] Created: (HBX-1169) 3.2.4 fix broke non file based schemaupdate

by Max Rydahl Andersen (JIRA)

3.2.4 fix broke non file based schemaupdate ------------------------------------------- Key: HBX-1169 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1169 Project: Hibernate Tools Issue Type: Bug Components: ant Affects Versions: 3.2.4 Beta1 Reporter: Max Rydahl Andersen Assignee: Anthony Patricio Fix For: 3.2.4.GA HBX-757 broke the following ant where no outputfile is specified to just have it on the console output: <schemaupdate quiet="false" text="false"> <fileset dir="../test" id="id"> <include name="**/*TopDown.hbm.xml" /> </fileset> </schemaupdate> this results in a NPE. Now you have to add a bogus outputfile="notused.txt" to avoid the NPE but you now have a notused.txt file: <schemaupdate quiet="false" text="false" outputfile="notused.txt" > <fileset dir="../test" id="id"> <include name="**/*TopDown.hbm.xml" /> </fileset> </schemaupdate> -- 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

14 years, 1 month

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-5529) Bulk delete on Entity with @ElementCollection ignores the @CollectionTable

by Pascal Thivent (JIRA)

Bulk delete on Entity with @ElementCollection ignores the @CollectionTable -------------------------------------------------------------------------- Key: HHH-5529 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5529 Project: Hibernate Core Issue Type: Bug Components: entity-manager Affects Versions: 3.6.0.Beta4, 3.6.0.Beta3, 3.5.5, 3.6.0.Beta2, 3.6.0.Beta1, 3.5.4, 3.5.3, 3.5.2, 3.5.1, 3.5.0-Final, 3.5.0-CR-2, 3.5.0-CR-1, 3.5.0-Beta-4, 3.5.0-Beta-3, 3.5.0-Beta-2, 3.5.0.Beta-1 Environment: Hibernate 3.5.x, all database, all platforms. Reporter: Pascal Thivent Attachments: HHH-XXX.tar.gz I have an entity with a collection of basic elements mapped with @ElementCollection: {code} @Entity public class Foo { @Id @GeneratedValue private Long id; @ElementCollection @Column(name = "bar_column") @CollectionTable(name = "Bar") private Set<String> bars = new HashSet<String>(); public Long getId() { return id; } public void setId(Long id) { this.id = id; } public Set<String> getBars() { return bars; } public void setBars(Set<String> bars) { this.bars = bars; } } {code} A bulk delete on this entity fails due to constraint violation on the collection table (Hibernate ignores the collection table). I don't think that the following cascading restriction from the JPA 2.0 specification applies: {quote} h3. 4.10 Bulk Update and Delete Operations ... A delete operation only applies to entities of the specified class and its subclasses. It does not cascade to related entities. {quote} In other words, Hibernate should handle the collection table as we have no way to bulk delete the basic elements from the collection table. I have attached a test case allowing to reproduce the issue. -- 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

14 years, 1 month

5
11
0 / 0

[Hibernate-JIRA] Created: (HHH-5466) Create "Developer Guide"

by Steve Ebersole (JIRA)

Create "Developer Guide" ------------------------ Key: HHH-5466 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5466 Project: Hibernate Core Issue Type: Improvement Components: documentation Reporter: Steve Ebersole This is the more "action" or "story" based documentation -- 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

14 years, 2 months

2
22
0 / 0

[Hibernate-JIRA] Created: (HV-414) Assembly plugin fails with maven 3.0.1

by Hardy Ferentschik (JIRA)

Assembly plugin fails with maven 3.0.1 -------------------------------------- Key: HV-414 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-414 Project: Hibernate Validator Issue Type: Bug Components: build Affects Versions: 4.1.0.Final Reporter: Hardy Ferentschik Fix For: 4.2.0.CR1 When trying to run the assembly plugin (_mvn package assembly:assembly_) using maven 3.0.1 the build fails due to _ClassNotFoundException_s. The problem seems to be that when the assembly plugin forks for its build transitive dependencies are not getting included. As a workaround one can build with a maven 2.x version. -- 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

14 years, 2 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-5280) "java.lang.IllegalArgumentException: object is not an instance of declaring class" when persisting a object graph containing the same transient objetc twice.

by Benjamin Lerman (JIRA)

"java.lang.IllegalArgumentException: object is not an instance of declaring class" when persisting a object graph containing the same transient objetc twice. ------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-5280 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5280 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.2 Environment: Hibernate 3.5.2 Db: All? (At least h2 and mysql) Reporter: Benjamin Lerman Priority: Critical Attachments: hibernate-multi-parent.tgz, test.entity.TestCreate.txt I attach a maven project showing the bug. I have 3 classes, A, B, C with C have a one-to-many unidirectional relation to B and A. B have a one-to-many unidirectional relation to A. Those relations are mapped by foreign keys. The cascading properties for those relations are all save-update,persist For each of those relations, the inverse cardinality is 1 (which means A must be associated with a B and a C, and B must be associated with a C). I create an instance of C that I associate to an instance of B and an instance of A, and I associate the instance of B with the instance of A. I then try to save C, and I get the attached exception. For what I understood the problem is with the method StatefulPersistenceContext.getOwnerId: this method use a cache to retrieve the parent of the instance of A, but because A has 2 different parents (the instance of B and the instance of C), it does not retrieve the right one and try to call a method on the wrong entity. -- 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

14 years, 2 months

6
9
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues January 2011