Re: [hibernate-dev] JPA Events

Hi guys, any idea how to overcome this? Like I said, when I create my JPA listener with the following: @Override public void onPreUpdateCollection(PreCollectionUpdateEvent event) { super.touchForUpdate(event.getAffectedOwnerOrNull()); updateCollectionOwner(event); } private void updateC

[hibernate-dev] Problem with releasing 5.1.13.Final

I am able to build the documentation using Andrea's suggestion and now I'm struggling with gradle. I released the staging repository on nexus last night to make a deadline. I also updated the version in build.gradle to 5.1.14-SNAPSHOT, which was probably a mistake. Today I went back to build the

Re: [hibernate-dev] Cannot build documentation in 5.1 branch

Andrea, Your suggestion to use " https://www.oasis-open.org/docbook/xml/5.0b5/dtd/docbook.dtd"; worked great. Thanks! Gail On Tue, Mar 20, 2018 at 9:57 AM, Gail Badner wrote: > Sorry, I missed that PR somehow. It will get into 5.1.14 for sure. > > On Tue, Mar 20, 2018 at 5:27 AM, Sanne Grinov

Re: [hibernate-dev] Async JDBC proposal

The slides shown are from last year. Somehow that blog still promotes that ADBA is somehow a replacement of JDBC, instead of a separate API that will exist next to JDBC. Mark On 2018-03-20 21:23, Gunnar Morling wrote: > I don't know whether that's the resource Emmanuel meant to link to, > but i

Re: [hibernate-dev] Async JDBC proposal

I don't know whether that's the resource Emmanuel meant to link to, but it's the most recent presentation on the topic I'm aware of: https://blogs.oracle.com/java/jdbc-next%3a-a-new-asynchronous-api-for-connecting-to-a-database --Gunnar 2018-03-20 19:09 GMT+01:00 Mark Rotteveel : > Minor ni

Re: [hibernate-dev] Async JDBC proposal

Minor nitpick, the proposed asynchronous database API (ADBA) is not part of JDBC, nor does it rely on or use JDBC (or at least implementations doing that wouldn't be truely async). Mark PS Could you send the actual link? On 2018-03-20 12:01, Emmanuel Bernard wrote: > Nothing really new for peo

Re: [hibernate-dev] [in.relation.to] Only display post summary in list pages

On Tue, Mar 20, 2018 at 6:18 PM, Sanne Grinovero wrote: > Maybe you could improve it by forcing a "cut" before images, code snippets > and such > Made the extraction routine more Emmanuel compliant. There's still this weird post by Vlad on the front page but I prefer to keep the logic as it is

Re: [hibernate-dev] [in.relation.to] Only display post summary in list pages

Very nice! This should also mitigate some of the SEO problems. I see e.g. Emmanuel tends to have long unstructured starts - http://staging.in.relation.to/emmanuel-bernard/index.html Maybe you could improve it by forcing a "cut" before images, code snippets and such? Thanks, Sanne On 20 March

Re: [hibernate-dev] Cannot build documentation in 5.1 branch

Sorry, I missed that PR somehow. It will get into 5.1.14 for sure. On Tue, Mar 20, 2018 at 5:27 AM, Sanne Grinovero wrote: > Hi Gail, > > I was also hoping this would be included in the next 5.1, it was flagged > to get your attention: > - https://github.com/hibernate/hibernate-orm/pull/2151 >

Re: [hibernate-dev] [in.relation.to] Only display post summary in list pages

Great initiative, always wanted to have this! Can you send a PR for debezium.github.io, too ;) 2018-03-20 16:02 GMT+01:00 Guillaume Smet : > On Tue, Mar 20, 2018 at 2:23 PM, Yoann Rodiere > wrote: > > > It's definitely better. There are a few drawbacks, such as the summary > not > > displaying f

Re: [hibernate-dev] [in.relation.to] Only display post summary in list pages

On Tue, Mar 20, 2018 at 2:23 PM, Yoann Rodiere wrote: > It's definitely better. There are a few drawbacks, such as the summary not > displaying for older, non-asciidoctor posts, but the list was barely usable > without your change, so I think it's still an improvement. > I improved the extractio

Re: [hibernate-dev] [in.relation.to] Only display post summary in list pages

It's definitely better. There are a few drawbacks, such as the summary not displaying for older, non-asciidoctor posts, but the list was barely usable without your change, so I think it's still an improvement. +1 to merge, thanks for working on this! One improvement we could work on is to add an e

[hibernate-dev] [in.relation.to] Only display post summary in list pages

