April 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HSEARCH-446) how to install hibernate-search.zip in my project

by azael espinosa (JIRA)

how to install hibernate-search.zip in my project ------------------------------------------------- Key: HSEARCH-446 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-446 Project: Hibernate Search Issue Type: New Feature Affects Versions: 3.1.1.GA Environment: sqlserver, jboss-5.1.0.GA, jboss-seam-2.2.0.GA, ant 1.6. Reporter: azael espinosa I have this error 17:08:47,495 WARN [JDBCExceptionReporter] SQL Error: 102, SQLState: S0001 17:08:47,495 ERROR [JDBCExceptionReporter] Incorrect syntax near '-'. I recommend installing hibernate-search-3.1.1.GA, download the zip from hibernate and now do not know where or how to install it to avoid that error -- 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, 11 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-462) Indexes are not getting updated when entity gets updated via hql.

by shareef shaik (JIRA)

Indexes are not getting updated when entity gets updated via hql. ----------------------------------------------------------------- Key: HSEARCH-462 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-462 Project: Hibernate Search Issue Type: Bug Affects Versions: 3.1.1.GA Environment: Hibernate 3.3, H-Search 3.1.1 GA, Hiberante Annotations, Oracle DB, FSDirectoryProvider Reporter: shareef shaik We are using Hibernate Annotations and Hibernate Search, and to my understanding there is no need to write listeners to update/delete index on update/delete of an entity. I tried updating an entity via hql update, and also via persisting the entity and making changes in it. In the second scenario, the index is getting updated, but in the first scenario it is not. I checked for the changes in db and in both scenarios, the changes are reflected in db. A simple test case for the same. Case 1: -------- String hql = "update UserMaster umst set umst.userName = :uName where umst.userId = :uId"; org.hibernate.Query query = getSession().createQuery(hql); query.setParameter("uName","ABM1"); query.setParameter("uId",1001L); query.executeUpdate(); Case 2: -------- UserMaster master = (UserMaster)getSession().get(UserMaster.class,1001L); master.setUserName("ABM1"); -- 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, 11 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-466) separating annotations from core as own jar

by Vadim Bauer (JIRA)

separating annotations from core as own jar ------------------------------------------- Key: HSEARCH-466 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-466 Project: Hibernate Search Issue Type: Improvement Components: build Affects Versions: 3.2.0.Beta1, 3.1.1.GA, 3.1.0.GA, 3.1.0.CR1, 3.1.0.Beta2, 3.1.0.Beta1, 3.1.2, 3.2.0.CR1, 3.3.0 Environment: not important Reporter: Vadim Bauer Why not separating the hibernate search annotations from HS core? e.g. hibernate-search-core.jar hibernate-search-annotations.jar It is quite cumbersome if you in a fat clients or RCPs environment and want share the same domain model with your client. The client needs to have lucene, hibernate search and hibernate stuff even thou he never uses it except a few annotations. If it is ok I would like contribute my changes to the community. Best regards Vadim -- 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, 11 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-492) FSMasterDirectoryProvider and FSSlaveDirectoryProvider don't shutdown the Executor

by Sylvain Charton (JIRA)

FSMasterDirectoryProvider and FSSlaveDirectoryProvider don't shutdown the Executor ---------------------------------------------------------------------------------- Key: HSEARCH-492 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-492 Project: Hibernate Search Issue Type: Bug Components: directory provider Affects Versions: 3.1.1.GA Environment: Java 1.6.0 Reporter: Sylvain Charton Priority: Minor I'm using Hibernate Search clustering feature in a stand alone Java application (not a webapp). My problem is the application never stops: many threads are still living. Both FSMasterDirectoryProvider and FSSlaveDirectoryProvider use a Single Thread Executor to perform the CopyTask. When the FSSlaveDirectoryProvider.stop() is called, the timer is stopped, but not the Executor in the TimerTask. Consequence is the process can't stop, because some threads are still living, endlessly. This happens after the first CopyDirectory task was executed. My fix was to copy this class in my code, and replace the Executor in TriggerTask class by an ExecutorService in FSSlaveDirectoryProvider class. The ExecutorService is initialized in the start() method: {code:Java}this.executor = Executors.newSingleThreadExecutor() ;{code} And properly shut down in the stop() method: {code:java} executor.shutdown(); boolean terminated = false ; try{ terminated = executor.awaitTermination(20, TimeUnit.SECONDS); } catch (InterruptedException e1) { terminated = false ; } if (!terminated) { executor.shutdownNow() ; } {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, 11 months

3
12
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-425) Remove support for compressed fields (support removed in Lucene3)

by Sanne Grinovero (JIRA)

Remove support for compressed fields (support removed in Lucene3) ----------------------------------------------------------------- Key: HSEARCH-425 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-425 Project: Hibernate Search Issue Type: Deprecation Components: documentation, mapping Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 3.2.0.Beta2 -- 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, 11 months

