May 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HSEARCH-77) Expose configuration settings through API

by Christian Bauer (JIRA)

Expose configuration settings through API ----------------------------------------- Key: HSEARCH-77 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-77 Project: Hibernate Search Issue Type: New Feature Components: engine Reporter: Christian Bauer Priority: Minor I'd like to access my configuration settings, probably on a SearchFactory. I want to be able to e.g. get the hibernate.search.worker.batch_size to adjust my loops dynamically. I imagine there are a few other usecases, for example, avoid hardcoding the analyzer for hit highlighting but using the same as the HSearch indexer. -- 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

17 years, 6 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3310) Using Nested DetachedCriteria (Sub-Selects) throwing NullPointerException

by Roshan Dawrani (JIRA)

Using Nested DetachedCriteria (Sub-Selects) throwing NullPointerException ------------------------------------------------------------------------- Key: HHH-3310 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3310 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.5 Environment: Hibernate 3.2.5, Oracle 10g Reporter: Roshan Dawrani Attachments: Nested_Subselects.zip Hi, We have come across an issue with the usage of nested subselects in the sql query with hibernate 3.2.5. We get the following exception when there is more than one level of sub-selects in the query : ---------------------------------------------------------------------------------------------------------------------- java.lang.NullPointerException at org.hibernate.criterion.SubqueryExpression.getTypedValues(SubqueryExpression.java:80) at org.hibernate.loader.criteria.CriteriaQueryTranslator.getQueryParameters(CriteriaQueryTranslator.java:251) at org.hibernate.criterion.SubqueryExpression.toSqlString(SubqueryExpression.java:55) at org.hibernate.loader.criteria.CriteriaQueryTranslator.getWhereCondition(CriteriaQueryTranslator.java:334) at org.hibernate.loader.criteria.CriteriaJoinWalker.<init>(CriteriaJoinWalker.java:71) at org.hibernate.loader.criteria.CriteriaLoader.<init>(CriteriaLoader.java:67) at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1550) at org.hibernate.impl.CriteriaImpl.list(CriteriaImpl.java:283) at NestedDetachedCriteriaTest.testNestedDetachedCriteria(Unknown Source) ---------------------------------------------------------------------------------------------------------------------- The actual query that gets fired is like: ---------------------------------------------------------------------------------------------------------------------- select this_.name as y0_ from cat this_ where this_.name = (select this0__.name as y0_ from cat this0__ where this0__.parent_id = (select this0__.parent_id as y0_ from cat this0__ where this0__.name = (select this0__.name as y0_ from cat this0__ where this0__.cat_id = ?))) ---------------------------------------------------------------------------------------------------------------------- We investigated the issue and have fixed it by making some changes in org.hibernate.criterion.SubqueryExpression class. The attached file has the following contents: 1. SubqueryExpression.java - Fix we have made to SubqueryExpression class. 2. NestedDetachedCriteriaTest.zip - A test case to highlight the nested sub-select issue (testNestedDetachedCriteria). Regards, Roshan -- 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

17 years, 6 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-75) Use FieldSelector to filter returned Fields

by Emmanuel Bernard (JIRA)

Use FieldSelector to filter returned Fields ------------------------------------------- Key: HSEARCH-75 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-75 Project: Hibernate Search Issue Type: Improvement Components: engine Reporter: Emmanuel Bernard Priority: Minor Might be useful for projections, but is most likely unnecessary. -- 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

17 years, 6 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-175) USe domain specific annotations to plug custom bridges

by Emmanuel Bernard (JIRA)

USe domain specific annotations to plug custom bridges ------------------------------------------------------ Key: HSEARCH-175 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-175 Project: Hibernate Search Issue Type: New Feature Components: mapping Reporter: Emmanuel Bernard Fix For: 3.1.0 Use annotated annotations to declare bridges. Ie offer the same flexibility used by HSearch in @DateBridge -- 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

17 years, 6 months

1
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-176) explicitly setting cfg property to lucene default

by Sanne Grinovero (JIRA)

explicitly setting cfg property to lucene default ------------------------------------------------- Key: HSEARCH-176 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-176 Project: Hibernate Search Issue Type: Improvement Components: directory provider, documentation Reporter: Sanne Grinovero Priority: Trivial As highlighted by previous patch for http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-153 , some configuration settings may be inherited, so it becomes difficult to explicitly set "default" settings on some settings as some values are "Integer.MAX_VALUE" or "null" but the cfg parser only accepts int values. Also if the users wants to explicitly set lucene defaults it needs to study the current lucene source code. I'm going to provide a patch to support besides current int values also "default" and "null" Strings, to explicitly configure H.Search to: "default" -> don't mess with the value "null" -> explicitly null the value Also someone may find it useful to represent "MAX_VALUE", what do you think about that, or other configurations that should be recognized? -- 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

