February 2009 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (BVAL-127) remove ConstraintValidation.getGroups()

by Emmanuel Bernard (JIRA)

remove ConstraintValidation.getGroups() --------------------------------------- Key: BVAL-127 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-127 Project: Bean Validation Issue Type: Task Components: spec-general Affects Versions: 1.0 public draft Reporter: Emmanuel Bernard Fix For: 1.0 proposed final draft -- 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, 1 month

1
2
0 / 0

[Hibernate-JIRA] Created: (HV-123) Wrong elementType in MetaConstraint constructor

by Alaa Mohssen Nassef (JIRA)

Wrong elementType in MetaConstraint constructor ----------------------------------------------- Key: HV-123 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-123 Project: Hibernate Validator Issue Type: Bug Affects Versions: 4.0.0.Alpha1 Reporter: Alaa Mohssen Nassef Assignee: Alaa Mohssen Nassef Fix For: 4.0.0.Alpha2 In the first MetaConstraint constructor, which takes "Type t", the elementType passed to the full constructor is ElementType.FIELD and not ElementType.TYPE. This causes the getValue() method to return null for constraints that annotate classes. -- 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, 1 month

3
5
0 / 0

[Hibernate-JIRA] Commented: (HHH-1329) SchemaValidator fail when views are involved

by Julien Kronegg (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1329?page=c... ] Julien Kronegg commented on HHH-1329: ------------------------------------- Materialized views retrieval is not working using DB2, see http://opensource.atlassian.com/projects/hibernate/browse/HHH-3780 > SchemaValidator fail when views are involved > -------------------------------------------- > > Key: HHH-1329 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1329 > Project: Hibernate Core > Issue Type: Bug > Components: metamodel > Affects Versions: 3.1 > Environment: database: oracle9i > hibernate: 3.1 > jdbc driver: ojdbc14-10.2.0.1.0 > Reporter: Yariv Yaari > Assignee: Diego Plentz > Fix For: 3.2.6 > > > All calls in org.hibernate.tool.hbm2ddl.DatabaseMetadata.getTableMetadata to java.sql.DatabaseMetaData.getTables set the fourth parameter (types) to {"TABLE"} (defined as a class-level constant). > In the documentation of getTables it is not defined what are the meanings of the types passed as parameter, only that all the strings must be in java.sql.DatabaseMetaData.getTablesTypes return value. In oracle9i with ojdbc14-10.2.0.1.0.jar views are returned if types contains "VIEW" and not if its {"TABLE"}. It is a major problem only if hibernate.hbm2ddl.auto is set to validate, if it's set to update it will log some errors (since it can't create or alter the table, there is a view with this name) but it won't fail the deployment, and since in SQL views are treated as tables, there will be no more problems. > It should be checked for more databases/jdbc drivers. > It is not obvious what should be the solution. > Pass {"TABLE","VIEW"} always? Pass them if they are in getTableTypes? > Put it as part of the dialect, default to {"TABLE"} and change it in oreacle-dialects? -- 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, 1 month

1
0
0 / 0

[Hibernate-JIRA] Created: (ANN-806) Ability to have prefix embedded object columns

by Thad Cox (JIRA)

Ability to have prefix embedded object columns ---------------------------------------------- Key: ANN-806 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-806 Project: Hibernate Annotations Issue Type: Improvement Affects Versions: 3.4.0.GA Reporter: Thad Cox It would be very helpful if there were a way to specify a prefix for the column names of an embedded element as was suggested in the comments ANN-99. By this I mean @Embedded @ColumnPrefix("homeaddress") public Address getHomeAddress { return this.homeAddress; } The reasoning for rejecting the initial suggestion as put in the description of the issue made sense but the final solution of changing the naming strategy ends up being a very drastic solution for a simple problem. The problem is that for some embedded objects that I only use once I want to just have the plain column name, other times I use it twice in the same object and I need the column names to have different prefixes. An additional problem the naming strategy solution presents is that if I specify the column name in the embedded object then I can't use it. For example if I have an address object on a user and I want the postal code column to always end in "postal_code" instead of "postalcode" I can't use the naming strategy to add the prefix at all. -- 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, 1 month

