November 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HSEARCH-897) Improve Archetype generated pom.xml

by Sanne Grinovero (JIRA)

Improve Archetype generated pom.xml ----------------------------------- Key: HSEARCH-897 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-897 Project: Hibernate Search Issue Type: Task Reporter: Sanne Grinovero Fix For: 4.0.0.Alpha3 There are several issues: - it should not contains an scm tag pointing to Hibernate Search's repository - not mention us as authors of the newly generated project - nor Hibernate as an organization - nor mandate our License! - generated project depends on org.hibernate:hibernate-search-analyzers:jar:[NEWLY GENERATED PROJECT VERSION] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-692) FieldSelection should be allowed in more cases

by Sanne Grinovero (JIRA)

FieldSelection should be allowed in more cases ---------------------------------------------- Key: HSEARCH-692 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-692 Project: Hibernate Search Issue Type: Improvement Reporter: Sanne Grinovero Fix For: 3.5 The allowFieldSelection is now turned off by the DocumentBuilder if the entity contains any field which is not two-way projectable. This results in having FieldSelectors being disabled, even if the only field being asked for as projection contains only two-way projectable fields. Also, the current code in org.hibernate.search.engine.DocumentBuilderIndexedEntity.checkAllowFieldSelection() is a mess; we should figure out from the bridges exactly which fields they are going to need to read: FieldSelector needs now to be disabled for bridges such as org.hibernate.search.test.id.PersonPKBridge. -- 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

1
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-376) Delegate search to remote nodes and aggregate

by Emmanuel Bernard (JIRA)

Delegate search to remote nodes and aggregate --------------------------------------------- Key: HSEARCH-376 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-376 Project: Hibernate Search Issue Type: New Feature Reporter: Emmanuel Bernard This would require to - discover the participating nodes - replace the IndexReaders with Searchable (for some valid reasons I chose not to initially) - use a ParallelMultiIndexSearcher - expose IndexSearcher remotely. will be be useful for infinispan -- 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

2
4
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-858) Assembly plugin prints a lot of warnings during build

by Hardy Ferentschik (JIRA)

Assembly plugin prints a lot of warnings during build ----------------------------------------------------- Key: HSEARCH-858 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-858 Project: Hibernate Search Issue Type: Task Components: build Affects Versions: 4.0.0.Alpha1 Reporter: Hardy Ferentschik Fix For: 4.0 The current assembly configuration is very complicated and needs to be adjusted manually all the time. At the same time the assembly plugin prints a lot of warnings during the assembly process: {noformat} INFO] --- maven-assembly-plugin:2.2.1:assembly (default-cli) @ hibernate-search-parent --- [INFO] Reading assembly descriptor: /Users/hardy/work/hibernate/git/search/src/main/assembly/dist.xml [WARNING] [DEPRECATION] moduleSet/binaries section detected in root-project assembly. MODULE BINARIES MAY NOT BE AVAILABLE FOR THIS ASSEMBLY! To refactor, move this assembly into a child project and use the flag <useAllReactorProjects>true</useAllReactorProjects> in each moduleSet. [INFO] Processing sources for module project: org.hibernate:hibernate-search:jar:4.0.0-SNAPSHOT [WARNING] NOTE: Currently, inclusion of module dependencies may produce unpredictable results if a version conflict occurs. [WARNING] The following patterns were never triggered in this artifact exclusion filter: o 'i18nlog:i18nlog' [WARNING] The following patterns were never triggered in this artifact exclusion filter: o 'i18nlog:i18nlog' [WARNING] [DEPRECATION] moduleSet/binaries section detected in root-project assembly. MODULE BINARIES MAY NOT BE AVAILABLE FOR THIS ASSEMBLY! To refactor, move this assembly into a child project and use the flag <useAllReactorProjects>true</useAllReactorProjects> in each moduleSet. [WARNING] NOTE: Currently, inclusion of module dependencies may produce unpredictable results if a version conflict occurs. [WARNING] The following patterns were never triggered in this artifact exclusion filter: o 'i18nlog:*' [INFO] Building tar : /Users/hardy/work/hibernate/git/search/target/hibernate-search-4.0.0-SNAPSHOT-dist.tar.gz {noformat} We need to investigate whether there is a new version of the plugin, a better way to configure it or a better way to build the bundles in general. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-336) Create a DirectoryProvider for InstantiatedIndex

by Sanne Grinovero (JIRA)

Create a DirectoryProvider for InstantiatedIndex ------------------------------------------------ Key: HSEARCH-336 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-336 Project: Hibernate Search Issue Type: New Feature Components: directory provider Reporter: Sanne Grinovero Assignee: Sanne Grinovero have an option to copy startup data from at startup (like clone a FSDirectory) ? -- 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

3
12
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-794) Make FilterCachingStrategy a SPI

