June 2012 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (OGM-22) Support Session#list and JP-QL queries

by Emmanuel Bernard (JIRA)

Support Session#list and JP-QL queries -------------------------------------- Key: OGM-22 URL: http://opensource.atlassian.com/projects/hibernate/browse/OGM-22 Project: Hibernate OGM Issue Type: New Feature Components: query Reporter: Emmanuel Bernard -- 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, 8 months

2
3
0 / 0

[Hibernate-JIRA] Created: (JPA-15) Criteria API based on MapKeyColumn is not working

by Edwin Dalorzo (JIRA)

Criteria API based on MapKeyColumn is not working ------------------------------------------------- Key: JPA-15 URL: http://opensource.atlassian.com/projects/hibernate/browse/JPA-15 Project: Java Persistence API Issue Type: Bug Environment: Hibernate 3.6.1 MySQL 5.0 Reporter: Edwin Dalorzo Attachments: log.txt, src.zip I defined an Employee entity having a map of phone numbers, where the key is the type of phone (home, office, mobile) and the value is the phone number as a String. @ElementCollection(fetch=FetchType.LAZY) @CollectionTable(name="emp_phone") @MapKeyColumn(name="phone_type") @Column(name="phone_num") private Map<String, String> phoneNumbers; Then I tried to write a Criteria API query using a map join, like this: CriteriaBuilder builder = entityManager.getCriteriaBuilder(); CriteriaQuery<Employee> criteria = builder.createQuery(Employee.class); Root<Employee> employeeRoot = criteria.from(Employee.class); criteria.select(employeeRoot); MapJoin<Employee, String, String> phoneRoot = employeeRoot.joinMap("phoneNumbers"); criteria.where(builder.equal(phoneRoot.key(), "HOME")); System.out.println(entityManager.createQuery(criteria).getResultList()); You get an NullPointerException java.lang.NullPointerException at org.hibernate.ejb.criteria.path.AbstractPathImpl.prepareAlias(AbstractPathImpl.java:246) at org.hibernate.ejb.criteria.path.AbstractPathImpl.render(AbstractPathImpl.java:253) at org.hibernate.ejb.criteria.predicate.ComparisonPredicate.render(ComparisonPredicate.java:173) at org.hibernate.ejb.criteria.QueryStructure.render(QueryStructure.java:258) at org.hibernate.ejb.criteria.CriteriaQueryImpl.render(CriteriaQueryImpl.java:340) at org.hibernate.ejb.criteria.CriteriaQueryCompiler.compile(CriteriaQueryCompiler.java:223) at org.hibernate.ejb.AbstractEntityManagerImpl.createQuery(AbstractEntityManagerImpl.java:441) at com.dalorzo.Main.main(Main.java:57) Exception in thread "main" java.lang.RuntimeException: java.lang.NullPointerException at com.dalorzo.Main.main(Main.java:64) Caused by: java.lang.NullPointerException at org.hibernate.ejb.criteria.path.AbstractPathImpl.prepareAlias(AbstractPathImpl.java:246) at org.hibernate.ejb.criteria.path.AbstractPathImpl.render(AbstractPathImpl.java:253) at org.hibernate.ejb.criteria.predicate.ComparisonPredicate.render(ComparisonPredicate.java:173) at org.hibernate.ejb.criteria.QueryStructure.render(QueryStructure.java:258) at org.hibernate.ejb.criteria.CriteriaQueryImpl.render(CriteriaQueryImpl.java:340) at org.hibernate.ejb.criteria.CriteriaQueryCompiler.compile(CriteriaQueryCompiler.java:223) at org.hibernate.ejb.AbstractEntityManagerImpl.createQuery(AbstractEntityManagerImpl.java:441) at com.dalorzo.Main.main(Main.java:57) If you change the query to filter on value instead of key, it works just fine criteria.where(builder.equal(phoneRoot.value(), "88750372")); I have attached a log with exceptions as well as the Employee entity and the Main class containing a main method. Also, the code in question runs perfectly fine in EclipseLink. -- 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, 8 months

6
8
0 / 0

[Hibernate-JIRA] (HHH-7385) upgrade to Gradle 1.0

by Strong Liu (JIRA)

13 years, 8 months

1
3
0 / 0

[Hibernate-JIRA] Created: (HHH-7305) NPE in LogicalConnectionImpl when multi tenancy is used without providing a release mode manually

by Christian kalkhoff (JIRA)

