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, 4 weeks
Should we support out of date non-LTS Java versions?
by Sanne Grinovero
Hi all,
I just tested if we still need the dependency to
'javax.activation:javax.activation-api:1.2.0' from Hibernate ORM /
master, as I was suspecting the original reasons to add it might be
out of date.
I guessed almost right, as it turns out we don't need this dependency
for Java 11, nor it was ever needed for Java 8 either: it was
introduced to solve a specific Java 9 compatibility issue.
I verified it's still needed for Java 9 compatibility. Personally that
makes me think I'd rather remove the dependency, people should no
longer use Java 9;
Java 9 has been "out of support" since a while now: I expect people to
either be on the latest stable release Java 11 - or on the previous
stable release aka Java 8 (others might be toying with 12 and/or 13
but that's not relevant).
Clearly since we have no more 5.x minor releases planned, I'm thinking
of dropping a JVM version in a micro (!) - but considering this is an
unsupported non-LTS JVM I'm not considering this to be an outrageous
idea as we'd normally treat such a suggestion.
Please don't take this as nitpicking about removing a single
dependecy: that's easy enough for people to ignore and workaround by
re-adding it explicitly; it's more important to focus on us creating a
clear policy for the future.
Can we establish how we'll treat support for any other future
non-Long-Term-Support JVM version?
Next time we might have a more tricky issue, and I think we should
make our intentions and policy clear so to have freedom to drop
support for experimental Java releases as we see fit, provided they
are out of date.
I couldn't test JDK 10 - but that doesn't matter as the details of
this specific issue are irrelevant to the main point of agreeing on a
general policy.
Comments?
Thanks,
Sanne
7 years, 1 month
Upgrading Hibernate Causes null index column for collection error for List
by Amit Shah
We are trying to upgrade hibernate from version 4.3.5 to 5.4.0. With this
the jpa version also changes from hibernate-jpa-2.1 to jpa-2.2. After the
upgrade we get the following error when using the List<> collection with
@OrderColumn
"javax.persistence.PersistenceException: org.hibernate.HibernateException:
null index column for collection"
It is a unidirectional one-to-mapping with following annotations
@Entity@Table(name = "DS_GENERIC")@PrimaryKeyJoinColumn(name =
"DSG_DS_ID")public class GenericConnection extends
DataSourceConnection {
@OneToMany(cascade = ALL, orphanRemoval = true, fetch = FetchType.EAGER)
@JoinColumn(name = "DSC_DS_ID", nullable = false)
@OrderColumn(name = "DSC_ORDER", updatable = false, insertable = false)
List<Credentials> credentials = new ArrayList<>();
}
@Entity@Table(name = "DS_CREDENTIALS")public class Credentials {
@Id
@GeneratedValue(generator = "uid-generator")
@Column(name = "DSC_ID", updatable = false)
private Long id;
//...}
The below test code fails
//construct the connection object with credentials
entityManager.persist(connection);
entityManager.find(DataSourceConnection.class, id); //this call fails
with the above error
Note that this code worked fine with hibernate 4.3.5 and one workaround
that also works is converting List to Set as below
@OneToMany(cascade = ALL, orphanRemoval = true, fetch =
FetchType.EAGER)@JoinColumn(name = "DSC_DS_ID", nullable =
false)@OrderBy("DSC_ID")Set<Credentials> credentials = new
HashSet<>();
I do not understand the root cause of this failure. Any inputs would be
appreciated.
Thanks.
P.S - I have posted this query on stackoverflow too
<https://stackoverflow.com/questions/54686603/upgrading-hibernate-causes-n...>
7 years, 1 month
JDK 12: First Release Candidate available
by Rory O'Donnell
Hi Sanne,
**OpenJDK builds *- JDK 12 Early Access build 32 **is now available **at
: - jdk.java.net/12/*
**JDK 12: First Release Candidate [1]**
* Per the JDK 12 schedule [2], we are now in Release Candidate Phase.
* The stabilization repository, jdk/jdk12, is open for P1 bug fixes
per the JDK Release Process (JEP 3) [3].
* All changes require approval via the Fix-Request Process [4].
*
Release note additions since last email
o
Build 31 - can_pop_frame and can_force_early_return capabilities
are disabled if JVMCI compiler is used (JDK-8218025
<https://bugs.openjdk.java.net/browse/JDK-8218025>) The JVMTI
|can_pop_frame| and |can_force_early_return| capabilities are
disabled if a JVMCI compiler (like Graal) is used. As a result
the corresponding functionality (|PopFrame| and
|ForceEarlyReturnXXX| functions) is not available to JVMTI
agents. This issue is being fixed via JDK-8218885
<https://bugs.openjdk.java.net/browse/JDK-8218885>
[https://bugs.openjdk.java.net/browse/JDK-8218885
<https://bugs.openjdk.java.net/browse/JDK-8218885>].
o Build 28: JDK-8212233
<https://bugs.openjdk.java.net/browse/JDK-8212233> : javadoc
fails on jdk12 with "The code being documented uses modules but
the packages defined in $URL are in the unnamed module."
* Changes in this build.
<http://hg.openjdk.java.net/jdk/jdk12/log?rev=reverse%28%22jdk-12%2B31%22%...>
**OpenJDK builds *- JDK 13 Early Access build 8 is **now available **at
: - jdk.java.net/13/*
* These early-access, open-source builds are provided under the
o GNU General Public License, version 2, with the Classpath
Exception <http://openjdk.java.net/legal/gplv2+ce.html>.
* Release Notes updates
* Build 8
o GraphicsEnvironment.getCenterPoint()/getMaximumWindowBounds()
are unified across the platforms (JDK-8214918
<https://bugs.openjdk.java.net/browse/JDK-8214918>)
o The experimental FIPS 140 compliant mode has been removed from
the SunJSSE provider. (JDK-8217835
<https://bugs.openjdk.java.net/browse/JDK-8217835>)
* Build 7
o Change DOM parser to not resolve EntityReference and add Text
node with
DocumentBuilderFactory.setExpandEntityReferences(false)
(JDK-8206132 <https://bugs.openjdk.java.net/browse/JDK-8206132>)
* Build 6
o Base64.Encoder and Base64.Decoder methods can throw
OutOfMemoryError (JDK-8210583
<https://bugs.openjdk.java.net/browse/JDK-8210583>)
* Changes in this build
<http://hg.openjdk.java.net/jdk/jdk/log?rev=reverse%28%22jdk-13%2B7%22%3A%...>
* FOSS Bugs fixed in recent builds
o Build 6 : JDK-8216970
<https://bugs.openjdk.java.net/browse/JDK-8216970> : condy
causes JVM crash
o Build 7: JDK-8215577
<https://bugs.openjdk.java.net/browse/JDK-8215577> : Remove
javadoc support for HTML 4
Rgds,Rory
[1]
https://mail.openjdk.java.net/pipermail/jdk-dev/2019-February/002623.html
[2] http://openjdk.java.net/projects/jdk/12/#Schedule
[3] http://openjdk.java.net/jeps/3
[4] http://openjdk.java.net/jeps/3#Fix-Request-Process
--
Rgds,Rory O'Donnell
Quality Engineering Manager
Oracle EMEA , Dublin, Ireland
7 years, 1 month
Goodbye HipChat, hello Zulip!
by Yoann Rodiere
Hi,
As you may already know, HipChat Cloud will cease to operate in about ten
days. We need a replacement for our real-time chat, and we chose Zulip.
An instance has been set up and configured. You can sign up and login with
the link below; please do!
https://hibernate.zulipchat.com/
Zulip takes an opinionated approach to chat, so you are encouraged to read
this:
https://hibernate.zulipchat.com/help/about-streams-and-topics
Please keep in mind that Zulip will only subscribe you to the
hibernate-user stream by default, so you need to subscribe explicitly to
other streams you are interested in (hibernate-orm-dev, ...).
If you need to test Zulip features, you can use the "sandbox" stream, which
is there exactly for this purpose.
If you have any questions, please let me know - on Zulip, of course. Or if
you have trouble connecting, you can always send me an email. Please avoid
HipChat or Gitter, though, for obvious reasons ;)
Thanks,
Yoann Rodière
Hibernate NoORM Team
yoann(a)hibernate.org
7 years, 1 month
Survey for Research on Lambda Expressions
by FERNANDO PETRULIO
Dear Hibernate devs,
I'm a researcher from UZH and my team and I are conducting a study on
Lambda Expressions and Functional Interface in APIs.Hibernate project is
one of our targets and we would gather some information and opinion about
this topic from you. So I would be really happy if you filled the survey at
the following link:
https://www.surveygizmo.com/s3/4781913/704005e13cdb
Kind Regards, Fernando Petrulio.
7 years, 1 month