by Emmanuel Bernard (JIRA)

Make FilterCachingStrategy a SPI -------------------------------- Key: HSEARCH-794 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-794 Project: Hibernate Search Issue Type: Improvement Components: engine Reporter: Emmanuel Bernard Fix For: 4.0.0.Alpha1 Make sure we agree on the idea and move the class to .spi package -- 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

2
5
0 / 0

[Hibernate-JIRA] Created: (HV-500) ConfigurationImpl should support multiple programmatic constraint mappings

by Gunnar Morling (JIRA)

ConfigurationImpl should support multiple programmatic constraint mappings -------------------------------------------------------------------------- Key: HV-500 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-500 Project: Hibernate Validator Issue Type: Improvement Components: engine Reporter: Gunnar Morling Fix For: 4.3.0.next The method {{HibernateValidatorConfiguration#addMapping(ConstraintMapping mapping)}} suggests that several programmatically configured constraint mappings could be added to the configuration (similar to XML based mappings). Actually only one programmatic mapping is supported though, as {{ConfigurationImpl}} doesn't hold a collection of mappings, but only a single one. Hence only the mapping "added" last is actually applied. -- 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

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5308) hibernate cannot handle Inheritance, if the discriminatorColumn is part of a composite pk in a @MappedSupperclass

by AndyW (JIRA)

hibernate cannot handle Inheritance, if the discriminatorColumn is part of a composite pk in a @MappedSupperclass ----------------------------------------------------------------------------------------------------------------- Key: HHH-5308 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5308 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.5.2 Environment: Linux, Java 6 Reporter: AndyW Attachments: jpatest_hibernate_aktuell.zip Hi, i am having the following mapping structure @MappedSuperclass LadeeinheitEinausgaenge | @Entity | @Inheritance(strategy=InheritanceType.SINGLE_TABLE) | @DiscriminatorColumn(name = "LAEA_TYP") | @Table(name = "LADEEINHEIT_EINAUS") +- AbstractEinAusgang | | @DiscriminatorValue("AUSGANG") | | @Entity | +- LadeeinheitAusgaenge | | @DiscriminatorValue("EINGANG") | | @Entity | +- LadeeinheitEingaenge The composite pk is defined in the MappedSuperclass. The discriminator column is part of the composite pk. when i start my app, i am getting the following error: > Repeated column in mapping for entity: de.dbsystel.gate.integration.model.LadeeinheitAusgaenge column: LAEA_TYP (should be mapped with insert="false" update="false") the error message is kind of misleading, because the @DiscriminatorColumn annotation only defines which column to use for the mapping, i guess. however the actual mapping is defined in the MappedSuperclass. When moving the @DiscriminatorColumn to the mappedSuperclass, hibernate does not complain when starting, but then it creates tables, it create the default DiscriminatorColumn named DTYPE, which is not wanted, because i explicitly defined a discriminator column. If the discriminator column is defined in the mappedSuperclass then it will be ignore. if it is defined in my abstract base entity. then i get the error mentioned above. My Intention is to query the AbstractEinAusgang and get one of the two possible concrete classes, that are defined via the discriminator value. i have attached the testcase that shows the problem. cheers, andy -- 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

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-4601) implement orphanRemoval for *ToMany and OneToOne

by Emmanuel Bernard (JIRA)

implement orphanRemoval for *ToMany and OneToOne ------------------------------------------------ Key: HHH-4601 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4601 Project: Hibernate Core Issue Type: Sub-task 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

14 years, 3 months

5
9
0 / 0

[Hibernate-JIRA] Created: (HHH-5559) JPA 2 orphanRemoval on OneToOne relation does not work properly

by loic descotte (JIRA)

JPA 2 orphanRemoval on OneToOne relation does not work properly --------------------------------------------------------------- Key: HHH-5559 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5559 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.6.0.Beta4, 3.6.0.Beta3, 3.5.5, 3.6.0.Beta2, 3.6.0.Beta1, 3.5.4, 3.5.3, 3.5.2, 3.5.1, 3.5.0-Final, 3.5.0-CR-2, 3.5.0-CR-1, 3.5.0-Beta-4, 3.5.0-Beta-3, 3.5.0-Beta-2, 3.5.0.Beta-1 Environment: Hibernate 2.5 (tested with 3.5.4) Reporter: loic descotte I have an class A with a oneToRelation with a classe B : @Entity public class A{ @OneToOne(cascade = {CascadeType.ALL}, orphanRemoval=true) B b; ... } If i do this : A a = new A(); B b1 = new B(); a.setB(b1); em.persist(a); B b2 = new B(); a.setB(b2); em.update(a); As b1 become an orphan, Hibernate should remove it from the database. But it still remains in the DB. -- 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

9
19
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 November 2011