I googled, but was not able to find this information.
Spring Data 2.0.2 supports Hibernate 5.2 and this is an implementation of JPA 2.1
Related
I am planning to use MapStruct in my project. Using JDK11, Spring boot 2.7.x has my current version but soon planning to upgrade it to JDK17 and Spring Boot 3.0. Based on documentation, latest library will support JDK8 onwards. Would like to know, whether library will support for above said specification. And also would like to know, how actively the project is going to support in near future?
Hi looking for guidance on a version of spring-data-aerospike for Springboot 2.4.2. I don't see it listed here
There wasn't a specific spring-data-aerospike version that used Spring Boot 2.4.2.
spring-data-aerospike 2.4.2.RELEASE used Spring Boot 2.3.5.RELEASE.
spring-data-aerospike 2.5.0/3.0.0 used Spring Boot 2.5.1.
spring-data-aerospike 3.0.1 is using Spring Boot 2.5.3.
Using the latest spring-data-aerospike is recommended, if you can I would consider an upgrade, if its not an option - I would suggest using the latest version possible that works with your current version of Spring Boot (probably 2.4.2.RELEASE).
Will Mybatis support Spring Boot 2.5? Currently Mybatis Framework is shown as an unsupported Dependency on the Spring initializer Site for Spring Boot 2.5.0 M1 release.
Yes, it will once it reaches GA.
'M1' means it still is a milestone release.
See this answer for the details.
Even 2.5.0 GA can not choose Mybatis Framework In Initializr,
but I hear it is preparing now.
Besides, I can still use it by adding mybatis-spring-boot-starter to dependencies.
I am trying to use EclipseLink 2.5 in my GlassFish 3.1.2.2 but it seems that its not working properly.
So What are the supported versions of JPA does EclipseLink 2.5 support ?
I am restricted to use JPA 2.0 till the moment.
EclipseLink 2.5 is implementation of JPA 2.1 specification. Because JPA 2.1 (what's new) is more or less superset of JPA 2.0, it is possible to use EclipseLink 2.5 and limit usage to features available in JPA 2.0.
GlassFish 3.1.2.2 was shipped with EclipseLink 2.3.2 (which is implementation of JPA 2 specification), so it is rather easy try is EclipseLink version source of problems. Likely not - but new bugs are of course always possible. Also then issue is not directly connected to supported JPA specification version.
I am working with GlassFish 3.1.2.2 (I can not upgrade to 4 due to OS restrictions).
I'm interested in upgrading JPA 2.0 to JPA 2.1 GlassFish 3.1.2.2. How can I achieve this?
This is most likely not possible at all. JPA 2.1 is part of EE 7 and therefore not fully integrated with EE 6 GF 3.1.2.2.
Did you try just replacing the EclipseLink and JPA jar files in Glassfish?
It will probably work, but if you use managed persistence units they will not expose any JPA 2.1 API, you would need to unwrap the EntiyManager to access these.
I'm using Hibernate 4.3.8 (requires JPA 2.1) with Glassfish 3.1.2.2.
Note: I'm not using any services provided by glassfish. All the libraries I use are in the WEB-INF/lib.
1 - Override all JPA classes (package javax.persistence) in glassfish/modules/javax.persistence.jar with JPA 2.1 version. You should not replace the entire JAR, only override the classes. This JAR has an OSGI manifest and other classes that must remain there.
2 - Remove all javassist classes (package javasssist) from glassfish/modules/weld-osgi-bundle.jar. This solves a possible incompatibility if you are using Hibernate.