NPE in LogicalConnectionImpl when multi tenancy is used without providing a release mode manually ------------------------------------------------------------------------------------------------- Key: HHH-7305 URL: https://hibernate.onjira.com/browse/HHH-7305 Project: Hibernate ORM Issue Type: Bug Components: core Affects Versions: 4.1.3 Environment: cfg.setProperty(Environment.MULTI_TENANT, MultiTenancyStrategy.DATABASE.name()); Reporter: Christian kalkhoff Priority: Critical When multi tenancy is used and hibernate.connection.release_mode is not set, one gets a NPE in LogicalConnectionImpl because it accesses a (non-multi-tenancy)connection provider to determine the release mode. Stack trace: java.lang.NullPointerException at org.hibernate.engine.jdbc.internal.LogicalConnectionImpl.determineConnectionReleaseMode(LogicalConnectionImpl.java:119) at org.hibernate.engine.jdbc.internal.LogicalConnectionImpl.<init>(LogicalConnectionImpl.java:100) at org.hibernate.engine.jdbc.internal.LogicalConnectionImpl.<init>(LogicalConnectionImpl.java:82) at org.hibernate.engine.jdbc.internal.JdbcCoordinatorImpl.<init>(JdbcCoordinatorImpl.java:75) at org.hibernate.engine.transaction.internal.TransactionCoordinatorImpl.<init>(TransactionCoordinatorImpl.java:87) at org.hibernate.internal.SessionImpl.<init>(SessionImpl.java:249) at org.hibernate.internal.SessionFactoryImpl$SessionBuilderImpl.openSession(SessionFactoryImpl.java:1835) ... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

4
12
0 / 0

[Hibernate-JIRA] Created: (HHH-6608) @JoinColumns doesn't work inside an @Embedded member

by Joeri Hendrickx (JIRA)

@JoinColumns doesn't work inside an @Embedded member ---------------------------------------------------- Key: HHH-6608 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6608 Project: Hibernate Core Issue Type: Bug Components: annotations, metamodel Affects Versions: 4.0.0.CR1, 3.5.6 Environment: Version 3.5.6 and up, no DB Reporter: Joeri Hendrickx Attachments: hibernate-embedded-joincolumns.zip If you use multiple joincolumns on a @ManyToOne or @OneToOne field in an @Embedded class, hibernate will fail when building its metamodel with the following exception: Exception in thread "main" org.hibernate.MappingException: property [_model_MainEntity_embeddedEntity.referencedEntity] not found on entity [model.ReferencedEntity] at org.hibernate.mapping.PersistentClass.getRecursiveProperty(PersistentClass.java:379) at org.hibernate.cfg.annotations.TableBinder.bindFk(TableBinder.java:406) at org.hibernate.cfg.ToOneFkSecondPass.doSecondPass(ToOneFkSecondPass.java:111) at org.hibernate.cfg.AnnotationConfiguration.processEndOfQueue(AnnotationConfiguration.java:541) at org.hibernate.cfg.AnnotationConfiguration.processFkSecondPassInOrder(AnnotationConfiguration.java:523) at org.hibernate.cfg.AnnotationConfiguration.secondPassCompile(AnnotationConfiguration.java:380) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1377) at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:954) at model.Test.main(Test.java:12) Caused by: org.hibernate.MappingException: property [_model_MainEntity_embeddedEntity.referencedEntity] not found on entity [model.ReferencedEntity] at org.hibernate.mapping.PersistentClass.getRecursiveProperty(PersistentClass.java:425) at org.hibernate.mapping.PersistentClass.getRecursiveProperty(PersistentClass.java:376) ... 8 more A test case is included. Just run model. Test with the hibernate libraries in the classpath. I get the impression this is because of the dot in the generated property name. Hibernate generates a synthetic property, named after the FQN of the owning entity (with dots replaces by underscores) appended by and underscore and the name of the property. But properties inside of embedded objects are represented with a dot; when Hibernate later tries to retrieve the same property, it incorrectly interprets this dot as a delimiter, and will look for `_model_MainEntity_embeddedEntity` (in the example above) instead; which it will not find. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

4
5
0 / 0

[Hibernate-JIRA] Created: (HHH-7108) @TypeDef doesn't work for enums

by Michael Nascimento Santos (JIRA)