17 years, 6 months

2
7
0 / 0

[Hibernate-JIRA] Created: (HHH-3283) protect BulkManipulationTest#testInsertWithGeneratedTimestampVersion where Dialect#supportsParametersInInsertSelect == false

by Steve Ebersole (JIRA)

protect BulkManipulationTest#testInsertWithGeneratedTimestampVersion where Dialect#supportsParametersInInsertSelect == false ---------------------------------------------------------------------------------------------------------------------------- Key: HHH-3283 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3283 Project: Hibernate3 Issue Type: Improvement Components: testsuite Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.2.x, 3.3.0.CR2 Because the timestamp there is vm-based, that particular test is hosed if the dialect/jdbc-driver does not support defining parameters in the INSERT ... SELECT statement. -- 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

17 years, 6 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-2883) ManyToMany doesn't work with polymorfism

by Dirk (JIRA)

ManyToMany doesn't work with polymorfism ---------------------------------------- Key: HHH-2883 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2883 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.4 Environment: Hibernate 3.2.4, Annotations 3.3.0, Entitymanager 3.3.0 Reporter: Dirk We tried out the SingleTable inheritance with a ManyToMany @Entity @Table(name="SHB_PRINCIPAL") @Inheritance(strategy=InheritanceType.SINGLE_TABLE) @DiscriminatorColumn(name="TYPE",discriminatorType=DiscriminatorType.INTEGER) @Cache(usage=CacheConcurrencyStrategy.TRANSACTIONAL) public class Principal implements Serializable { .... @Entity @DiscriminatorValue(PrincipalType.USER_NR) @Cache(usage=CacheConcurrencyStrategy.NONSTRICT_READ_WRITE) public class ApplicationUser extends Principal { private static final long serialVersionUID = 1L; @ManyToMany(fetch=FetchType.LAZY, cascade={CascadeType.PERSIST, CascadeType.MERGE, CascadeType.REFRESH}, targetEntity=Role.class) @JoinTable(name="SHB_PRINCIPAL_TO_PRINCIPAL", joinColumns=@JoinColumn(name="FROM_PRINCIPAL_ID"), inverseJoinColumns=@JoinColumn(name="TO_PRINCIPAL_ID")) private Set<Role> roles; @ManyToMany(fetch=FetchType.LAZY, cascade={CascadeType.PERSIST, CascadeType.MERGE, CascadeType.REFRESH}, targetEntity=ApplicationGroup.class) @JoinTable(name="SHB_PRINCIPAL_TO_PRINCIPAL", joinColumns=@JoinColumn(name="FROM_PRINCIPAL_ID"), inverseJoinColumns=@JoinColumn(name="TO_PRINCIPAL_ID")) private Set<ApplicationGroup> groups; @Entity @DiscriminatorValue(PrincipalType.GROUP_NR) @Cache(usage=CacheConcurrencyStrategy.NONSTRICT_READ_WRITE) public class ApplicationGroup extends Principal { private static final long serialVersionUID = 1L; @ManyToMany(fetch=FetchType.LAZY, cascade={CascadeType.PERSIST, CascadeType.MERGE, CascadeType.REFRESH}) @JoinTable(name="SHB_PRINCIPAL_TO_PRINCIPAL", joinColumns=@JoinColumn(name="TO_PRINCIPAL_ID"), inverseJoinColumns=@JoinColumn(name="FROM_PRINCIPAL_ID")) private Set<ApplicationUser> users; public ApplicationGroup() { super(); this.type = PrincipalType.GROUP; } public Set<ApplicationUser> getUsers() { return users; } public void setUsers(Set<ApplicationUser> users) { this.users = users; } } But in the groups and the roles of the user, hibernate returns all principals, not only the users or groups. In the query it's clear that the descriminator is NOT used. -- 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

17 years, 6 months

4
5
0 / 0

[Hibernate-JIRA] Created: (EJB-360) Create a property to intercept the Configuration for programmatic modification before the EntityManagerFactory is created

by John Leach (JIRA)

Create a property to intercept the Configuration for programmatic modification before the EntityManagerFactory is created ------------------------------------------------------------------------------------------------------------------------- Key: EJB-360 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-360 Project: Hibernate Entity Manager Issue Type: New Feature Components: EntityManager Affects Versions: 3.3.2.GA Reporter: John Leach Attachments: ConfigurationCustomizer.patch Create a property (hibernate.cfg.customizer) in persistence.xml which allows the user to specify a class which can programmatically modify the constructed Configuration object (built via annotations and XML configuration) before the EntityManagerFactory is created. The aim is to provide a third mechanism for configuration, after annotation and XML configuration has been performed. By specifying a user supplied class name the user can then use Configuration methods to access the mappings and make programmatic modifications, such as converting Cascade.ALL (JPA) to cascade all-delete-orphans (Hibernate). The attached patch provides the code modifications, currently used in Spikes, (http://lab.jugtorino.it/trac/sandbox/wiki/Spikes) to allow programmatic modifications of the Configuration object. The patch file was created from the current trunk (18/05/2008) of hibernate-entitymanager, more specifically, trunk/src/java/org/hibernate/ejb. The user supplied class must have a no argument constructor, and implement the org.hibernate.ejb.ConfigurationCustomizer interface. The mechanism is similar to hibernate.ejb.interceptor in concept, except that it acts on the Configuration object rather than on the entity life cycle. -- 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

17 years, 6 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2254) A query validation bug produces QueryException: "Expected positional parameter count: 1, actual parameters: [Parent@bec357b] [from Child this where this.id.parent = ?]"

