March 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-5051) JPA 2 Criteria Query with Object as Parameter not Working

by Guido Müller (JIRA)

JPA 2 Criteria Query with Object as Parameter not Working --------------------------------------------------------- Key: HHH-5051 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5051 Project: Hibernate Core Issue Type: Bug Components: entity-manager Affects Versions: 3.5.0-CR-2 Reporter: Guido Müller Priority: Blocker The problem is with this scenario: 2 Entity classes A and B We have a 1:N relation between A (N) and B (1) This test fails: I get one instance of B with the entity manager find method. I query the database with JPA 2 query to get a list of all instances of A that have the many-to-one property equals the instance got from the 1st step. Code: EntityManager em = ... B b = em.find(B.class, 1L); CriteriaBuilder cb = em.getCriteriaBuilder(); CriteriaQuery<A> q = cb.createQuery(A.class); Root<A> p = q.from(A.class); q.select(p).where(cb.equal(p.get(A_.b), b)); List<A> l = em.createQuery(q).getResultList(); em.close(); This does not work but it should. It works properly with EclipseLink. In Hibernate I get this to work when I provide b.getId() as Parameter. But this is not correct! -- 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
7
0 / 0

[Hibernate-JIRA] Created: (HHH-4955) java persistence not bundled with 3.5.0-CR-2

by Daniel Padwa (JIRA)

java persistence not bundled with 3.5.0-CR-2 -------------------------------------------- Key: HHH-4955 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4955 Project: Hibernate Core Issue Type: Bug Components: build Affects Versions: 3.5.0-CR-2 Environment: Hibernate 3.5.0-CR-2 Reporter: Daniel Padwa Upgrading from Annotations 3.4 to the unified 3.5 core, I no longer get the ejb3-persistence library in the download. Even worse, the ejb3-persistence.jar that shipped with Annotation 3.4 does not work with 3.5.0-CR2 - it is missing the class javax.persistence.Cacheable -- 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
9
0 / 0

[Hibernate-JIRA] Created: (HHH-4965) Bug in org.hibernate.ejb.QueryImpl

by jean-claude cote (JIRA)

Bug in org.hibernate.ejb.QueryImpl ---------------------------------- Key: HHH-4965 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4965 Project: Hibernate Core Issue Type: Bug Components: entity-manager Affects Versions: 3.5.0-CR-1 Reporter: jean-claude cote Priority: Minor Emmanuel There seems to be a bug in the QueryImpl class in the method extractParameterInfo() Here's what I've done: I create an equal predicate using a Path to House.address and a Address value. @Entity class House { @Type(type="jc.AddressUserType") @Columns(columns={@Column(name="address")}) Address address; In the extractParameterInfo() method there is a loop that gets the javaType from a namedParameterTypeRedefinition. It gets the javaType (Address.class) then since it is not null tries to find the hibernate Type using the TypeFactory.heuristicType() method. But given a javaType this will only work for strings, int, double etc. What is passed in is an Address not an AddressUserType. The huristicType actually returns an hibernate SerializableType and resets the descriptor which was correct in the first place. I've fix this for myself my just commenting out the call to resetExpectedType but there must be a good reason why this call is made there correct? Thanks Jean-Claude @SuppressWarnings({ "unchecked", "RedundantCast" }) private void extractParameterInfo(Map<String,Class> namedParameterTypeRedefinition) { if ( ! AbstractQueryImpl.class.isInstance( query ) ) { throw new IllegalStateException( "Unknown query type for parameter extraction" ); } HashSet<Parameter<?>> parameters = new HashSet<Parameter<?>>(); AbstractQueryImpl queryImpl = AbstractQueryImpl.class.cast( query ); // extract named params for ( String name : (Set<String>) queryImpl.getParameterMetadata().getNamedParameterNames() ) { final NamedParameterDescriptor descriptor = queryImpl.getParameterMetadata().getNamedParameterDescriptor( name ); Class javaType = namedParameterTypeRedefinition.get( name ); if ( javaType != null ) { descriptor.resetExpectedType( TypeFactory.heuristicType( javaType.getName() ) ); } else if ( descriptor.getExpectedType() != null ) { javaType = descriptor.getExpectedType().getReturnedClass(); } final ParameterImpl parameter = new ParameterImpl( name, javaType ); parameters.add( parameter ); if ( descriptor.isJpaStyle() ) { if ( jpaPositionalIndices == null ) { jpaPositionalIndices = new HashSet<Integer>(); } jpaPositionalIndices.add( Integer.valueOf( name ) ); } } -- 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
12
0 / 0

[Hibernate-JIRA] Created: (HHH-4077) Misuse of NamingStrategy and logical column names in HbmBinder

by Emmanuel Bernard (JIRA)

Misuse of NamingStrategy and logical column names in HbmBinder -------------------------------------------------------------- Key: HHH-4077 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4077 Project: Hibernate Core Issue Type: Bug Components: metamodel Affects Versions: 3.3.2 Reporter: Emmanuel Bernard Assignee: Emmanuel Bernard Fix For: 3.5 -- 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
10
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-406) Removing cyclic reference between JMSBackendProcessor and JMSBackendProcessorFactory

