April 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HSEARCH-333) Remove or improve log warning in DocumentBuilderContainedEntity.checkDocumentId

by Hardy Ferentschik (JIRA)

Remove or improve log warning in DocumentBuilderContainedEntity.checkDocumentId ------------------------------------------------------------------------------- Key: HSEARCH-333 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-333 Project: Hibernate Search Issue Type: Bug Components: engine Affects Versions: 3.1.0.GA Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 3.1.1 http://forum.hibernate.org/viewtopic.php?t=993097 -- 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, 5 months

3
7
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-486) Review the getting started section's pom and archetype creation

by Emmanuel Bernard (JIRA)

Review the getting started section's pom and archetype creation --------------------------------------------------------------- Key: HSEARCH-486 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-486 Project: Hibernate Search Issue Type: Task Components: documentation Affects Versions: 3.2.0.Beta1 Reporter: Emmanuel Bernard Assignee: Hardy Ferentschik Fix For: 3.2.0 HSEARCH-428 has been done but a second polish is likely required. -- 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, 5 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-515) Lucene AlreadyClosedExceptions During Batch Processing With ASYNC Workers

by j nadler (JIRA)

Lucene AlreadyClosedExceptions During Batch Processing With ASYNC Workers ------------------------------------------------------------------------- Key: HSEARCH-515 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-515 Project: Hibernate Search Issue Type: Bug Affects Versions: 3.2.0.CR1 Reporter: j nadler We have a batch job that updates 10,000 preexisting User entities in a single transaction; each User has an @IndexedEmbedded UserDetails entity which is also updated during the job run. When run with hibernate.search.worker.execution=sync, life is good. When we run with async, indexing intermittently fails with a Lucene AlreadyClosedException. There is no other exception logged even with TRACE logging enabled. We did not see this issue with 3.1.1GA but Sanne has noted that it is possible the exceptions were occurring and were not being logged in that version; I cannot exclude this possibility. Posted a log file to http://www.attensa.com/download/files/attensa.log the first exception is at timestamp [2010-04-21 11:23:45.992,236829] Associated forum discussion here: https://forum.hibernate.org/viewtopic.php?f=9&t=1004022&p=2429214#p2429214 -- 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, 5 months

3
11
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-506) Suggest dependency to core 3.5.1

by Sanne Grinovero (JIRA)

Suggest dependency to core 3.5.1 -------------------------------- Key: HSEARCH-506 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-506 Project: Hibernate Search Issue Type: Improvement Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 3.2.0 The release pom should suggest a dependency to core version 3.5.1 , but it would be nice to start defining support for ranges of versions. I'd propose something like {{<version>[3.5.0,3.6.0)</version>}} but have to try to see how this interacts with the {{.FINAL}} postfix -- 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, 5 months

1
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-512) Associate with two open session issue and subsequent hang

by Marc Schipperheyn (JIRA)

Associate with two open session issue and subsequent hang --------------------------------------------------------- Key: HSEARCH-512 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-512 Project: Hibernate Search Issue Type: Bug Components: engine Affects Versions: 3.2.0.CR1 Environment: Hibernate 3.5.1, MySQL 5.1.44, Lucene 2.9.2 Reporter: Marc Schipperheyn I've noticed the issue described in http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-490. It seems to happen sometimes, especially when threads pause for a debugging break and I don't immediately continue them. But I also notice that then the MassIndexer just doesn't finish and hangs with all the threads still in running state. Nothing seems to be happening or completing. I think that HSEARCH-490 has prevented the threads from completing at this point. The system/website then becomes completely unresponsive. -- 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, 5 months

2
16
0 / 0

[Hibernate-JIRA] Created: (HHH-1992) Some cascade actions should not trigger a property access on lazy properties

by Emmanuel Bernard (JIRA)

Some cascade actions should not trigger a property access on lazy properties ---------------------------------------------------------------------------- Key: HHH-1992 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1992 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.cr3 Reporter: Emmanuel Bernard Assigned to: Emmanuel Bernard Priority: Critical Fix For: 3.2.0.ga -- 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, 5 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HV-310) Define, which parts of HV constitute its public API

by Gunnar Morling (JIRA)

Define, which parts of HV constitute its public API --------------------------------------------------- Key: HV-310 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-310 Project: Hibernate Validator Issue Type: Improvement Reporter: Gunnar Morling Assignee: Hardy Ferentschik Fix For: 4.1.0 Background: Mostly users interact only indirectly with Hibernate Validator through the Bean Validation API. But there are also some classes within HV, which are intended to be directly accessed by users (@Email, ResourceBundleMessageInterpolator etc). Right now it is not obvious, which parts (packages, classes) of Hibernate Validator make up this public API. To do: * Identify and mark those parts of HV, which constitute its public, user-accessible API. The following rules should apply: *# It seems useful to let complete packages be part of the API or not (instead of single classes) *# Non-public packages shouldn't contain public packages *# Whether a package is public or not should be stated in the package's JavaDoc. *# The fewer public classes there are, the better, as it will be way harder to modify those in future versions. * The following packages/classes are candidates for the public API: ** org.hibernate.validator ** org.hibernate.validator.constraints ** org.hibernate.validator.engine.resourceloading (should be moved due to 2.; maybe CachingResourceBundleLocator should be excluded?) ** org.hibernate.validator.engine.ResourceBundleMessageInterpolator (should be moved due to 1.) * Add a section to the HV ref guide describing the public API. In that context it should be defined and documented, which rules apply to the further development of this API (especially with respect to changes breaking backward-compatibility) * Modify the HV OSGi manifest in order to export only the public packages -- 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, 5 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HV-314) Add @List annotations to the HV-specific constraints