2
6
0 / 0

[Hibernate-JIRA] Created: (HV-303) in propertyPath don't get index for Sets and SortedSets

by wof (JIRA)

in propertyPath don't get index for Sets and SortedSets ------------------------------------------------------- Key: HV-303 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-303 Project: Hibernate Validator Issue Type: Bug Components: engine Affects Versions: 4.0.2.GA Reporter: wof Assignee: Hardy Ferentschik The method isIndexable in ValidatorImpl don't support SortedSets or Sets. While there is no no particular order for an Iterater of a Set, most common implementations iterate at least for two calls in the same way. So it is arguable if Sets should be supported. SortedSets on the other hand guarantee always a particular order and have to be supported. So there are possible solutions: - check for SortedSets and allow them - check for Set and hope that without change in this Set, the order will be the same as the last time (at least I know no other implementation) - check for Iterable and hope the same. ;-) cheers wof -- 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, 11 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-460) LazyInitializationException while removing entity with @ContainedIn annotation

by Maciej Szulik (JIRA)

LazyInitializationException while removing entity with @ContainedIn annotation ------------------------------------------------------------------------------ Key: HSEARCH-460 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-460 Project: Hibernate Search Issue Type: Bug Components: engine Affects Versions: 3.1.1.GA Reporter: Maciej Szulik Priority: Blocker Attachments: hibsearch.zip, Lazy.stack I attach a Jboss Seam 2.2.0.GA project (without lib directory - one should take it entirely from seam default application generated using seam gen), as a complete illustration of the problem. The Problem itself: I have 2 entities: Color (Long id, String name, Set<Vehicle> vehicles) and Vehicle (Long id, String name, Color color). Vehicle is indexed entity (@Indexed), while color has @ContainedIn on Set<Vehicle>. Problem arises while managing color objects, strictly speaking while removing colors, LazyInitalizationException is thrown (stack trace is in attachment). Every other operation on color entity (inserting, updating) works like a charm. In attached example I created with a simple page for managing colors. It presents a list of already defined color objects in DB. If non present, you should generate some with 'Add random color'. To obtain above error click on 'Remove' link next to one of the colors presented on list. -- 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, 11 months

3
8
0 / 0

[Hibernate-JIRA] Created: (HHH-5082) QueryException thrown when grouping by component

by Gail Badner (JIRA)

QueryException thrown when grouping by component ------------------------------------------------ Key: HHH-5082 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5082 Project: Hibernate Core Issue Type: Bug Components: query-criteria Affects Versions: 3.5.0-Final Reporter: Gail Badner Assignee: Gail Badner Fix For: 3.5.x QueryException thrown when grouping by component. -- 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, 11 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-5085) Literals with leading zero in HQL validated as octal but used as decimal

by James Livingston (JIRA)

Literals with leading zero in HQL validated as octal but used as decimal ------------------------------------------------------------------------ Key: HHH-5085 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5085 Project: Hibernate Core Issue Type: Bug Components: query-hql Affects Versions: 3.3.2 Reporter: James Livingston Priority: Minor The grammar used to parse HQL/JPAQL treats numeric literals[0] with a leading 0 as octal (and 0x as hexadecimal), however those values are always converted[1] as base 10. This means that a literal 0100 will match a value of decimal one hundred, but a literal of 0108 will fail to validate due to the '8' character. Either the grammar should not handle octal/hexadecimal, or the conversation should process them correctly. [0] Starting at line 831 of core/src/main/antlr/hql.g in the 3.3.2 source [1] LiteralProcessor.determineIntegerRepresentation() -- 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, 11 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-5080) NPE when determining types of named parameters

by John Aylward (JIRA)

NPE when determining types of named parameters ---------------------------------------------- Key: HHH-5080 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5080 Project: Hibernate Core Issue Type: Bug Components: core, query-hql Affects Versions: 3.5.0-Final Environment: sun java 6.0.19 runtime, hibernate 3.5.0-final using annotations, mysql 5.0.75-0ubuntu10.3 Reporter: John Aylward Attachments: hibernateLog.txt Attached is the relevant hibernate log with the offending query. Relevant stack trace: java.lang.NullPointerException at org.hibernate.hql.ast.ParameterTranslationsImpl.getNamedParameterExpectedType(ParameterTranslationsImpl.java:87) at org.hibernate.engine.query.HQLQueryPlan.buildParameterMetadata(HQLQueryPlan.java:320) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:121) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:80) at org.hibernate.engine.query.QueryPlanCache.getHQLQueryPlan(QueryPlanCache.java:98) at org.hibernate.impl.AbstractSessionImpl.getHQLQueryPlan(AbstractSessionImpl.java:156) at org.hibernate.impl.AbstractSessionImpl.createQuery(AbstractSessionImpl.java:135) at org.hibernate.impl.SessionImpl.createQuery(SessionImpl.java:1760) -- 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, 11 months

2
7
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues April 2010