by Amin Mohammed-Coleman (JIRA)

Removing cyclic reference between JMSBackendProcessor and JMSBackendProcessorFactory ------------------------------------------------------------------------------------ Key: HSEARCH-406 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-406 Project: Hibernate Search Issue Type: Improvement Components: engine Affects Versions: 3.1.1.GA Environment: Mac OS 10.6 Reporter: Amin Mohammed-Coleman Priority: Minor Attachments: JMS.patch The patch provided removes the cyclic reference between JMSBackendProcessor and JMSBackendProcessorFactory. The patch also includes: 1) Validation in the initialize method of JMSBackendProcessorFactory to check whether connection factory and queue property is included 2) Created a JMSBackendProcessorParameter which encapsulates all the necessary info for JMSBackendProcessor 3) Updated JMSBackendProcessor to include transacted parameter -- 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: (HSEARCH-468) Refactor build to have a module setup

by Hardy Ferentschik (JIRA)

Refactor build to have a module setup ------------------------------------- Key: HSEARCH-468 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-468 Project: Hibernate Search Issue Type: Task Components: build Affects Versions: 3.2.0.Beta1 Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 3.2.0.Beta2 Right now I can see the following modules * core * testing * archetype Later on we can add modules for * infinispan and maybe other directory provider It would be nice to simplify the dependencies by getting rid of the profiles w/ and w/o optional dependencies. -- 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
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-320) Hibernate Search conflicts with Spring's class path scanning

by Paul Middelkoop (JIRA)

Hibernate Search conflicts with Spring's class path scanning ------------------------------------------------------------ Key: HSEARCH-320 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-320 Project: Hibernate Search Issue Type: Bug Affects Versions: 3.1.0.GA, 3.1.0.CR1 Reporter: Paul Middelkoop Hibernate Search conflicts with Spring's class path scanning. When Hibernate Search is on the classpath Spring throws an exception while reading annotation metadata. 3.1.0 Beta1 and 3.0.x versions had no problems. Stacktrace: Caused by: java.lang.ArrayIndexOutOfBoundsException: 50432 at org.springframework.asm.ClassReader.readUTF8(Unknown Source) at org.springframework.asm.ClassReader.accept(Unknown Source) at org.springframework.asm.ClassReader.accept(Unknown Source) at org.springframework.core.type.classreading.SimpleMetadataReader.getAnnotationMetadata(SimpleMetadataReader.java:55) at org.springframework.core.type.filter.AnnotationTypeFilter.matchSelf(AnnotationTypeFilter.java:68) at org.springframework.core.type.filter.AbstractTypeHierarchyTraversingFilter.match(AbstractTypeHierarchyTraversingFilter.java:55) at org.springframework.context.annotation.ClassPathScanningCandidateComponentProvider.isCandidateComponent(ClassPathScanningCandidateComponentProvider.java:224) at org.springframework.context.annotation.ClassPathScanningCandidateComponentProvider.findCandidateComponents(ClassPathScanningCandidateComponentProvider.java:182) at org.springframework.context.annotation.ClassPathBeanDefinitionScanner.doScan(ClassPathBeanDefinitionScanner.java:201) at org.springframework.context.annotation.ComponentScanBeanDefinitionParser.parse(ComponentScanBeanDefinitionParser.java:85) at org.springframework.beans.factory.xml.NamespaceHandlerSupport.parse(NamespaceHandlerSupport.java:69) at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1255) at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1245) at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.parseBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:135) at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.registerBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:92) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.registerBeanDefinitions(XmlBeanDefinitionReader.java:507) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:398) -- 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

