February 2012 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HV-542) HibernateTraversableResolver does not correctly determine if an lazy property is initialized.

by Tim Heys (JIRA)

HibernateTraversableResolver does not correctly determine if an lazy property is initialized. --------------------------------------------------------------------------------------------- Key: HV-542 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-542 Project: Hibernate Validator Issue Type: Bug Components: engine Affects Versions: 4.1.0.Final Environment: HV4.1F, HC3.6.7F, JPA2 Reporter: Tim Heys HibernateTraversableResolver is returning true in "isReachable" for lazy loaded properties that are not initliazed. Line 115: Hibernate.isPropertyInitialized( traversableObject, traversableProperty.getName() ); only ch "traversableObject" is a Direct reference to the Entity and not a proxy, and Hibernate.isPropertyInitialized is only checking if it is an instance of HibernateProxy or "instrumented" to determine if it is initialized or not. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-6915) Restrictions.ilike(String propertyValue, Object value) does not correctly initialize LikeExpresison

by Martin Kartumovich (JIRA)

Restrictions.ilike(String propertyValue, Object value) does not correctly initialize LikeExpresison --------------------------------------------------------------------------------------------------- Key: HHH-6915 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6915 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 4.0.0.Final Reporter: Martin Kartumovich Priority: Minor The method Restrictions.ilike(String propertyValue, Object value) uses the LikeExpression-Constructor LikeExpression(propertyName, value.toString()) which will initialize the LikeExpression with "ignoreCase = false". The resulting SQL shows a normal "xyz like ?" instead of the expected "lower(xyz) like lower(?)" (i.e. Oracle10gDialect). This issue seems to have been introduced with HHH-4943. Workaround: Use Restrictions.ilike(String propertyValue, Object value, MatchMode mode). This will correctly initialize LikeExpression with "ignoreCase = true". -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

5
8
0 / 0

[Hibernate-JIRA] Created: (HHH-6556) Bind unsaved value for identifier/version property

by Strong Liu (JIRA)

Bind unsaved value for identifier/version property -------------------------------------------------- Key: HHH-6556 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6556 Project: Hibernate Core Issue Type: Task Components: metamodel Reporter: Strong Liu Fix For: 4.0.0.next currently org.hibernate.metamodel.binding.KeyValueBinding#getUnsavedValue is not binded -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

3
6
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-979) Programmatic API: mapping a composite primary key

by Fuessmann (JIRA)

Programmatic API: mapping a composite primary key ------------------------------------------------- Key: HSEARCH-979 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-979 Project: Hibernate Search Issue Type: Bug Components: mapping Affects Versions: 3.4.1.Final, 3.3.0.Final Environment: Hibernate 3.6 Final Reporter: Fuessmann Hallo, I'm using Hibernate Search in combination with the [b]Programmatic API[/b] for dynamic indexing. Is there any possibility to index an entity with an composite primary key annotated with [b]@EmbeddedId[/b]. Using H.Search without the Programmatic API i choose a TwoWayFieldBridge but how can I use it with the Programmatic API? In my case I am trying to implement a programmatic mapping for an entity. The entity has an an composite primary key annotated with @EmbeddedId. {quote} ... @Entity(name = "a") @Table(name = "a") public class A implements java.io.Serializable { ... @EmbeddedId @AttributeOverrides( { @AttributeOverride(name = "name_1", column = @Column(name = "name_1", nullable = false, length = 64)), @AttributeOverride(name = "name_2", column = @Column(name = "name_2", nullable = false, length = 16)) }) public AId getId() { return this.id; ... } {quote} Code for ABridge.class is not shown but still exists .. I try a code like this, but the code does not work: {quote} mapping.entity(A.class).indexed().indexName("a") .property("id", ElementType.METHOD).documentId().field().bridge(ABridge.class) {quote} Exception occurred during event dispatching: {quote} org.hibernate.HibernateException: [color=#FF0000]could not init listeners{color} ... Caused by: org.hibernate.search.SearchException: {color:red} Unable to guess FieldBridge for id{color} ... {quote} I need an advise to solve my problem. Thanks -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

