Blaze-Persistence 1.2.0-Alpha5 Release

Blaze-Persistence version 1.2.0-Alpha5 was just released

By Christian Beikov on 15 March 2018

We promised you more frequent releases, and here they are! Although we said that this will be the last Alpha release for 1.2.0, we decided that we need another round since we couldn’t get everything done yet for which we already had an API. One of our main concerns was Java 9 compatibility related to split packages. So we moved a few things around and gave all modules proper Automatic-Module-Name manifest entries. We also spent quite some time on supporting REST technologies and providing examples which, but it was worth it! Overall, we have quite a few nice features for you

  • #323 Support for fetch strategies for non-correlated mappings

  • #51 Add method to enable query result caching

  • #450 Updatable attributes by default now allow all known subtypes that don’t introduce cycles, rather than requiring the user to specify all allowed subtypes

  • #209 Support for compiling and running on JDK 9 & 10 & 11-EA

  • #538 Spring Data 2.0 and DeltaSpike 1.8 support

  • #535 Spring Data Rest integration offering first class keyset pagination support

  • #496 DeltaSpike Data Rest integration offering pagination support similar to what Spring Data offers

  • #536 Support for positional parameters

and lots of bugfixes, most notably

  • #417 EntityViewManager was wrongly passed to @PostCreate Java 8 default methods in interfaces

  • #537 Fix illegal Entity-To-Association-Id rewrite

  • #518, #519, #521 Fix a few problems that occur when using Hibernate specific features

  • #514 Fix in cyclic join detection that happened when using multiple join nodes in ON clause

A big thanks is going out to Jan-Willem Gmelig Meyling for all the tests and fixes he provided in the last few weeks. We very much appreciate the contribution!

We advise you to update to 1.2.0-Alpha5 as soon as possible to prevent getting hit from the Entity-To-Association-Id rewrite issue #537.

There are a few features left that already have a partial implementation or are present in APIs that we are going to finish for the final release of 1.2.0. For future versions, we intend to follow our time based release model more strictly.

Stay tuned, the final 1.2.0 release that was originally targeted for end of February is rescheduled for the end of April.

announcement release
comments powered by Disqus