5
18
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-277) Adding Lucene Score

by Ulrich Vachon (JIRA)

Adding Lucene Score ------------------- Key: HSEARCH-277 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-277 Project: Hibernate Search Issue Type: Improvement Reporter: Ulrich Vachon Priority: Minor Hello, Is it plans to add implicitly the score to bean via an annotation for example? In my bean, if I have a annoted property or method like : @Score private float score; HS will inject the score result after the query in my bean. Thank you, Ulrich -- 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
4
0 / 0

[Hibernate-JIRA] Created: (HHH-4864) "Cannot read files twice on NativeScanner" exception when using multiple persistence.xml

by Bouiaw (JIRA)

"Cannot read files twice on NativeScanner" exception when using multiple persistence.xml ---------------------------------------------------------------------------------------- Key: HHH-4864 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4864 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.0-Beta-3 Reporter: Bouiaw When subclassing DefaultPersistenceUnitManager as described in http://ancientprogramming.blogspot.com/2007/05/multiple-persistencexml-fi... in order to have my entities in different jars, Hibernate 3.5-Beta3 throw the following exception (it worked with previous version of Hibernate) : java.lang.RuntimeException: error trying to scan <jar-file>: file:/Users/bouiaw/resthub/resthub-core/target/classes/ at org.hibernate.ejb.Ejb3Configuration.scanForClasses(Ejb3Configuration.java:700) at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:465) at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:165) at org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean.createNativeEntityManagerFactory(LocalContainerEntityManagerFactoryBean.java:225) at org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.afterPropertiesSet(AbstractEntityManagerFactoryBean.java:288) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1457) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1397) ... 51 more Caused by: org.hibernate.AssertionFailure: Cannot read files twice on NativeScanner at org.hibernate.ejb.packaging.NativeScanner.getFilesInJar(NativeScanner.java:168) at org.hibernate.ejb.Ejb3Configuration.addScannedEntries(Ejb3Configuration.java:393) at org.hibernate.ejb.Ejb3Configuration.scanForClasses(Ejb3Configuration.java:697) ... 57 more -- 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

5
7
0 / 0

[Hibernate-JIRA] Created: (HHH-3543) method org.hibernate.transaction.JDBCTransaction.notifyLocalSynchsBeforeTransactionCompletion "swallows" all exceptions occured inside it

by Roman (JIRA)

method org.hibernate.transaction.JDBCTransaction.notifyLocalSynchsBeforeTransactionCompletion "swallows" all exceptions occured inside it ----------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-3543 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3543 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1 Environment: MS Windows XP SP2, JDK 1.6.8, Eclipse 3.2.0 Reporter: Roman When using JBoss Envers any exceptions occured during saving data into version tables are swallowed by code block in class org.hibernate.transaction.JDBCTransaction (line 273): try { sync.beforeCompletion(); } catch (Throwable t) { log.error("exception calling user Synchronization", t); } Thereby, any exceptions occured in sync.beforeCompletion() will only be shown in log, but will not have any effect on application functionality So I have such behaviour: 1. Entity changes are saved in database by hibernate 2. Version tables for entities are empty, because, for example, of invalid column names 3. Transaction commits successfully. -- 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

5
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues March 2010