February 2012 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-4874) Embedded Objects get set to null if all its members are null

by Srinath (JIRA)

Embedded Objects get set to null if all its members are null ------------------------------------------------------------ Key: HHH-4874 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4874 Project: Hibernate Core Issue Type: Bug Components: annotations Reporter: Srinath Embedded Objects get set to null if all its members are null.i am facing this problem when i am having @Embeddable properties are null.even i creating instance in Parent class no-argument constructor.is there any other way to overcome from this issue? Thanks -- 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

11 years, 4 months

4
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3733) Introduce an annotation to disable ad-hoc null semantic of Hibernate components

by Vladimir Kovalyuk (JIRA)

Introduce an annotation to disable ad-hoc null semantic of Hibernate components ------------------------------------------------------------------------------- Key: HHH-3733 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3733 Project: Hibernate Core Issue Type: Improvement Components: core Reporter: Vladimir Kovalyuk see http://forums.hibernate.org/viewtopic.php?t=993972 For the model @Entity public class Person { private Address name = new Address(); ... @Embedded Address getAddress() {} } @Embeddable public class Address { public String getCity() {} public String getStreet() {} } the following xhtml excerpt causes NPE constantly when editing a person which address properties hasn't been filled in yet <h:inputText value="#{person.address.city}" /> I suggest introducing an annotation @Static which could be applied to Address class and lead to disabling null ad-hoc semantic on its instances. For some environments such as user interface this may be considered as the default behavior. I suggest introducing an Hibernate configuration parameter which would switch off the semantic. I would propose to consider embeddable classes as static mixins from OO design, not as just limited entities without identity. This point of view explains that embedded instance is a part of entity so it's lifecycle is the same as the entity's lifecycle. Thus constant presence of embeddable instance (property is never null) is the default behavior. Thus configuration parameter is "must have", not the thing which is "nice to have". >From the other hand null ad-hoc semantic is like dynamic mixins. So it would be nice to have a @Dynamic annotation to force this semantic for some components. -- 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

11 years, 4 months

4
6
0 / 0

[Hibernate-JIRA] Created: (HHH-2308) Adjusting the Outer Join Predicate using Criteria Query

by Ben Grant (JIRA)

Adjusting the Outer Join Predicate using Criteria Query ------------------------------------------------------- Key: HHH-2308 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2308 Project: Hibernate3 Type: New Feature Components: query-criteria Versions: 3.2.1 Environment: Linux Using MS SQLServer Reporter: Ben Grant I have two tables Table A ||Col_1||Col_2|| |London| UK | |Liverpool| UK | | New York | USA | Table B ||Col_1||Col_2|| Col_3|| | UK | Europe | 0 | USA | Americas | 1 Using the Criteria class, Restriction Class and FetchMode, Hibernate manages to create a query that looks like this select distinct top 2000 this_.Col_1 as y0_, TableB3_.Col2 as y1_ from TableA this_ left outer join TableB TableB3_ on this_.Col_2= TableB3_.Col_1 where TableB3_.Col_3=1 When really i need the query to be like this select distinct top 2000 this_.Col_1 as y0_, TableB3_.Col2 as y1_ from TableA this_ left outer join TableB TableB3_ on this_.Col_2= TableB3_.Col_1 AND TableB3_.Col_3=1 currently their isn't any know way for hibernate to adjust or apply filters within the join clause. -- 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

11 years, 4 months

12
27
0 / 0

[Hibernate-JIRA] Created: (HHH-6420) SQL Server dialect is broken

by Tomaz Cerar (JIRA)

SQL Server dialect is broken ---------------------------- Key: HHH-6420 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6420 Project: Hibernate Core Issue Type: Task Components: query-sql Affects Versions: 4.0.0.Beta3, 4.0.0.Beta2, 4.0.0.Beta1 Environment: AS7 hibernate 4 beta1/beta2 SQL Server 2008 R2 Reporter: Tomaz Cerar SQLServer dialect is broken for boolean fields When it tries to create table for entity that has boolean attribute it fails as sql server does not know of type "boolean" it has type bit I have created fix for it https://github.com/hibernate/hibernate-core/pull/124 but I have not tested it on older versions of sql server than 2008 -- 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

11 years, 4 months

6
11
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-791) Make it easier to setup Infinispan with partially generated dynamic configurations