by Hernan Liendo (JIRA)

A query validation bug produces QueryException: "Expected positional parameter count: 1, actual parameters: [Parent@bec357b] [from Child this where this.id.parent = ?]" ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ Key: HHH-2254 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2254 Project: Hibernate3 Type: Bug Components: query-hql Versions: 3.2.0.ga Environment: Hibernate 3.2 using Sybase. However this is not an environment caused problem. It's supposed to happen in every environment. Reporter: Hernan Liendo -- Short description ============================================================================ -- A query validation bug produces QueryException: "Expected positional parameter count: 1, actual parameters: [Parent@bec357b] [from Child this where this.id.parent = ?]. Both Parent and Child use composite keys. -- Context ====================================================================================== -- Having composite keys for a Parent class and a Child class, I want to retrieve childs that belong to an specific Parent. -- Parent Definition ============================================================================ -- public class Parent { public ParentId ParentId; ... } public class ParentId { private String idField1; private int idField2; ... } // the parent mapping <hibernate-mapping> <class mutable="false" table="xx" name="Parent"> <composite-id class="ParentId" access="field" name="parentId"> <key-property column="idField1" access="field" name="idField1"/> <key-property column="idField2" access="field" name="idField2"/> </composite-id> </class> </hibernate-mapping> -- Child Definition ============================================================================ -- public class Child { public ChildId childId; ... } public class ChildId { public Parent parent; public String aditionalIdField; ... } // the mapping <hibernate-mapping> <class mutable="false" table="yyy" name="Child"> <composite-id class="ChildId" access="field" name="childId"> <key-many-to-one name="parent" class="Parent" access="field"> <column name="idField1" not-null="true" /> <column name="idField2" not-null="true" /> </key-many-to-one> <key-property column="aditionalIdField" access="field" name="aditionalIdField"/> </composite-id> </class> </hibernate-mapping> -- HQL Statement ============================================================================ -- from Child this where this.childId.parent = ? or from Child this where this.id.parent = ? // using aliased id -- The Exception ============================================================================ -- org.hibernate.QueryException: Expected positional parameter count: 1, actual parameters: [Parent@bec357b] [from Child this where this.childId.parent = ?] at org.hibernate.impl.AbstractQueryImpl.verifyParameters(AbstractQueryImpl.java:319) at org.hibernate.impl.AbstractQueryImpl.verifyParameters(AbstractQueryImpl.java:275) at org.hibernate.impl.QueryImpl.list(QueryImpl.java:75) ... -- The Problem ============================================================================ -- class: org.hibernate.impl.AbstractQueryImpl method: protected void verifyParameters(boolean reserveFirstParameter) throws HibernateException line: 286 The method validates parameters. It resolves the "positionalValueSpan" variable witch in my case gets the value of 2 (One for parent's idField1 and the other for parent's idField2). The method compares positionalValueSpan (2) with parameterMetadata.getOrdinalParameterCount() witch it is 1 (the quantity of "?" signs in the HQL statement". This bug only happens when: 1. composed keys are used (and) 2. having a parent-child relationship (and) 3. resolving children from certain parent. -- Hibernate user workaround ============================================================================ -- Not to use a parent instance variable in the Child class. Hope this helps. If you guys need the source code in order to check the bug, please let me know it. Good luck! Hernan -- 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

17 years, 6 months

4
6
0 / 0

[Hibernate-JIRA] Created: (EJB-312) Hibernate EM 3.3.1.ga has invalid pom.xml - depends on jboss-common-core instead of a jboss-archive-browsing

by Matt Raible (JIRA)

Hibernate EM 3.3.1.ga has invalid pom.xml - depends on jboss-common-core instead of a jboss-archive-browsing ------------------------------------------------------------------------------------------------------------ Key: EJB-312 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-312 Project: Hibernate Entity Manager Issue Type: Bug Components: EntityManager Affects Versions: 3.3.1.GA Reporter: Matt Raible http://forum.hibernate.org/viewtopic.php?p=2363366 -- 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

17 years, 6 months

2
1
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 May 2008