by Gunnar Morling (JIRA)

Add @List annotations to the HV-specific constraints ---------------------------------------------------- Key: HV-314 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-314 Project: Hibernate Validator Issue Type: Improvement Components: validators Affects Versions: 4.1.0.Beta1 Reporter: Gunnar Morling Assignee: Hardy Ferentschik Priority: Minor Background: The BV spec (chapter 2.2) recommends, that each constraint annotation should be accompanied by an inner multi-valued annotation @List, which allows to specify the same constraint multiple times at one element. This can be useful for instance to let the same constraint have different error messages for different validation groups. Todo: Add @List annotations as inner annotations to the HV-specific constraint annotations. -- 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, 5 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5179) Criteria Projections.countDistinct() does not work for composite IDs or components for some dialects

by Gail Badner (JIRA)

Criteria Projections.countDistinct() does not work for composite IDs or components for some dialects ---------------------------------------------------------------------------------------------------- Key: HHH-5179 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5179 Project: Hibernate Core Issue Type: Improvement Components: query-criteria Affects Versions: 3.5.1 Environment: hsqldb, mssql Reporter: Gail Badner Assignee: Gail Badner Priority: Minor Criteria Projections.countDistinct() does not work for composite IDs or compenents if the dialect only supports SELECT COUNT( DISTINCT ... ) with only 1 argument. According to http://msdn.microsoft.com/en-us/library/ms175997.aspx , a SQL workaround is: SELECT COUNT(*) FROM (SELECT DISTINCT authorFirstName, authorLastName, authorMiddleName, authorId from Authors) as foo -- 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, 5 months

1
1
0 / 0

[Hibernate-JIRA] Updated: (HHH-1015) Incorrect SQL generated when one-to-many foreign key is in a discriminated subclass table

by Gail Badner (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1015?page=c... ] Gail Badner updated HHH-1015: ----------------------------- Affects Version/s: 3.5.1 > Incorrect SQL generated when one-to-many foreign key is in a discriminated subclass table > ----------------------------------------------------------------------------------------- > > Key: HHH-1015 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1015 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.1 beta 2, 3.5.1 > Environment: Hibernate versions 3.1 beta 3 and 3.0.5 > Reporter: Steven Grimm > Priority: Minor > Attachments: 3.3.2.GA-HHH-1015-v1.patch, hhh-1015-version2.patch, hhh-1015.patch > > > I have the following mappings describing a hierarchy of events and a class that the events refer to: > <hibernate-mapping package="com.xyz"> > <class name="Event" table="event" discriminator-value="-1"> > <id name="Id" type="long" column="event_id"/> > <discriminator column="event_type_id" type="integer" /> > <subclass name="EventPayer" discriminator-value="-3"> > <join table="event_payer"> > <key column="event_id" /> > <many-to-one name="payer" column="payer_id" class="Payer" /> > </join> > <subclass name="EventPayerCreated" discriminator-value="1" /> > </subclass> > </class> > <class name="Payer" table="payer"> > <id name="payerId" column="payer_id" type="java.lang.Long"/> > <set name="eventPayers" inverse="true" cascade="save-update"> > <key column="payer_id"/> > <one-to-many class="EventPayer"/> > </set> > </class> > </hibernate-mapping> > When I fetch the Payer.eventPayers collection, Hibernate generates this SQL: > select eventpayer0_.payer_id as payer7_1_, > eventpayer0_.event_id as event1_1_, > eventpayer0_.event_id as event1_5_0_, > eventpayer0_1_.payer_id as payer2_6_0_, > eventpayer0_.event_type_id as event2_5_0_ > from event eventpayer0_ > inner join event_payer eventpayer0_1_ > on eventpayer0_.event_id=eventpayer0_1_.event_id > where eventpayer0_.payer_id=? > The problem is that there is no event.payer_id column; payer_id is in the child table, not the parent. It appears that specifying a discriminated subclass in <one-to-many> is the same as specifying the superclass, or that Hibernate is ignoring the subclass's <join> element. As far as I can tell, this leaves no way to resolve bidirectional associations where one end of the association is in a discriminated subclass, which seems like a perfectly reasonable thing to want to do. > I also tried changing <key column="payer_id"/> to <key property-ref="payer"/> in the Payer class's <set> element, but got similar behavior in the form of a "property not found" error: Hibernate is either looking in the superclass's properties rather than the subclass's or is ignoring the list of properties in the <join> element. -- 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, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues April 2010