by Sanne Grinovero (JIRA)

Make it easier to setup Infinispan with partially generated dynamic configurations ---------------------------------------------------------------------------------- Key: HSEARCH-791 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-791 Project: Hibernate Search Issue Type: New Feature Components: integration Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 4.0 Inspired by: http://community.jboss.org/message/613152#613152 Storing the index in Infinispan currently requires a cacheloader in the Infinispan configuration, it would be very easy if this could be the datasource used by Hibernate core. Also it would be nice if we could reuse the CacheManager from the Hibernate Second level cache, if this happens to be 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

11 years, 4 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-736) Provide examples to configure the Infinispan backend to persist state on Hibernate's Datasource

by Sanne Grinovero (JIRA)

Provide examples to configure the Infinispan backend to persist state on Hibernate's Datasource ----------------------------------------------------------------------------------------------- Key: HSEARCH-736 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-736 Project: Hibernate Search Issue Type: Improvement Components: documentation Reporter: Sanne Grinovero Fix For: 3.4.1, 3.5 We need to clearly document something like what I described on the Infinispan forums: http://community.jboss.org/thread/152424 but instead of configuring a new JDBC connection "from scratch" we should show how to reuse Hibernate core's provided connections. -- 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

11 years, 4 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HV-523) Hibernate validator must be a fragment of javax.validation and should easily plug with extenders

by Charlie Mordant (JIRA)

Hibernate validator must be a fragment of javax.validation and should easily plug with extenders ------------------------------------------------------------------------------------------------ Key: HV-523 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-523 Project: Hibernate Validator Issue Type: Bug Components: engine Affects Versions: 4.2.0.Final Environment: Osgi Reporter: Charlie Mordant Priority: Blocker Attachments: orthank-sample.zip It's for now about impossible to plug hibernate validators in an osgi environment with extenders like spring-dm. I've found multiple blog entries explaining the bootstrapping issue of validation api. http://katastrophos.net/magnus/blog/2009/07/18/having-fun-with-jsr-303-be... http://www.jasonday.net/content/jsr-303-bean-validation-and-spring-mvc-sl... I'm not an OSGI expert, so I think you'll better understand the problem than me. The problem remains that validation api is not usable in a valuable osgi environment for now (spring-dm, blueprint...). Regards, Charlie Thank you to investigate on this problem, I give you a sample project in order to test it ('mvn pax:provision -Dframework=equinox' in order to run the server). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

3
10
0 / 0

[Hibernate-JIRA] Created: (HHH-5695) Hibernate complains about an unknown mappedBy property when mapping a bidirectional OneToOne relation with a derived identifier

by Pascal Thivent (JIRA)