1
0
0 / 0

[Hibernate-JIRA] Created: (HV-120) ConstraintDescriptor.getGroups() returns Default.class if no group is declared on the constraint

by Emmanuel Bernard (JIRA)

ConstraintDescriptor.getGroups() returns Default.class if no group is declared on the constraint ------------------------------------------------------------------------------------------------ Key: HV-120 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-120 Project: Hibernate Validator Issue Type: Bug Components: engine Reporter: Emmanuel Bernard Priority: Minor Fix For: 4.0.0.Alpha2 Adjusted in the JavaDoc. -- 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, 1 month

2
2
0 / 0

[Hibernate-JIRA] Commented: (HHH-1523) LazyInitializationError on enabling query cache...

by Sylvain Veyrié (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1523?page=c... ] Sylvain Veyrié commented on HHH-1523: ------------------------------------- We use a lot "join fetch" (and I think we aren't the only ones). After some tests, we tried to enable L2 query cache, but this bug made all application stacktrace. As we do not want to use "initialize()" (as this is an ugly hack to apply everywhere) or stop using "join fetch", we can't activate query cache and exploit this tuning possibility. > LazyInitializationError on enabling query cache... > -------------------------------------------------- > > Key: HHH-1523 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1523 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.0.5, 3.1 > Environment: 3.0.1 and 3.1, HSQLDB and Oracle > Reporter: Vikas Sasidharan > Attachments: cache_issue.log, QueryCacheIssue.zip > > > I have two domain objects - Employee and Department - and there is a 1:N relationship from Department to Employee. When I join fetch an Employee with its Department, without query cache enabled, it works fine. If I enable query cache for this same query, it bombs with a LazyInitializationException. > Notes: > 1) We get this error only if query cache is enabled. > 2) We observed the same behaviour on both oscache and ehcache > 3) Calling Hibernate.initialize() explicitly after firing the HQL seems to work. The initialization does not fire an extra query though (it seems to pick it from the cache). > 4) Setting "lazy=false" on the "many-to-one" mapping also works. However, it wouldn't be acceptable. > Hibernate version: 3.0.5 > Mapping documents: > Employee.hbm.xml > <hibernate-mapping> > <class name="tavant.platform.test.domain.Employee" > table="CACHE_ISSUE_EMP" lazy="true" dynamic-update="true" dynamic-insert="true"> > <cache usage="read-write" /> > <id name="id" column="EMP_ID" type="java.lang.Long" > access="field" unsaved-value="null"> > <generator class="increment" /> > </id> > > <property name="name" type="string" update="true" > insert="true" column="EMP_NAME"/> > <many-to-one name="department" class="tavant.platform.test.domain.Department" > cascade="none" outer-join="auto" update="true" insert="true" column="DEPARTMENT_ID"/> > </class> > </hibernate-mapping> > > Department.hbm.xml > <hibernate-mapping> > <class name="tavant.platform.test.domain.Department" table="CACHE_ISSUE_DEP" > lazy="true" dynamic-update="true" dynamic-insert="true"> > > <cache usage="read-write" /> > <id name="id" column="DEPARTMENT_ID" > type="java.lang.Long" access="field"> > <generator class="increment"/> > </id> > <property name="name" type="java.lang.String" > update="false" insert="true" column="NAME"/> > <bag name="employees" lazy="true" > inverse="true" cascade="save-update" access="field"> > <cache usage="read-write"/> > <key column="DEPARTMENT_ID"/> > <one-to-many class="tavant.platform.test.domain.Employee"/> > </bag> > </class> > </hibernate-mapping> > > Code between sessionFactory.openSession() and session.close(): > public Employee getEmployeeWithDepartment(String empName) { > Session session = null; > try { > session = sessionFactory.openSession(); > Employee emp = (Employee) session.createQuery( > "from Employee e join fetch e.department where e.name = :name") > .setString("name", empName) > .setCacheable(true) > .uniqueResult(); > // If I uncomment the next line, this works (even without > // firing an extra query)! > // Hibernate.initialize(emp.getDepartment()); > return emp; > } finally { > if (session != null) { > session.close(); > } > } > } > > // First load employee and populate cahces > Employee emp = test.getEmployeeWithDepartment(EMPLOYEE_NAME); > System.out.println("Employee : " + emp + ", Employee.Department : " > + emp.getDepartment()); > > // Now try to make use of the cache > emp = test.getEmployeeWithDepartment(EMPLOYEE_NAME); > System.out.println("Employee : " + emp + ", Employee.Department : " > + emp.getDepartment()); > > Full stack trace of any exception that occurs: > org.hibernate.LazyInitializationException: could not initialize proxy - the owning Session was closed > at org.hibernate.proxy.AbstractLazyInitializer.initialize(AbstractLazyInitializer.java:53) > at org.hibernate.proxy.AbstractLazyInitializer.getImplementation(AbstractLazyInitializer.java:84) > at org.hibernate.proxy.CGLIBLazyInitializer.intercept(CGLIBLazyInitializer.java:134) > at tavant.platform.test.domain.Department$$EnhancerByCGLIB$$67b26899.toString(<generated>) > at java.lang.String.valueOf(String.java:2131) > at java.lang.StringBuffer.append(StringBuffer.java:370) > at tavant.platform.test.client.TestPrefetchRelationWithQueryCacheEnabled.main(TestPrefetchRelationWithQueryCacheEnabled.java:116) > > Name and version of the database you are using: > We have noticed this on Oracle and HSQL > The generated SQL (show_sql=true): > #First read, goes fine > Hibernate: select employee0_.EMP_ID as EMP1_0_, department1_.DEPARTMENT_ID as DEPARTMENT1_1_, employee0_.EMP_NAME as EMP2_1_0_, employee0_.DEPARTMENT_ID as DEPARTMENT3_1_0_, department1_.NAME as NAME0_1_ from CACHE_ISSUE_EMP employee0_ inner join CACHE_ISSUE_DEP department1_ on employee0_.DEPARTMENT_ID=department1_.DEPARTMENT_ID where (employee0_.EMP_NAME=? ) > #Prints the Employee and Department fine > Employee : [Id : 1, name : testEmployee], Employee.Department : [Id : 1, name : testDepartment] > #Second read bombs! > org.hibernate.LazyInitializationException: could not initialize proxy - the owning Session was closed > at org.hibernate.proxy.AbstractLazyInitializer.initialize(AbstractLazyInitializer.java:53) > at org.hibernate.proxy.AbstractLazyInitializer.getImplementation(AbstractLazyInitializer.java:84) > at org.hibernate.proxy.CGLIBLazyInitializer.intercept(CGLIBLazyInitializer.java:134) > [..] > Please have a look at the post [http://forum.hibernate.org/viewtopic.php?t=955839] for more details and follow ups. > Kindly help. I am attaching an Eclipse Project containing the TestCase. The main file is TestPrefetchRelationWithQueryCacheEnabled. > Thanks, > Vikas -- 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, 1 month