4
5
0 / 0

[Hibernate-JIRA] Created: (HHH-7072) ElementCollection not updated correctly if the Embeddable component has a nullable property

by Aaron Trewern (JIRA)

ElementCollection not updated correctly if the Embeddable component has a nullable property ------------------------------------------------------------------------------------------- Key: HHH-7072 URL: https://hibernate.onjira.com/browse/HHH-7072 Project: Hibernate ORM Issue Type: Bug Components: annotations Affects Versions: 3.5.2 Reporter: Aaron Trewern I have an @ElementCollection that is a collection of @Embeddable components. When saving an updated entity I can see that Hibernate issues an SQL DELETE for each of the rows in the collection followed by an INSERT, as is expected behaviour for an @ElementCollection. The rows are deleted using a where clause that includes all the properties of the @Embeddabkle component. With MySQL the DELETE fails to delete any rows where the property is a nullable property and the previous value was null. This is because Hibernate issues a prepared SQL ststement like "DELETE FROM tableName t where t.a = ? and t.b = ?" now if b is a nullable property and the component being saved has a null value for b then the delete will fail. To correctly delete the row with MySQL the statement should be "DELETE FROM tableName t where t.a = ? and t.b is null" -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-6617) Remove deprecation from Configuration until after new metamodel completely in place

by Steve Ebersole (JIRA)

Remove deprecation from Configuration until after new metamodel completely in place ----------------------------------------------------------------------------------- Key: HHH-6617 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6617 Project: Hibernate Core Issue Type: Task Reporter: Steve Ebersole Assignee: Steve Ebersole Decided to leave in place for {{Ejb3Configuration}} since JPA bootstrapping was always the recommended and supported mechanism for JPA use cases. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-959) Create copyright.txt as mentioned by the license headers

by Hardy Ferentschik (JIRA)

Create copyright.txt as mentioned by the license headers -------------------------------------------------------- Key: HSEARCH-959 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-959 Project: Hibernate Search Issue Type: Bug Affects Versions: 4.0.0.CR1 Reporter: Hardy Ferentschik Priority: Minor Fix For: 4.1 See also https://hibernate.onjira.com/browse/HV-518 We probably can apply the same solution as the one applied on HV. Maybe we can/should create a consistent author tag format at the same time. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HV-457) Simplify IDE setup of annotation processor by providing a shaded jar

by Kevin Pollet (JIRA)

Simplify IDE setup of annotation processor by providing a shaded jar -------------------------------------------------------------------- Key: HV-457 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-457 Project: Hibernate Validator Issue Type: Improvement Components: annotation-processor Reporter: Kevin Pollet When configuring the annotation processor in IDEs it's classpath has to be specified. In IDEs like Netbeans or IntelliJ the annotation processor can use the project classpath. But it's better if the classpath of project and annotation processor are isolated. In that case people shall setup manually the annotation processor classpath which has to contain at least HV and BV dependency. As Gunnar said it would be usefull to simplify the annotation processor configuration in IDEs by providing a shaded jar. -- 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

12 years, 9 months

3
16
0 / 0

[Hibernate-JIRA] Created: (HHH-6624) Interaction between the JBossTS and the datasource is broken causing envers test failures

by Gail Badner (JIRA)

Interaction between the JBossTS and the datasource is broken causing envers test failures ----------------------------------------------------------------------------------------- Key: HHH-6624 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6624 Project: Hibernate Core Issue Type: Bug Components: envers Reporter: Gail Badner Fix For: 4.0.0.next This will probably be fixed by switching from XAPool to ironjacama. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

3
13
0 / 0

[Hibernate-JIRA] Created: (HHH-6552) Map returned by MetadataImpl.getImports() does not include entries for unqualified entity names

by Gail Badner (JIRA)

Map returned by MetadataImpl.getImports() does not include entries for unqualified entity names ----------------------------------------------------------------------------------------------- Key: HHH-6552 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6552 Project: Hibernate Core Issue Type: Bug Reporter: Gail Badner Assignee: Gail Badner -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

3
8
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues February 2012