Hibernate complains about an unknown mappedBy property when mapping a bidirectional OneToOne relation with a derived identifier ------------------------------------------------------------------------------------------------------------------------------- Key: HHH-5695 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5695 Project: Hibernate Core Issue Type: Bug Components: entity-manager Affects Versions: 3.6.0, 3.6.0.CR2, 3.6.0.CR1, 3.5.6, 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 Environment: Hibernate 3.5+, any database. Reporter: Pascal Thivent Attachments: HHH-5695.zip I have a OneToOne mapping between Foo and Bar where Bar uses a derived identifier. So Bar is the "dependent" entity and has a single primary key attribute which is mapped by the relationship attribute (i.e. using `Id` on the `OneToOne` relationship). Foo is mapped like this: {code} @Entity public class Foo { @Id @GeneratedValue private Long id; private String name; @OneToOne(mappedBy="foo", cascade=CascadeType.ALL) private Bar bar; public Long getId() { return id; } //... } {code} and Bar: {code} @Entity public class Bar { @Id @OneToOne @JoinColumn(name="BAR_ID") private Foo foo; //... } {code} This mapping is described in the section 2.4.1.2 of the JPA 2.0 specification, Example 4, case (a) and works with the RI (run {{mvn test -Peclipselink,h2}} on the attached project). However, Hibernate fails to initialize and complains about the mappedBy attribute: {code} Caused by: org.hibernate.AnnotationException: Unknown mappedBy in: com.acme.Foo.bar, referenced property unknown: com.acme.Bar.foo at org.hibernate.cfg.OneToOneSecondPass.doSecondPass(OneToOneSecondPass.java:159) at org.hibernate.cfg.Configuration.originalSecondPassCompile(Configuration.java:1686) at org.hibernate.cfg.Configuration.secondPassCompile(Configuration.java:1393) at org.hibernate.cfg.Configuration.buildMappings(Configuration.java:1345) at org.hibernate.ejb.Ejb3Configuration.buildMappings(Ejb3Configuration.java:1477) at org.hibernate.ejb.EventListenerConfigurator.configure(EventListenerConfigurator.java:193) at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:1096) at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:278) at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:362) ... 24 more {code} Run {{mvn test}} to reproduce. -- 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

11 years, 4 months

6
20
0 / 0

[Hibernate-JIRA] Created: (HHH-6361) Collection events may contain wrong stored snapshot after merging a detached entity into the persistencecontext

by Erik-Berndt Scheper (JIRA)

Collection events may contain wrong stored snapshot after merging a detached entity into the persistencecontext --------------------------------------------------------------------------------------------------------------- Key: HHH-6361 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6361 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.6.5 Reporter: Erik-Berndt Scheper Priority: Minor After the merge process, driven by the {{DefaultMergeEventListener}}, it can happen that the Hibernate collection events contain references to an incorrect stored snapshot. This is both the case for the {{PersistentCollection}} and the {{CollectionEntry}}, as returned by {{session.getPersistenceContext().getCollectionEntry(persistentCollection)}} By itself, this looks like a minor issue. However, this leads to severe problems when Envers is used. This bug causes HHH-6349, which results in inconsistent (invalid) audit trails and possibly AssertionFailures when the {{ValidityAuditStrategy}} is used. I am pretty sure the same bug exists in the 4.0.0 Betas, since I have an Envers testcase for testng (3.6 branch) and junit4 (master) which both exhibit the same behaviour. However, I haven't looked in the changes in the merge process in 4.0.0 betas (compared to 3.6.x). I am currently preparing a testcase for the Hibernate testsuite (complimentary to the Envers testcases) together with a suggested fix, but this takes a bit more work than I anticipated. -- 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

11 years, 4 months

5
8
0 / 0

[Hibernate-JIRA] Created: (HHH-5436) different lock deepness for joined subclass

by kakusi kakusi (JIRA)

different lock deepness for joined subclass ------------------------------------------- Key: HHH-5436 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5436 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.3.2, 3.2.5 Environment: Oracle 10g Reporter: kakusi kakusi Hi, we use hibernate, oracle and pessimstic locking, to avoid concurrent modification through different threads. This worked fine for a while. But now we sometimes get deadlocks. We analyzied and found the cause: we produced locks with different deepnesses for objects of type joined subclass. An example for our kind of mapping: {noformat} <class name="TraceObject" table="TraceObjects"> <cache usage="read-write" /> <id name="objectId" column="objectId" type="long"> <generator class="native"> <param name="sequence">TraceObjectsSeq</param> </generator> </id> <timestamp name="dbVersionControl" /> ... </class> <joined-subclass name="VehicleObject" table="VehicleObjects" extends="TraceObject"> <key column="id" /> ... </joined-subclass>{noformat} Method: {{session.get(Class clazz, Serializable id, LockMode lockMode);}} Created Select-Statement: {{SELECT traceobjec0_.objectId ... FROM TraceObjects traceobjec0_ LEFT OUTER JOIN VehicleObjects traceobjec0_3_ ON traceobjec0_.objectId=traceobjec0_3_.id WHERE traceobjec0_.objectId=? FOR UPDATE;}} Effect: This locks the relevant data in table TraceObjects and joined table VehicleObjects. Method: {{session.get(Class clazz, Serializable id);}} {{session.lock(Object object, LockMode lockMode);}} Created Select-Statement: {{select traceobjec0_.objectId ... from TraceObjects traceobjec0_ left outer join VehicleObjects traceobjec0_3_ on traceobjec0_.objectId=traceobjec0_3_.id where traceobjec0_.objectId=?;}} {{select objectId from TraceObjects where objectId =? for update;}} Effect: This only locks the relevant data in table TraceObjects. We think this is a bug, because all techniques to lock should create the same lock type (only locking the parent table). -- 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

11 years, 4 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues February 2012