API differences in Hibernate ORM 5.1 vs 5.3
by Gail Badner
Hi,
There were lots of differences in the compatibility report, so as a first
step, I've excluded packages/classes that I considered SPI, internal, or
"grey area". This reduced the the differences to a more manageable amount.
You can see a summary of the incompatibilities along with suggested
mitigation at [1].
The report is attached to [1], along with a zip with instructions for
running the report.
I believe there are some "false positives" in the report, and I have
documented them in the section, "False Positives?".
Feel free to comment on the article.
Thanks,
Gail
[1]
https://developer.jboss.org/wiki/HibernateORMBinaryCompatibilityBetween51...
2 months, 1 week
IP banned from forum
by Gunnar Morling
Hi,
Is anyone banning users from the forum? I am getting "A ban has been
issued on your IP address."
I don't think banning by IP is a good strategy as many users will have
dynamic IPs from their hoster's shared pool, so it's a random game to
hit an IP previously banned due to some other user's spam.
Thanks,
--Gunnar
2 months, 1 week
New CI machine preview
by Sanne Grinovero
You're all welcome to play with http://54.225.162.168/
however please keep these in mind:
- it's not the final machine: don't put too much effort in creating
nice build scripts as we'll reset it to clean state soon. We *might*
be able to store jobs defined so far, but we might choose not to.
- domain name should be coming: ci.hibernate.org ..not sure when, got
no replies so far from.
- authentication: just click on login, it will use OAuth2 to request
your identity via your GitHub account. Permissions to create new jobs,
edit existing jobs, run a build manually depend on your github account
be part of the Hibernate organization (or not, in which case you have
read only status)
At this stage I'd like to get a feeling if the hardware is powerful
enough, and also we need to select which other plugins we want to use,
I'm looking especially to:
- static analysis reports
- pull requests integration
both are relatively undefined, we can of course start simple and
improve later.. just checking this fits basic needs now.
Sanne
4 months, 3 weeks
Using Panache without Quarkus
by Gunnar Morling
Hi,
An interesting question came up during the Quarkus meet-up with Harald
Pehl here in Hamburg last night: could Panache also be used without
Quarkus, e.g. within a WildFly application?
Any plans to enable that?
Thanks,
--Gunnar
6 years
DB2 support in Hibernate RX
by Sanne Grinovero
Hi all,
Andy Guibert (IBM) is creating a reactive driver to access DB2, based
on the VertX APIs.
The new driver is not fully complete yet but I believe it might be in
good enough status to experiment with its integration in Hibernate RX.
An overview of its status can be found here:
- https://github.com/orgs/eclipse-vertx/projects/1
Andy has been contributing on Quarkus as well: don't hesitate to reach
out to him for any need, as I hope he'll be able to help on RX too.
Thanks,
Sanne
6 years
Hibernate Search 6.0.0.Beta5 released
by Yoann Rodiere
Hello,
We just published Hibernate Search 6.0.0.Beta5.
This release mainly changes the way the Elasticsearch backend accesses
indexes, introduces delayed commits and near-real-time queries for the
Lucene backend, and renames a few methods in the Search DSL. It also
includes upgrades to Lucene 8.4, Elasticsearch 7.6 and Hibernate ORM
5.4.12.Final.
For more information, see our blog:
https://in.relation.to/2020/02/24/hibernate-search-6-0-0-Beta5/
Yoann Rodière
Hibernate Team
yoann(a)hibernate.org
6 years
PSA: Maven users, upgrade to Maven 3.6.3 if you can
by Yoann Rodiere
Hello,
Just to warn you there are bugs in Maven 3.6.1 and below impacting the
resolution of transitive dependencies when your direct dependencies rely on
exclusions or dependency management.
In practice, I don't think it's very dangerous, as Maven has algorithms
that resolve conflicting dependencies whenever they arise. Not great to
rely on these, but they work most of the time.
However, it's bound to cause some headaches, as I recently discovered
thanks to Fabio: the maven-enforcer-plugin was (wrongly) detecting a
dependency convergence issue with Maven 3.6.1 and below, just because the
dependency management of one of our dependencies was being ignored.
So there is no rush, but for your own good, I recommend that you upgrade
your machine and CI jobs to Maven 3.6.3, and maybe even set the minimum
required version of Maven to 3.6.2 (the first version that fixes the bug)
in your POM.
The CI already uses Maven 3.6.3 by default for all jobs configured with
Maven 3.6. Jobs configured with Maven 3.5 or below will be affected by the
bug.
Cheers,
Yoann Rodière
Hibernate Team
yoann(a)hibernate.org
6 years, 1 month
api/doc suggestions
by Max Rydahl Andersen
Heya,
While working on Quarkus a few of us (Georgios in cc and I in
particular) been pondering on doing a guide on best approaches on
how to access data a bit more raw (i.e. raw sql, stateless season, etc.)
as we got quite a lot of feedback stating Hibernate/JPA was considered
complex in comparison to things like Spring Data and JDBC.
When you go look its as if Spring Data and JDBC copied a lot of the
patterns/access patterns we had in Hibernate before neither of those two
existed :)
Unfortunately, there are though a few gotchas I think would be great if
we could somehow improve.
Sanne suggested me to post to this list to start the conversation -
there might come some more once I get going on writing the full guide;
but wanted to get it started sooner rather than later.
### Document simplest programatic configuration
(This might just be "max is stupid" issue - please tell me :)
Trying to do a simple java main method booting Hibernate I could not
figure out with the "new" metadata API a simple way to just start
Hibernate.
What is the equivalent way to do this in new metadata api:
```
new Configuration().setProperty("hibernate.dialect",
"org.hibernate.dialect.H2Dialect")
.setProperty("hibernate.connection.url",
"jdbc:h2:./sakila")
.setProperty("hibernate.connection.username", "sa")
.buildSessionFactory();
```
Just setup dialect, give connection info and get a
sessionfactory/entitymanager ?
I found apis to start from a file containing those settings; but I
really just want a programmatic api
to use in batch script etc. without a need for external files.
### Non-documented Deprecation of `setResultTransformer()` and friends
The [approach of using
`setResultTransformer`](https://in.relation.to/2006/03/17/hibernate-32-transformers-for-hql-and-sql/)
we've had "forever" and its exactly what spring data and jdbc are using
in examples where they say data access are easier.
We want to focus and use this kind of API in our Quarkus guides to
educate this is available.
Unfortunately in Hibernate 5.2+ that api got marked [as
deprecated](https://github.com/hibernate/hibernate-orm/blob/7a51b12cbb9a3...
with no other documentation than a `@todo develop a new approach to
result transformers`.
The actual only proper reason I could find was mentioned in
https://vladmihalcea.com/hibernate-resulttransformer/ where its pointed
out that for now we couldn't do a related functional style api for this
until Hibernate 6.
The @deprecation makes all code using this in many ides get a strike
through of that code, making people think it is bad to use when it is
very much not the case.
Any chance that deprecation can either be removed or at least documented
to be less scary/more informative ?
(I'll happily make a PR if can be pointed to the new better api?)
### doWork missing on stateless session
In similar vein `.connection()` on stateless session is marked as
deprecated with [no alternative nor actual
docs/info](https://github.com/hibernate/hibernate-orm/blob/master/hiberna....
on Session the alternative is `doWork`. Any reason why that api isn't
available on stateless session ?
Here again, the ask is so we can educate and point people to use
statelessSession rather than dropping Hibernate fully and from that
api if needed go do `.doWork()` rather than refer to deprecated
`.connection()`
Thanks,
/max
https://xam.dk/about
6 years, 1 month
Hibernate ORM : format of the version logged on boot
by Sanne Grinovero
It's minor cosmetics, but I'd like to change the format of the message
we log on boot.
Currently we have:
INFO [org.hib.Version] HHH000412: Hibernate Core {5.4.11-SNAPSHOT}
I would like to change it into:
INFO [org.hib.Version] HHH000412: Hibernate ORM core version 5.4.11-SNAPSHOT
in particular:
- to remove the "{}" wrapping around the number
- add "ORM"
- lowercase "core" and add "version"
Looks good? It would be more consistent with our own project
naming/branding, and with the format of similar messages being logged
by other popular libraries.
Thanks,
Sanne
6 years, 1 month
