Default access type and MappedSuperclass
by Guillaume Smet
Hi,
We recently had this issue opened about us not choosing the right access
type for a mapped super class:
https://hibernate.atlassian.net/browse/HHH-12938 .
Hibernate currently base the access type decision on the sole placement of
the @Id annotation, which, in the case of a @MappedSuperclass might not be
defined (this is the OP's case).
I closed the issue explaining what we do and pointing a workaround but the
OP rightfully replied with the JPA spec saying "The default access type of
an entity hierarchy is determined by the placement of mapping annotations
on the attributes of the entity classes and mapped superclasses of the
entity hierarchy that do not explicitly specify an access type".
I'm wondering if we should also consider the @Column annotations placement
if there is no @Id annotation.
If the answer is that it's already fixed in 6, it's all good for me :).
Thoughts?
--
Guillaume
5 years, 11 months
inSession / inTransaction
by Steve Ebersole
In tests we find our `#inSession` and `#inTransaction` methods very
useful. Which got me thinking that maybe we should support these on
SessionFactory directly:
public interface SessionFactory ... {
...
void inSession(Consumer<Session> action);
void inTransaction(Consumer<Session> action);
void inTransaction(Session session, Consumer<Session> action);
}
and maybe even:
public interface Session ... {
void inTransaction(Consumer<Session> action);
}
Objections?
5 years, 11 months
JDK 12 Early Access build 26 & JDK 13 Early Access builds available
by Rory O'Donnell
Hi Sanne,
Happy New Year!
*OpenJDK builds *- JDK 12 Early Access build 26 is available at
http://jdk.java.net/12/
* These early-access, open-source builds are provided under the GNU
General Public License, version 2, with the Classpath Exception
<http://openjdk.java.net/legal/gplv2+ce.html>.
* Changes since last email
o Distrust TLS server certificates anchored by Symantec Root CAs
(JDK-8207258 <https://bugs.openjdk.java.net/browse/JDK-8207258>)
o Customizing the generation of a PKCS12 keystore (JDK-8076190
<https://bugs.openjdk.java.net/browse/JDK-8076190>)
o Compact Number Formatting Support (JDK-8177552
<https://bugs.openjdk.java.net/browse/JDK-8177552>)
*OpenJDK builds *- JDK 13 - Early Access build 2 is available at
http://jdk.java.net/13/
* These early-access, open-source builds are provided under the GNU
General Public License, version 2, with the Classpath Exception
<http://openjdk.java.net/legal/gplv2+ce.html>.
* Changes in this build
<http://hg.openjdk.java.net/jdk/jdk/log?rev=reverse%28%22jdk-13%2B1%22%3A%...>
*jpackage EA builds*
* This is an early access build of JEP 343: Packaging Tool
<https://openjdk.java.net/jeps/343>, aimed at testing a prototype
implementation of jpackage, which is a new tool for packaging
self-contained Java applications along with a Java Runtime Environment.
* Please send feedback via e-mail to core-libs-dev(a)openjdk.java.net
<mailto:core-libs-dev@openjdk.java.net>
*Quality Outreach report for December 2018*
* The report for December 2018 is available here
<https://wiki.openjdk.java.net/display/quality/Quality+Outreach+report+for...>
Rgds,Rory
--
Rgds,Rory O'Donnell
Quality Engineering Manager
Oracle EMEA , Dublin, Ireland
5 years, 11 months
SAP HANA build failing for a while - does it reveal a bug?
by Guillaume Smet
Hi,
Since this build
http://ci.hibernate.org/view/ORM/job/hibernate-orm-master-hana-main/688/ ,
the SAP HANA build is failing consistently.
With a lot of tests failing with:
Caused by: org.hibernate.MappingException: Unable to build insert statement
for table [Employee]: SAP HANA requires at least one value in insert
value-list clause.
at org.hibernate.sql.Insert.toStatementString(Insert.java:104)
at
org.hibernate.persister.entity.AbstractEntityPersister.generateIdentityInsertString(AbstractEntityPersister.java:2826)
at
org.hibernate.persister.entity.AbstractEntityPersister.doLateInit(AbstractEntityPersister.java:4147)
at
org.hibernate.persister.entity.AbstractEntityPersister.postInstantiate(AbstractEntityPersister.java:4220)
at
org.hibernate.metamodel.internal.MetamodelImpl.initialize(MetamodelImpl.java:257)
at
org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:294)
at
org.hibernate.boot.internal.SessionFactoryBuilderImpl.build(SessionFactoryBuilderImpl.java:462)
at
org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:938)
I wonder if we have broken something because I wouldn't expect so many
tests to end with an empty insert?
Could someone more familiar with these tests take a look at it? I don't
think we need SAP HANA to check for the empty INSERT issue.
Thanks.
--
Guillaume
5 years, 11 months
