November 2012 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] (HV-652) Update JavaDoc stylesheet when building with Java 7

by Gunnar Morling (JIRA)

11 years, 11 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HV-467) Complete handling of default group sequence re-definitions for method validation

by Gunnar Morling (JIRA)

Complete handling of default group sequence re-definitions for method validation -------------------------------------------------------------------------------- Key: HV-467 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-467 Project: Hibernate Validator Issue Type: New Feature Components: engine Reporter: Gunnar Morling Fix For: 4.x In the context of method validation redefined default group sequences are currently considered only, when the evaluated bean type itself re-defines the default group sequences (so re-definitions up in the hierarchy are ignored). This behaviour should be aligned with the logic used for "standard" bean validation. -- 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, 11 months

3
19
0 / 0

[Hibernate-JIRA] Created: (HV-579) Investigate whether it makes sense to load meta data for method validation lazily

by Gunnar Morling (JIRA)

Investigate whether it makes sense to load meta data for method validation lazily --------------------------------------------------------------------------------- Key: HV-579 URL: https://hibernate.onjira.com/browse/HV-579 Project: Hibernate Validator Issue Type: Improvement Components: engine Affects Versions: 4.3.0.Beta1 Reporter: Gunnar Morling Fix For: 5.x Currently the entire meta data (bean as well as method validation related) is loaded upon validation. In order to increase runtime performance as well as to save memory, it might make sense to load method validation related meta data only in the method validation case. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

2
1
0 / 0

[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, 11 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, 11 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, 11 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, 11 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, 11 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, 11 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, 11 months

3
10
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues November 2012