August 2009 - hibernate-issues - Jboss List Archives

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

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

5
7
0 / 0

[Hibernate-JIRA] Created: (HHH-2809) dialect changes: limit string

by Anthony Patricio (JIRA)

dialect changes: limit string ----------------------------- Key: HHH-2809 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2809 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.3 Reporter: Anthony Patricio Attachments: IngresDialect.svndiff32 In Ingres we use "SELECT FIRST $n col1,... FROM ..." to limit the resultset. The old dialect replaces the first 6 chars of the select statement with "SELECT FIRST $n". When running our partner application, hibernate has put 2 or 3 blanks at the begining of the query, which causes an error, of course. Patch attached -- 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, 9 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3962) Ingres Hibernate dialect for EAP 4.3.0 GA CP04

by Enrico Schenk (JIRA)

Ingres Hibernate dialect for EAP 4.3.0 GA CP04 ---------------------------------------------- Key: HHH-3962 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3962 Project: Hibernate Core Issue Type: Improvement Components: core Affects Versions: 3.2.4.sp1 Environment: Hibernate Core 3.2.4.SP1 CP07, Ingres 9.2.0 Reporter: Enrico Schenk Priority: Minor Attachments: IngresDialect.java This is the Ingres dialect that was used for the EAP 4.3.0 GA CP04 tests. It's based on the latest dialect from the trunk contains changes for the functions current_time, current_timestamp and current_date. The dialect also overrides the method getForUpdateString() to disable the use of "SELECT...FOR UPDATE" statements. -- 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, 9 months

5
10
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-386) In a Transaction, Delete on unindexed entities referenced by indexed entities with ContainedIn throw LazyInitializationException

by Grégoire Rolland (JIRA)

In a Transaction, Delete on unindexed entities referenced by indexed entities with ContainedIn throw LazyInitializationException -------------------------------------------------------------------------------------------------------------------------------- Key: HSEARCH-386 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-386 Project: Hibernate Search Issue Type: Bug Affects Versions: 3.1.1.GA, 3.1.0.GA Environment: Hibernate 3.3.1.GA, PostgreSQL 8.3 Reporter: Grégoire Rolland Priority: Critical Attachments: hsearch.tar.gz Delete on unindexed entities referenced by indexed entities with ContainedIn annotation failed. On PostCommit Transaction, I get a LazyInitializationException on the collection with the ContainedIn annotation. I upload a test case to reproduce this, run the Boot class. 1/ Entity2 is not lacking @DocumentId, I read the doc again and again (my english is very poor, but ...) : "In fact since the 3.1.0 release of Hibernate Search @DocumentId is optional in the case where an @Id annotation exists." 2/ Entity2 is not lacking @IndexedEmbedded, see the "entity1" association. 3/ From Hibernate Entity Manager Doc : "In an EXTENDED persistence context, all read only operations of the entity manager can be executed outside a transaction (find(), getReference(), refresh(), and read queries). Some modifications operations can be executed outside a transaction, but they are queued until the persistence context join a transaction. This is the case of persist(), merge(), remove(). Some operations cannot be called outside a transaction: flush(), lock(), and update/delete queries.". This is the case of the attached test. I attach a second testcase with all the operation in a transaction, the result is the same. 4/ I check 3.1.1-GA, the problem occurs alway. 5/ All the operation are in a transaction. Please read and run my testcase and if I missuse hibernate say me where. I can't reopen the bug HSEARCH-342, I open a new bug because the resolution of the bug HSEARCH-178 don't resolve this problem. Thank you. -- 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, 9 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-2295) entity-name attribute's syntax not clearly documented

by Jeremy Michael Crosbie (JIRA)

