February 2018 - hibernate-dev - Jboss List Archives

ORM DDL doesn't reflect BV constraints with validation mode CALLBACK

by Gunnar Morling

Hi, If the JPA validation mode is set to CALLBACK, BV constraints such as @NotNull, @Size etc. are not reflected in the DDL created by ORM. Instead, in TypeSafeActivator, the BV constraints are only considered for DDL if the validation mode is DDL or AUTO [1]. CALLBACK is the safe way to ensure BV is invoked by JPA (instead of silently ignoring it if no BV provider is present), so it's the setting I usually recommend. I think constraints should also be propagated to DDL in this mode, so I'm wondering whether there a specific reason for the current behaviour or wether we can change it? Thanks, --Gunnar [1] https://github.com/hibernate/hibernate-orm/blob/master/hibernate-core/src...

7 years, 2 months

5
27
0 / 0

Support for entities without default constructor

by Vlad Mihalcea

Hi, I realized that we could allow users to define entities without a default constructor. For Kotlin, which supportsdefault values, this could be beneficial. There is some info about how we could do that in this using Objenesis in the following Spring issue: https://jira.spring.io/plugins/servlet/mobile#issue/SPR-10594 Let me know what you think, Vlad

7 years, 2 months

2
3
0 / 0

Could we have a Hibernate 5.3 compatibility layer that includes the ORM 5.1 Hibernate Session class

by Scott Marlow

WildFly would like to have a version of 5.3+, that is compatible with ORM 5.1, with regard to the org.hibernate.session changes (including mapping of exceptions thrown, so that the same exceptions are thrown). Is it even possible to have an extra org.hibernate.Session interface + impl (bridge) that matches the same session included in 5.1? The impl would delegate to the real underlying org.hibernate.Session impl classes and also wrap thrown exceptions, so that Hibernate 5.1 native ORM apps, continue to work without code changes Or something like that. I could see how some users wouldn't want to use the compatibility layer to avoid extra overhead, so in WildFly, we would have to make that possible also. What do you think? We would need something similar in ORM 6.0+ that is also compatible with 5.1, if this is possible. Scott

7 years, 2 months

3
8
0 / 0

Jenkins updates tomorrow

by Davide D'Alto

Hi, I'm planning to update Jenkins tomorrow, it should painless but, just in case, expect possible disruptions. Cheers, Davide

7 years, 2 months

2
3
0 / 0

ORM documentation info hibernate.org

by Steve Ebersole

Now that the hibernate.org infrastructure supports doc versions, should we remove the version drop-down from the info pages? Vlad I know you spent some time adding that; what are your thoughts?

7 years, 2 months

4
4
0 / 0

Some insight about HHH-12101 / remove HQL-style positional parameters

by Laurent Almeras

Hi, Testing Hibernate 9.3.0.Beta2, I run into this issue: =============== Cannot define positional and named parameterSpecs : select queuedTaskHolder from org.iglooproject.jpa.more.business.task.model.QueuedTaskHolder queuedTaskHolder where queuedTaskHolder.status in (:x1_0, :x1_1, :x1_2, :x1_3) and queuedTaskHolder.queueId = ?2 =============== Hibernate complains that query contains both named and positional parameters (note that this query use to work on Hibernate 5.2.x). This new behavior is linked to: * this commit: https://github.com/hibernate/hibernate-orm/commit/5e0274adbbd3e0aa3092c29... * this issue: https://hibernate.atlassian.net/browse/HHH-12116 * and this parent issue: https://hibernate.atlassian.net/browse/HHH-12101 I also find that you already talk about this behavior on this same mailing-list: http://lists.jboss.org/pipermail/hibernate-dev/2016-September/015460.html I think that allowing this behavior was not a good idea, so I don't have any hope that you consider this as a bug. But I think it should be noticed in the release note (http://in.relation.to/2018/01/18/hibernate-orm-530-beta1-release/) or in this ticket (https://hibernate.atlassian.net/browse/HHH-12101) as a side-effect. On my side, I run in this issue because I use QueryDSL-jpa, and the query I give as an example is buggy because it mixes a IN statement (named parameter) dans an EQUAL statement (positional parameter). Is there anyone following both Hibernate and QueryDSL here that is already aware or working on this issue ? Thanks Laurent Almeras

7 years, 2 months

2
2
0 / 0

Hibernate Search 5.9.0.Final released

by Yoann Rodiere

Hello, We just published 5.9.0.Final, the first stable release in the 5.9 branch. This release brings a brand-new JSR-352 integration for mass indexing, WildFly feature packs, and better integration to modular environments. Check out our blog for more information about this release: http://in.relation.to/2018/02/07/hibernate-search-5-9-0-Final/ -- Yoann Rodiere yoann(a)hibernate.org / yrodiere(a)redhat.com Software Engineer Hibernate NoORM team

7 years, 2 months

1
0
0 / 0

Hibernate ORM 5.2.13.Final has been released

by andrea boriero

*For details:http://in.relation.to/2018/02/07/hibernate-orm-5213-final-release <http://in.relation.to/2018/02/07/hibernate-orm-5213-final-release>*

7 years, 2 months

1
0
0 / 0

Starting 5.2.13 release

by andrea boriero

*Please do not push anything to 5.2 branch.Thanks,Andrea*

7 years, 2 months

1
0
0 / 0

Repackaging dependencies with Hibernate

by Vlad Mihalcea

Hi, This Hibernate forum question provides a good point: https://discourse.hibernate.org/t/hibernate-in-weblogic-has-a-conflicting... Frameworks like EclipseLink and Spring ( https://twitter.com/starbuxman/status/960854907854249986 ) repackage dependencies to avoid the issue when the user needs a different library version (ANTLR 3.3) in their Classpath. Is it possible to do so for Hibernate ORM? Is there any license issues that would prevent doing it? Vlad

7 years, 2 months

3
4
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-dev February 2018