Hi, It's been bugging me for a while and I took some time this morning to do some changes to the post list pages of the blog. We currently display the whole articles whereas I thought it would be better to only display a summary of them and get people to the full article with a button. I pushed

Re: [hibernate-dev] Cannot build documentation in 5.1 branch

Hi Gail, I was also hoping this would be included in the next 5.1, it was flagged to get your attention: - https://github.com/hibernate/hibernate-orm/pull/2151 On 20 March 2018 at 11:34, andrea boriero wrote: > Hi Gail, > > I have tried and I'm facing the same failure what I noticed is that >

Re: [hibernate-dev] [HV] Retiring HibernateValidatorContext#parameterNameProvider()

On Tue, Mar 20, 2018 at 1:06 PM, Gunnar Morling wrote: > This is a spec-level API, defined in ValidatorContext: > > https://github.com/beanvalidation/beanvalidation- > api/blob/master/src/main/java/javax/validation/ValidatorContext.java#L77 > > So unless we change the rules (there might be so

Re: [hibernate-dev] [HV] Retiring HibernateValidatorContext#parameterNameProvider()

This is a spec-level API, defined in ValidatorContext: https://github.com/beanvalidation/beanvalidation-api/blob/master/src/main/java/javax/validation/ValidatorContext.java#L77 So unless we change the rules (there might be some leeway now when formalizing compat rules for Jakarta EE), we cannot

Re: [hibernate-dev] Cannot build documentation in 5.1 branch

Hi Gail, I have tried and I'm facing the same failure what I noticed is that changing http://docbook.org/xml/5.1/dtd/docbook.dtd"; ..> to https://www.oasis-open.org/docbook/xml/5.0b5/dtd/docbook.dtd"; ..> seems solving the issue. On 20 March 2018 at 05:16, Gail Badner wrote: > I'm in the proc

Re: [hibernate-dev] Hibernate OGM mapping for "server side Hibernate Search" via Infinispan Remote

On 20 March 2018 at 10:50, Emmanuel Bernard wrote: > I think treating the client side HSearch input and transparently push it > down is a recipe for disaster. Looks cool on paper until you have > divergence between HSearch proper and Infinispan's or whatever > Infinispan exposes. > ​Looks like w

Re: [hibernate-dev] [HV] Retiring HibernateValidatorContext#parameterNameProvider()

Let's hypotethically assume that some scenario needs this. I'm thinking of an application which as different compilation units, so some module might have been compiled with different conventions and need different name resolvers. Would you enforce such a use case to use different, independently co

Re: [hibernate-dev] Async JDBC proposal

Emmanuel, is this a correct link? That one is ORM 5.1 vs. 5.3 binary compatibility analysis... I have seen [1] posted earlier today on; is this what you have in mind? I am very happy that JDBC will have an async variant; we have some plans for asynchronous persistence in Infinispan so this migh

[hibernate-dev] Async JDBC proposal

Nothing really new for people at the edge of news but a nice presentation showing how async JDBC will likely work https://docs.google.com/document/d/1jH0znbYwgvGKHC-110zcjRaXLllBsvRKw-pdHrMzRzw Emmanuel ___ hibernate-dev mailing list hibernate-dev@lists.

Re: [hibernate-dev] Hibernate OGM mapping for "server side Hibernate Search" via Infinispan Remote

I think treating the client side HSearch input and transparently push it down is a recipe for disaster. Looks cool on paper until you have divergence between HSearch proper and Infinispan's or whatever Infinispan exposes. So yes we could have GridDialect specific metadata information around indexi

Re: [hibernate-dev] [HV] Retiring HibernateValidatorContext#parameterNameProvider()

Can't you a priori apply your optimization and have a if ( perInstance != perFactory ) backdoor? Meaning I don't really get why you cannot apply your optimization by default and fall back to a slow codepath when the value is overridden. Emmanuel On Mon 18-03-19 17:47, Guillaume Smet wrote: >Hi, >

Re: [hibernate-dev] [HSEARCH][V6-POC] FieldBridge 2.0

If you want to have a look at the sources on Github directly, and don't want to clone the repo to have a look in your IDE, here is the paragraph listing the bridge implementations, but with links to Github sources: - ISBNBridge

[hibernate-dev] [HSEARCH][V6-POC] FieldBridge 2.0

Hello, In Search 6, we are changing the field bridge APIs to move away from Lucene dependencies. Similarly to the query DSL, this breaks backward compatibility whatever we do, so we had a look to improving the field bridge API a bit with some other changes. The result is we have three types of br