April 2011 - hibernate-issues - Jboss List Archives

[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, 2 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, 2 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, 2 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, 2 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, 2 months

3
11
0 / 0

[Hibernate-JIRA] Created: (METAGEN-57) Attributes are not generated for EmbeddedId and collections when the mapping is defined in orm.xml mapping files

by Rolf Thunbo (JIRA)

Attributes are not generated for EmbeddedId and collections when the mapping is defined in orm.xml mapping files ---------------------------------------------------------------------------------------------------------------- Key: METAGEN-57 URL: http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-57 Project: Hibernate Metamodel Generator Issue Type: Bug Affects Versions: 1.1.0.Final Reporter: Rolf Thunbo Assignee: Hardy Ferentschik To fix the collection problem l. 196 of XmlMetaEntity (in the getCollectionTypes method): if ( expectedElementKind.equals( elem.getKind() ) ) { should be replaced by if ( ! expectedElementKind.equals( elem.getKind() ) ) { To fix the EmbeddedId problem the following code should be inserted at l. 332 of XmlMetaEntity (in the parseAttributes method): if ( attributes.getEmbeddedId() != null) { EmbeddedId embeddedId = attributes.getEmbeddedId(); ElementKind elementKind = getElementKind( embeddedId.getAccess() ); String type = getType( embeddedId.getName(), null, elementKind ); if ( type != null ) { attribute = new XmlMetaSingleAttribute( this, embeddedId.getName(), type ); members.add( attribute ); } } -- 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: (METAGEN-53) Remove dependency of JPA API classes to simplify setup

by Max Rydahl Andersen (JIRA)

Remove dependency of JPA API classes to simplify setup ------------------------------------------------------ Key: METAGEN-53 URL: http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-53 Project: Hibernate Metamodel Generator Issue Type: New Feature Components: processor Reporter: Max Rydahl Andersen Assignee: Hardy Ferentschik Even though the annotation processor is dependent on knowing the name of JPA API classes it shouldn't actually require access to the concrete classes. Removing this would make it one less dependency to have to configure/setup for annotation processor path. -- 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
2
0 / 0

[Hibernate-JIRA] Created: (METAGEN-52) Remove dependency to JPA jar/classes

by Hardy Ferentschik (JIRA)

Remove dependency to JPA jar/classes ------------------------------------ Key: METAGEN-52 URL: http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-52 Project: Hibernate Metamodel Generator Issue Type: Improvement Components: processor Affects Versions: 1.1.1.Final Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 1.x It should be possible to remove all dependencies to JPA classes in the annotation processor. The advantage would be that when configuring the processor one does not have to specify a processor classpath. On the other hand, when using the processor you will always need a JPA jar anyways since otherwise your code won't compile. So the only benefit is a slightly "easier" configuration of the processor. See also https://issues.jboss.org/browse/WELD-835 -- 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

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3383) QueryKey is storing references to entities instead of identifiers

by Manuel Dominguez Sarmiento (JIRA)

QueryKey is storing references to entities instead of identifiers ----------------------------------------------------------------- Key: HHH-3383 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3383 Project: Hibernate3 Issue Type: Improvement Components: caching (L2) Affects Versions: 3.3.0.CR1 Environment: ehcache 1.5.0b2 Reporter: Manuel Dominguez Sarmiento Context: query caching Hibernate is storing full entity references when building QueryKeys and the query has restrictions which reference entities. This happens either with Criteria or HQL queries. Although this is not incorrect, when the referenced entities reference in turn "heavy" object graphs, this causes a very significant memory usage increase, since references to detached entities will remain in the cache. This is even more evident when using disk persistence with ehcache, since the full object graphs are serialized to disk. This could be easily improved (correct me if I'm wrong) by storing ONLY entity identifiers in the QueryKey instead of full entities, since all the query really needs is the identifier property. The memory usage would decrease dramatically. So far the workaround we've found is explicitly using restrictions that reference identifiers instead of properties in HQL queries, however this is not particularly elegant, and still leaves open the issue with Criteria queries. The same cannot be done without criteria.createCriteria() which generates an unnecessary join in most cases. -- 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
10
0 / 0

[Hibernate-JIRA] Created: (METAGEN-60) Embedded class implementing List interface leads to missing identifier

by Jan Stolze (JIRA)

Embedded class implementing List interface leads to missing identifier ---------------------------------------------------------------------- Key: METAGEN-60 URL: http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-60 Project: Hibernate Metamodel Generator Issue Type: Bug Components: processor Affects Versions: 1.1.1.Final Environment: Hibernate 3.6.1 final Reporter: Jan Stolze Assignee: Hardy Ferentschik Attachments: ListOfString2.java, ListOfString2_.java I have an Embedded class which implements the java.util.List interface when running the annotation processor for the JPA meta model it fails with the message Note: Determining access type for ListOfString2 [javac] ListOfString2_.java:9: <identifier> expected [javac] public static volatile SingularAttribute<ListOfString2, String> ; when looking into the generated class the message makes sense because the identifier is indeed missing, question is how is that possible. See attachment for Embedded object and generated output of the meta model class. -- 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
8
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 April 2011