entity-name attribute's syntax not clearly documented ----------------------------------------------------- Key: HHH-2295 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2295 Project: Hibernate3 Type: Bug Components: documentation Versions: 3.2.1 Environment: Windows XP/JDK 1.5/HypersonicSQL Reporter: Jeremy Michael Crosbie Priority: Minor Attachments: Group.hbm.xml Setting entity-name to a value containing a hyphen, in my case 'lender-group' causes odd behaviors seemingly only when calling get() or load(). Also in my case I am mapping a class to two different tables (attached). The first mapping has an entity name with a hyphen, the other does not. When I call load *after committing a transaction where a new entity is persisted* I get an exception (see below). The exception complains of a column called "LENDER" not existing. But once I change the entity-name to something like 'lendergroup' the problem goes away. Interestingly, the missing column complained about is the text before the hyphen, so if I name the entity 'lndr-group' it complains of a column name 'LNDR' not existing. It almost appears if this format is assuming some sort of discriminator, but the online docs are terse when it comes to describing the entity-name field. Exception: org.hibernate.exception.SQLGrammarException: could not load an entity: [lender-group#G9] at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:67) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) at org.hibernate.loader.Loader.loadEntity(Loader.java:1799) at org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:47) at org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:41) at org.hibernate.persister.entity.AbstractEntityPersister.load(AbstractEntityPersister.java:2730) at org.hibernate.event.def.DefaultLoadEventListener.loadFromDatasource(DefaultLoadEventListener.java:365) at org.hibernate.event.def.DefaultLoadEventListener.doLoad(DefaultLoadEventListener.java:346) at org.hibernate.event.def.DefaultLoadEventListener.load(DefaultLoadEventListener.java:123) at org.hibernate.event.def.DefaultLoadEventListener.proxyOrLoad(DefaultLoadEventListener.java:177) at org.hibernate.event.def.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:87) at org.hibernate.impl.SessionImpl.fireLoad(SessionImpl.java:862) at org.hibernate.impl.SessionImpl.get(SessionImpl.java:799) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.hibernate.context.ThreadLocalSessionContext$TransactionProtectionWrapper.invoke(ThreadLocalSessionContext.java:301) at $Proxy0.get(Unknown Source) at com.fares.mtrac.group.GroupDaoImpl.findById(GroupDaoImpl.java:148) at com.fares.mtrac.group.GroupDaoImplTest.testFindByIdStringCompanyType(GroupDaoImplTest.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at junit.framework.TestCase.runTest(TestCase.java:164) at junit.framework.TestCase.runBare(TestCase.java:130) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:120) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:128) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) Caused by: java.sql.SQLException: Column not found: LENDER in statement [select lender-gro0_.group_cd as group1_48_0_, lender-gro0_.group_nm as group2_48_0_, lender-gro0_.user_nm as user3_48_0_ from lender_group_name lender-gro0_ where lender-gro0_.group_cd=?] at org.hsqldb.jdbc.Util.throwError(Unknown Source) at org.hsqldb.jdbc.jdbcPreparedStatement.<init>(Unknown Source) at org.hsqldb.jdbc.jdbcConnection.prepareStatement(Unknown Source) at org.hibernate.jdbc.AbstractBatcher.getPreparedStatement(AbstractBatcher.java:442) at org.hibernate.jdbc.AbstractBatcher.getPreparedStatement(AbstractBatcher.java:368) at org.hibernate.jdbc.AbstractBatcher.prepareQueryStatement(AbstractBatcher.java:105) at org.hibernate.loader.Loader.prepareQueryStatement(Loader.java:1561) at org.hibernate.loader.Loader.doQuery(Loader.java:661) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:224) at org.hibernate.loader.Loader.loadEntity(Loader.java:1785) ... 36 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, 9 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-331) Verify sorting behaviour for DoubleBridge

by Sanne Grinovero (JIRA)

Verify sorting behaviour for DoubleBridge ----------------------------------------- Key: HSEARCH-331 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-331 Project: Hibernate Search Issue Type: Task Reporter: 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

14 years, 9 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-155) JMS implementation requires jndi - I want to use it in J2SE no web container/appserver

by Jason Eacott (JIRA)

JMS implementation requires jndi - I want to use it in J2SE no web container/appserver -------------------------------------------------------------------------------------- Key: HSEARCH-155 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-155 Project: Hibernate Search Issue Type: Improvement Affects Versions: 3.0.0.GA Environment: All Reporter: Jason Eacott the current JMS implementation requires jndi configuration, I would like to use hibernatesearch in a j2se project with the jms configuration. -- 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, 9 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-211) SharedReaderProvider: should own lock when testing for index state

by Sanne Grinovero (JIRA)

SharedReaderProvider: should own lock when testing for index state ------------------------------------------------------------------ Key: HSEARCH-211 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-211 Project: Hibernate Search Issue Type: Bug Components: directory provider Reporter: Sanne Grinovero Developing a new IndexReader I made a stress-test to compare performance to base readers, but got this when measuring SharedReaderProvider: Exception in thread "pool-2-thread-13" org.apache.lucene.store.AlreadyClosedException: this IndexReader is closed at org.apache.lucene.index.IndexReader.ensureOpen(IndexReader.java:163) at org.apache.lucene.index.DirectoryIndexReader.isCurrent(DirectoryIndexReader.java:149) at org.hibernate.search.reader.SharedReaderProvider.openReader(SharedReaderProvider.java:83) at org.hibernate.search.query.FullTextQueryImpl.buildSearcher(FullTextQueryImpl.java:486) at org.hibernate.search.query.FullTextQueryImpl.getResultSize(FullTextQueryImpl.java:528) at org.hibernate.search.test.reader.performance.SearchActivity.doAction(SearchActivity.java:24) at org.hibernate.search.test.reader.performance.AbstractActivity.run(AbstractActivity.java:54) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) -- 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, 9 months

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