1
0
0 / 0

[Hibernate-JIRA] Created: (BVAL-121) Define built-in constraints plural forms

by Emmanuel Bernard (JIRA)

Define built-in constraints plural forms ---------------------------------------- Key: BVAL-121 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-121 Project: Bean Validation Issue Type: New Feature Components: spec-general Reporter: Emmanuel Bernard Fix For: 1.0 proposed final draft -- 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, 1 month

1
1
0 / 0

[Hibernate-JIRA] Created: (BVAL-125) @Size.min default value should be 0

by Emmanuel Bernard (JIRA)

@Size.min default value should be 0 ----------------------------------- Key: BVAL-125 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-125 Project: Bean Validation Issue Type: Bug Components: spec-general Affects Versions: 1.0 public draft Reporter: Emmanuel Bernard Fix For: 1.0 proposed final draft -- 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, 1 month

2
4
0 / 0

[Hibernate-JIRA] Created: (BVAL-126) Clarify group seuquence logic

by Emmanuel Bernard (JIRA)

Clarify group seuquence logic ----------------------------- Key: BVAL-126 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-126 Project: Bean Validation Issue Type: Improvement Components: spec-general Affects Versions: 1.0 public draft Reporter: Emmanuel Bernard Fix For: 1.0 proposed final draft -- 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, 1 month

