July 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (METAGEN-69) When the root class of hierarchy does not declare @Id default access type cannot be resolved

by Igor Vaynberg (JIRA)

When the root class of hierarchy does not declare @Id default access type cannot be resolved -------------------------------------------------------------------------------------------- Key: METAGEN-69 URL: http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-69 Project: Hibernate Metamodel Generator Issue Type: Bug Components: processor Affects Versions: 1.1.1.Final Reporter: Igor Vaynberg Assignee: Hardy Ferentschik if we have {code} @MappedSuperClass Foo {} @Entity @Inheritance Bar extends Foo { @Id id } @Entity Baz extends Bar {} {code} Baz_ will not have any of Baz's bindings because while looking for access type the processor does not stop at Bar and continues to Foo which has default accesstype of null. Pull request with a test case incoming... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

2
7
0 / 0

[Hibernate-JIRA] Created: (METAGEN-72) Generate attributes for @Transient columns

by Adriano dos Santos Fernandes (JIRA)

Generate attributes for @Transient columns ------------------------------------------ Key: METAGEN-72 URL: http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-72 Project: Hibernate Metamodel Generator Issue Type: Improvement Components: processor Reporter: Adriano dos Santos Fernandes Assignee: Hardy Ferentschik Hibernate doesn't not generate metadata attributes for @Transient columns. They may be not interesting for criteria queries, but attributes may be used for general usage of entities across the application, for example, to construct screens. Please at least add an option to generate them. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2052) org.hibernate.pretty.MessageHelper.collectionInfoString tries to cast wrong object to String, causes ClassCastException

by Tree 'Huggy Bear' Hugger (JIRA)

org.hibernate.pretty.MessageHelper.collectionInfoString tries to cast wrong object to String, causes ClassCastException ----------------------------------------------------------------------------------------------------------------------- Key: HHH-2052 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2052 Project: Hibernate3 Type: Bug Reporter: Tree 'Huggy Bear' Hugger Attachments: bugtest.zip Debug level logging attempted by MessageHelper falls over when constructing a loggable string for a mapped collection on the main entity. Following the code in the stacktrace, I can see that MessageHelper expects the parent key for the collection relationship to be the primary key, but it is mapped to another field of a different type via a property-ref. Hence the ClassCastException below. The work around is to set logging to INFO or higher. I have also attached a pared-down zip with the maven 2 project containing the mappings and the unit test which fails. The following JIRA issue may be the same thing: http://opensource.atlassian.com/projects/hibernate/browse/ANN-298 The following messages on the Hib forum demonstrate other interest in this issue: http://forum.hibernate.org/viewtopic.php?t=949913 http://forum.hibernate.org/viewtopic.php?t=956778 http://forum.hibernate.org/viewtopic.php?t=962471 java.lang.ClassCastException: com.nomadsoft.cortex.domain.country.basic.BasicCountry at org.hibernate.type.StringType.toString(StringType.java:44) at org.hibernate.type.NullableType.toLoggableString(NullableType.java:168) at org.hibernate.pretty.MessageHelper.collectionInfoString(MessageHelper.java:284) at org.hibernate.loader.Loader.readCollectionElement(Loader.java:972) at org.hibernate.loader.Loader.readCollectionElements(Loader.java:635) at org.hibernate.loader.Loader.getRowFromResultSet(Loader.java:580) at org.hibernate.loader.Loader.doQuery(Loader.java:689) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:224) at org.hibernate.loader.Loader.loadEntity(Loader.java:1785) at org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:47) at org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:41) at org.hibernate.persister.entity.AbstractEntityPersister.load(AbstractEntityPersister.java:2730) at org.hibernate.event.def.DefaultLoadEventListener.loadFromDatasource(DefaultLoadEventListener.java:365) at org.hibernate.event.def.DefaultLoadEventListener.doLoad(DefaultLoadEventListener.java:346) at org.hibernate.event.def.DefaultLoadEventListener.load(DefaultLoadEventListener.java:123) at org.hibernate.event.def.DefaultLoadEventListener.proxyOrLoad(DefaultLoadEventListener.java:177) at org.hibernate.event.def.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:87) at org.hibernate.impl.SessionImpl.fireLoad(SessionImpl.java:862) at org.hibernate.impl.SessionImpl.get(SessionImpl.java:799) at org.hibernate.impl.SessionImpl.get(SessionImpl.java:792) at org.springframework.orm.hibernate3.HibernateTemplate$1.doInHibernate(HibernateTemplate.java:452) at org.springframework.orm.hibernate3.HibernateTemplate.execute(HibernateTemplate.java:366) at org.springframework.orm.hibernate3.HibernateTemplate.get(HibernateTemplate.java:446) at org.springframework.orm.hibernate3.HibernateTemplate.get(HibernateTemplate.java:440) at com.nomadsoft.cortex.infrastructure.hibernate.HibernateCountryRepository.getById(HibernateCountryRepository.java:26) at com.nomadsoft.cortex.domain.country.basic.BasicCountryService.getCountry(BasicCountryService.java:34) etc etc -- 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, 3 months

9
8
0 / 0

[Hibernate-JIRA] Created: (HHH-6190) Define JMX strategy

by Steve Ebersole (JIRA)

Define JMX strategy ------------------- Key: HHH-6190 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6190 Project: Hibernate Core Issue Type: Improvement Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 4.1.0 This encompasses building a SessionFactory as well as leveraging {{JmxService}} to expose management and monitoring capabilities. -- 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, 3 months

1
6
0 / 0

[Hibernate-JIRA] Created: (HHH-6034) Expose stats as Manageable service (jmx)

by Steve Ebersole (JIRA)

Expose stats as Manageable service (jmx) ---------------------------------------- Key: HHH-6034 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6034 Project: Hibernate Core Issue Type: Task Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 4.0.0.Alpha3 -- 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, 3 months

