August 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (METAGEN-70) BasicAttributeVistor doesn't recognize subclasses of java.io.Serializeable as Attributes.

by kk (JIRA)

BasicAttributeVistor doesn't recognize subclasses of java.io.Serializeable as Attributes. ----------------------------------------------------------------------------------------- Key: METAGEN-70 URL: http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-70 Project: Hibernate Metamodel Generator Issue Type: Bug Components: processor Affects Versions: 1.1.1.Final Reporter: kk Assignee: Hardy Ferentschik Situation: Interface 'UnitPersistentValueIF' extends 'PersistentValueIF'. Interface 'PersistentValueIF' extends 'java.io.Serializable'. Result: The annotationprocessor creates attributes for element 'PersistentValueIF' The annotationprocessor doesn't create attributes for element 'UnitPersistentValueIF' Expected result: The annotationprocessor creates for both 'PersistentValueIF' and 'UnitPersistentValueIF' the attributes. I have debugged the annotationprocessor and this could be the solution: In BasicAttributeVisitor.java in method visitDeclared(DeclaredType declaredType, Element element) there is the following code: if ( "java.io.Serializable".equals( interfaceElement.getQualifiedName().toString() ) ) { This code should also take into account its superclasses (or interfaces). Can this be done with 'java.lang.model' ? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

2
9
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, 3 months

2
5
0 / 0

[Hibernate-JIRA] Created: (METAGEN-66) XML Based Mapping of Embeddets in Mapped-Superclass is ignored

by Ralph Engelmann (JIRA)

XML Based Mapping of Embeddets in Mapped-Superclass is ignored -------------------------------------------------------------- Key: METAGEN-66 URL: http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-66 Project: Hibernate Metamodel Generator Issue Type: Bug Affects Versions: 1.1.1.Final Environment: Meta model generator for Hibernate (Version 1.1.1-Final), Hiberante 3.6.1.Final, Spring 3.0 Reporter: Ralph Engelmann Assignee: Hardy Ferentschik I use a Mapped Superclass, which refer to an (generic) Embeddded. Because this class is located in an different jar I needto map this class explicit in XML. But the Hibernate Model Generator does not create an field in the Meta Model of the Mapped Superclass that represent the Embedded. See the code for illustration. {code:title=Mapped Superclass(BusinessEntity<T>)} public abstract class BusinessEntity<T extends Serializable> implements Serializable { private Long id; private BusinessId<T> businessId; ... } {code} {code:title=Generic Embedded (BusinessId<T>)} public class BusinessId<T> implements Serializable { private long businessId; ... } {code} {code:title=orm.xml} <?xml version="1.0" encoding="UTF-8"?> <entity-mappings xmlns="http://java.sun.com/xml/ns/persistence/orm" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence/orm http://java.sun.com/xml/ns/persistence/orm_2_0.xsd" version="2.0"> <mapped-superclass class="BusinessEntity" access="FIELD"> <attributes> <id name="id"> <column nullable="false"/> <generated-value strategy="AUTO"/> </id> <embedded name="businessId"/> </attributes> </mapped-superclass> <embeddable class="BusinessId" access="FIELD"> <attributes> <basic name="businessId"> <column nullable="false" unique="true"/> </basic> </attributes> </embeddable> </entity-mappings> {code} {code:title=Generated Meta Model (BusinessEntity_)} import javax.persistence.metamodel.SingularAttribute; import javax.persistence.metamodel.StaticMetamodel; @StaticMetamodel(BusinessEntity.class) public abstract class BusinessEntity_ { public static volatile SingularAttribute<BusinessEntity, Long> id; } {code} {code:title=Generated Meta Model (BusinessId_)} import javax.persistence.metamodel.SingularAttribute; import javax.persistence.metamodel.StaticMetamodel; @StaticMetamodel(BusinessId.class) public abstract class BusinessId_ { public static volatile SingularAttribute<BusinessId, Long> businessId; } {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, 3 months

2
4
0 / 0

[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

14 years, 3 months

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

14 years, 3 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, 3 months

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

14 years, 3 months

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

14 years, 3 months

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

14 years, 3 months

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

14 years, 3 months

2
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 August 2011