1
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3740) Unable to build EntityManagerFactory when using a non-audited ManyToOne in Audited components

by Erik-Berndt Scheper (JIRA)

Unable to build EntityManagerFactory when using a non-audited ManyToOne in Audited components ---------------------------------------------------------------------------------------------- Key: HHH-3740 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3740 Project: Hibernate Core Issue Type: Bug Components: envers Affects Versions: 3.4 Reporter: Erik-Berndt Scheper Since the resolution of HHH-3563, relations in components are now supported. However, if I try to use a @NotAudited @ManyToOne in an @Embeddable, then Envers does not start up. Removing @NotAudited to the @ManyToOne @Embeddable and adding @Audited to the related entity resolves the issue. This does not occur with @NotAudited @ManyToOne in an @Entity. See attached test case to reproduce this issue. Stack trace: javax.persistence.PersistenceException: Unable to build EntityManagerFactory at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:677) at org.hibernate.envers.test.AbstractEntityTest.init(AbstractEntityTest.java:94) at org.hibernate.envers.test.AbstractEntityTest.init(AbstractEntityTest.java:82) 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.testng.internal.MethodHelper.invokeMethod(MethodHelper.java:580) at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:398) at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:145) at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:82) at org.testng.internal.TestMethodWorker.invokeBeforeClassMethods(TestMethodWorker.java:167) at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:104) at org.testng.TestRunner.runWorkers(TestRunner.java:712) at org.testng.TestRunner.privateRun(TestRunner.java:582) at org.testng.TestRunner.run(TestRunner.java:477) at org.testng.SuiteRunner.runTest(SuiteRunner.java:324) at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:319) at org.testng.SuiteRunner.privateRun(SuiteRunner.java:292) at org.testng.SuiteRunner.run(SuiteRunner.java:198) at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:823) at org.testng.TestNG.runSuitesLocally(TestNG.java:790) at org.testng.TestNG.run(TestNG.java:708) at org.testng.remote.RemoteTestNG.run(RemoteTestNG.java:73) at org.testng.remote.RemoteTestNG.main(RemoteTestNG.java:124) Caused by: org.hibernate.HibernateException: could not init listeners at org.hibernate.event.EventListeners.initializeListeners(EventListeners.java:205) at org.hibernate.cfg.Configuration.getInitializedEventListeners(Configuration.java:1352) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1341) at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:867) at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:669) ... 24 more Caused by: org.hibernate.MappingException: An audited relation to a non-audited entity org.hibernate.envers.test.entities.UnversionedStrTestEntity! 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.ComponentMetadataGenerator.addComponent(ComponentMetadataGenerator.java:40) at org.hibernate.envers.configuration.metadata.AuditMetadataGenerator.addValue(AuditMetadataGenerator.java:121) 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:87) at org.hibernate.envers.configuration.AuditConfiguration.getFor(AuditConfiguration.java:99) at org.hibernate.envers.event.AuditEventListener.initialize(AuditEventListener.java:232) at org.hibernate.event.EventListeners$1.processListener(EventListeners.java:198) at org.hibernate.event.EventListeners.processListeners(EventListeners.java:181) at org.hibernate.event.EventListeners.initializeListeners(EventListeners.java:194) ... 28 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

17 years, 1 month

3
5
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