1
7
0 / 0

[Hibernate-JIRA] Created: (HHH-5984) Make JdbcServices Manageable

by Steve Ebersole (JIRA)

Make JdbcServices Manageable ---------------------------- Key: HHH-5984 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5984 Project: Hibernate Core Issue Type: Improvement Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 4.0.0.Alpha1 Make JdbcServices Manageable to expose the things we want configurable via JMX -- 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, 3 months

1
8
0 / 0

[Hibernate-JIRA] Created: (HHH-2515) Remove all documentation about HAR, it is deprecated

by Christian Bauer (JIRA)

Remove all documentation about HAR, it is deprecated ---------------------------------------------------- Key: HHH-2515 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2515 Project: Hibernate3 Type: Improvement Components: documentation Reporter: Christian Bauer Priority: Critical Clearly not one of the best ideas we ever had is the HAR deployment. It should now be considered deprecated (superseded by the EJB3/JPA deployment model) and any documentation about it should be removed. This includes JBoss AS user guides, wiki pages, etc. If you have any objects and think that HAR is a fantastic thing, raise them here. -- 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, 3 months

4
11
0 / 0

[Hibernate-JIRA] Created: (HHH-4550) query cache: Attention with configuring Update Timestamps Cache region: expired entries cause wrong result sets!

by Guenther Demetz (JIRA)

query cache: Attention with configuring Update Timestamps Cache region: expired entries cause wrong result sets! ---------------------------------------------------------------------------------------------------------------- Key: HHH-4550 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4550 Project: Hibernate Core Issue Type: Improvement Components: caching (L2) Affects Versions: 3.3.2 Environment: 3.3.2 GA Reporter: Guenther Demetz Priority: Trivial Attachments: TestCaseQuryCache.jar When using hibernate's query cache (hibernate.cache.use_query_cache), then it's of fundamental importance to configure the Update Timestamps cache region in a way that his entries survive longer than the cached result sets in the Query cache region. Otherwise queries could return wrong (obsolete) result sets (See attached testcase). This is because the current UpdateTimestampsCache#isUpToDate implementation considers a result-set also as up-to-date, if there are no update-timestamps cached for the interested spaces (tables) at all. It if therefore important to notice that: 1- The Update-Timestamps-Cache-Region elements max-size should be configured higher than the number of tables you have on the db-schema, in manner that he can remember/hold the last update-timestamp for each table. 2- If you use any other eviction policy in the Update-Timestamps-Cache-Region, then you must assure that cached result sets in the Query-cache-region are evicted before relevant update-timestamps are going to be evicted. This fact should be clearly documented somewhere. Thanks G.D. -- 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, 3 months

4
6
0 / 0

[Hibernate-JIRA] Created: (HHH-3892) Improve support for mapping SQL LONGVARCHAR and CLOB to Java String, SQL LONGVARBINARY and BLOB to Java byte[]

by Gail Badner (JIRA)

Improve support for mapping SQL LONGVARCHAR and CLOB to Java String, SQL LONGVARBINARY and BLOB to Java byte[] --------------------------------------------------------------------------------------------------------------- Key: HHH-3892 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3892 Project: Hibernate Core Issue Type: Improvement Components: core Reporter: Gail Badner Assignee: Gail Badner Fix For: 3.2.x, 3.3.x, 3.5 Property types will be provided to enable an application to process data for a java.sql.Types.LONGVARCHAR or java.sql.Types.CLOB column as a Java String. Hibernate will internally process the data as a streams. On a read, stream data will immediately be materialized into a Java string. text - property type to map java.sql.Types.LONGVARCHAR column data as a Java String (via org.hibernate.type.TextType); (NOTE: currently, org.hibernate.type.TextType incorrectly maps "text" to java.sql.Types.CLOB; this will be fixed by this issue and updated in database dialects) materialized_clob - property type to map java.sql.Types.CLOB column data as a Java String (via org.hibernate.type.MaterializedClobType); In addition, new property types will be provided to enable an application to process data for a java.sql.Types.LONGVARBINARY or java.sql.Types.BLOB column as Java byte[]. Hibernate will internally process the data as a streams. On a read, stream data will immediately be materialized into a Java byte[]. image - property type to map java.sql.Types.LONGVARBINARY column data as byte[] (via org.hibernate.type.ImageType); materialized_blob - property type to map java.sql.Types.BLOB column data as byte[] (via org.hibernate.type.MaterializedBlobType); -- 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, 3 months

3
6
0 / 0

[Hibernate-JIRA] Created: (HHH-4555) Support use of Envers with Auto-commit mode.

by Kevin Schmidt (JIRA)

Support use of Envers with Auto-commit mode. -------------------------------------------- Key: HHH-4555 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4555 Project: Hibernate Core Issue Type: New Feature Components: envers Affects Versions: 3.5.0-Beta-2 Environment: Hibernate 3.5.0-Beta-2 Reporter: Kevin Schmidt Currently Envers is designed so that it synchronizes with the currently running transaction in order to know when to commit the inserts into the Audit Tables. This is an effective strategy for ensuring that the audit information is only saved to the database if the Transactional Unit of Work which caused the audit data to be created is committed. This design creates a limitation on Envers such that it cannot persist audit information unless there is an active transaction. This effectively disables auditing for anyone modifying data using Hibernate outside of a Hibernate Transaction. Specifically, if you are using Autocommit = True and manually flushing the Hibernate Session then you cannot have any of your data audited using Envers. I am not that well versed with the design of Envers but was hoping this situation could be detected and avoided. Maybe the audit information could be synchronized on the flush event rather than when a transaction is committed to the database. -- 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, 3 months

3
11
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 July 2011