@TypeDef doesn't work for enums ------------------------------- Key: HHH-7108 URL: https://hibernate.onjira.com/browse/HHH-7108 Project: Hibernate ORM Issue Type: Bug Components: core Affects Versions: 4.1.0 Environment: hibernate-jpa-2.0-api:1.0.1-Final; hibernate-core:4.1.0.Final; hibernate-entitymanager:4.1.0.Final Reporter: Michael Nascimento Santos Priority: Critical @TypeDef is supposed to allow users to define standard types to be used for specific classes. However, due to a bug in implementation, it simply doesn't work for enums. Enums are implicitly handled by the JPA spec. However, if a @TypeDef is defined for a particular enum, it will never be picked up due to bug in org.hibernate.cfg.annotations.SimpleValueBinder . This class has a concept of a "explicitType", i.e., a type that was explicitly specified for a property. However, even if @EnumType is not used to annotate a property, method setType(XProperty,XClass) considers the property as annotated with it. Then, when fillSimpleValue() is called as part of second-pass compilation, the ternary in line 344 chooses org.hibernate.type.EnumType instead of the enum FQN, causing any @TypeDef to be ignored. This behaviour should be fixed by considering a non-annotated enum property as implicitly typed, not explicitly. Then, the resolution order should be changed to explicitType -> returnedClassName -> implicitType. This would preserve default, expected behaviour for regular enums, while allowing @TypeDef to be used for enums as well. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

5
7
0 / 0

[Hibernate-JIRA] Created: (HHH-2808) CLONE -Impossible to define caching for a subclass's collection in hibernate.cgf.xml

by Sebastien Blind (JIRA)

CLONE -Impossible to define caching for a subclass's collection in hibernate.cgf.xml ------------------------------------------------------------------------------------- Key: HHH-2808 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2808 Project: Hibernate3 Issue Type: Bug Components: caching (L2) Affects Versions: 3.2.5 Environment: Hibernate 3.2.5 Sybase Reporter: Sebastien Blind Basically, hibernate allows to define <cache usage="transactional"/> inside the subclass mapping, i.e. <subclass name="SubClass" extends="BaseClass" discriminator-value="xxx"> <bag name="subClassLinks" lazy="false" inverse="true" batch-size="100"> <cache usage="transactional" region="xxx"/> <key column="xxx" not-null="true"/> <one-to-many class="xxx"/> </bag> <join table="xxx"> </join> </subclass> but it's not allowed to do the same using <collection-cache collection="subClass.myCollection" region="xxx" usage="transactional"/>. It throws: Exception in thread "main" org.hibernate.MappingException: Cannot cache an unknown collection: subClass.myCollection at org.hibernate.cfg.Configuration.setCollectionCacheConcurrencyStrategy(Configuration.java:1984) at org.hibernate.cfg.Configuration.parseSessionFactory(Configuration.java:1568) at org.hibernate.cfg.Configuration.doConfigure(Configuration.java:1534) at org.hibernate.cfg.Configuration.doConfigure(Configuration.java:1508) at org.hibernate.cfg.Configuration.configure(Configuration.java:1428) -- 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, 8 months

6
10
0 / 0

[Hibernate-JIRA] Created: (OGM-21) Support EntityManager#createQuery(String)

by Emmanuel Bernard (JIRA)

Support EntityManager#createQuery(String) ----------------------------------------- Key: OGM-21 URL: http://opensource.atlassian.com/projects/hibernate/browse/OGM-21 Project: Hibernate OGM Issue Type: New Feature Components: query Reporter: Emmanuel Bernard -- 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, 8 months

2
1
0 / 0

[Hibernate-JIRA] Created: (OGM-20) Integrate the JP-QL to HSQuery / Lucene module

by Emmanuel Bernard (JIRA)

Integrate the JP-QL to HSQuery / Lucene module ---------------------------------------------- Key: OGM-20 URL: http://opensource.atlassian.com/projects/hibernate/browse/OGM-20 Project: Hibernate OGM Issue Type: Task Reporter: Emmanuel Bernard Assignee: Sanne Grinovero -- 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, 8 months

2
2
0 / 0

[Hibernate-JIRA] Created: (OGM-173) Only load the necessary properties from MongoDB

by Emmanuel Bernard (JIRA)

Only load the necessary properties from MongoDB ----------------------------------------------- Key: OGM-173 URL: https://hibernate.onjira.com/browse/OGM-173 Project: Hibernate OGM Issue Type: Improvement Components: datastore Reporter: Emmanuel Bernard Today we load the whole MongoDB document. It can contain the association information wich might not be useful (lazy collections) and it can contain properties used by other apps but not mapped by Hibernate OGM. It would be better to explicitly select the list of properties we are interested in. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

3
6
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 June 2012