December 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (METAGEN-67) @ManyToOne fields in a @MappedSuperclass are not taken into account

by Matthieu Bertin (JIRA)

@ManyToOne fields in a @MappedSuperclass are not taken into account ------------------------------------------------------------------- Key: METAGEN-67 URL: http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-67 Project: Hibernate Metamodel Generator Issue Type: Bug Affects Versions: 1.1.1.Final Environment: Hibernate 3.6.1 Reporter: Matthieu Bertin Assignee: Hardy Ferentschik all the @manytoone fields in a mappedsuperclass are absent in the generated metamodel. -- 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

13 years

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

13 years

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

13 years

1
2
0 / 0

[Hibernate-JIRA] Created: (METAGEN-62) SortedSet attributes are not included in metamodel

by Patrice Blanchardie (JIRA)

SortedSet attributes are not included in metamodel -------------------------------------------------- Key: METAGEN-62 URL: http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-62 Project: Hibernate Metamodel Generator Issue Type: Improvement Components: processor Affects Versions: 1.1.1.Final Reporter: Patrice Blanchardie Assignee: Hardy Ferentschik SortedSet collections (with @Sort etc.) are not included in generated metamodel. Is it the wanted behavior, even if collections are annotated with @OneToMany/@ManyToMany? It produces the following error: "Unable to locate static metamodel field ..." -- 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

13 years

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-6512) Setup Oracle integration tests

by Karel Maesen (JIRA)

Setup Oracle integration tests ------------------------------ Key: HHH-6512 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6512 Project: Hibernate Core Issue Type: Sub-task Reporter: Karel Maesen -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

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

13 years

6
10
0 / 0

[Hibernate-JIRA] Created: (METAGEN-64) Normal class in hierarchy breaks metamodel

by Robin Sander (JIRA)

Normal class in hierarchy breaks metamodel ------------------------------------------ Key: METAGEN-64 URL: http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-64 Project: Hibernate Metamodel Generator Issue Type: Bug Affects Versions: 1.1.1.Final Environment: HIbernate 3.6.3.Final, PostgreSQL 8.4, Java 6 Reporter: Robin Sander Assignee: Hardy Ferentschik Priority: Minor If an entity class extends a normal class which in turn extends another entity or a mapped superclass the generated meta model doesn't reflect this hierarchy. -- 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

13 years

2
11
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

13 years

2
8
0 / 0

[Hibernate-JIRA] Created: (METAGEN-58) Subsequent processing rounds are trying to reprocess Entities that are already processed, this causes an error.

by Viet Trinh (JIRA)

Subsequent processing rounds are trying to reprocess Entities that are already processed, this causes an error. --------------------------------------------------------------------------------------------------------------- Key: METAGEN-58 URL: http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-58 Project: Hibernate Metamodel Generator Issue Type: Bug Components: processor Affects Versions: 1.1.1.Final Environment: jdk1.6.0_23, Eclipse 3.6, Maven 2, Hibernate version 3.6.1.Final, MS SQL 2005. Reporter: Viet Trinh Assignee: Hardy Ferentschik Priority: Minor I have an entity named "Car" and another processor that creates another entity name "CarAudit". After the first round, the class "Car_" and class "CarAudit" are created, therefore causing a subsequent round of processing since "CarAudit" is marked with @Entity. However, the second round fails with the following error: "diagnostic error: Problem with Filer: Attempt to recreate a file for type com.example.Car_" This is due to not clearing the "metaEntities" list from the context object after every round. Each processing round will use the same processor and context object and try to create all of the meta entries listed in the context during each round. My proposed solution is to clear the metaEntities list from the context object after each round of processing. Sorry, I do not have a test case for this right now. -- 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

13 years

2
4
0 / 0

[Hibernate-JIRA] Created: (METAGEN-50) Suppress Warnings

by Stephan Bublava (JIRA)

Suppress Warnings ----------------- Key: METAGEN-50 URL: http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-50 Project: Hibernate Metamodel Generator Issue Type: Improvement Components: processor Affects Versions: 1.1.1.Final Reporter: Stephan Bublava Assignee: Hardy Ferentschik Priority: Minor Please consider adding a @SuppressWarnings("all") annotation to the generated classes. Warnings in generated code are not helpful. In my case the warnings (driven by IDE settings) are caused by: 1) Entities marked as @Deprecated. 2) A custom Hibernate user type that maps a numeric SQL type into an EnumSet<T>. The generated SingularAttribute does not preserve the type of the set. -- 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

13 years

3
6
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues December 2011