I am upgrading my application's JMS from 1.1 to 2.0.
My application is currently having Spring 3.0.3 and uses JMSTemplete.
Is there any official ( Spring or JMS ) documentation mentioning the support for JMS 2.0 with Spring 3.0.3?
I was actually searching it in order to find out weather any Spring related change is required in my application or not.
It should just work since the 1.1 APIs are still supported in 2.0.
If you want to use the new 2.0 shared subscription feature (on topics), you will need to upgrade to at least Spring 4.1.
Related
I'm trying to migrate application with Camunda BPM 7.14.0 and Spring Boot 2.7.2 dependencies to latest Spring version(3.0.1/3.0.2) and at least Camunda 7.16.
Unfortunately I'm receiving some errors during migration and would like to ask what is the compatible version of Camunda which I can use with Spring 3.0.1?
From the compatibility matrix I can read that Camunda 7.18 is compatible only with version 2.7.x
https://docs.camunda.org/manual/7.18/user-guide/spring-boot-integration/version-compatibility/
Can someone confirm it?
Yes, I can confirm that 7.18 is compatible with 2.7.x
Spring Boot 3.0 requires some change in the autoconfiguration declaration and as far as I understood, the community edition will not support it until 7.20.0.
But the same thread mentions a manual fix that I haven't tried so far.
According to the TomEE Download Page, TomEE 8.0 implements the APIs of Java EE 8 and MicroProfile 2.0. Part of these specifications is the API JAX-RS 2.1.
Recently, however, I ran into ClassNotFoundExceptions when trying to use the the Jersey Testframework (Version 2.38), which also is based on JAX-RS 2.1. When I analyzed this problem, I found that Jersey introduced a dependency jakarta.ws.rs-api-2.1.6.jar, that contained different versions of the API classes than the ones from TomEE 8.0 (javaee-api-8.0-5.jar from org.apache.tomee:javaee-api:8.0-5). Furthermore, the source code from the latter library is commented with Apache Geronimo JAX-RS Spec 2.0. On the other hand, a javaee-api-8.0.jar from Oracle (javax:javaee-api:8.0) contains the same classes as the Jersey dependency.
So from this, it looks like TomEE is in fact based on JAX-RS 2.0. Can anybody shed a light on this discrepancy?
Is there any known version dependencies between Apache Wicket and Spring? Couldn't find any from the Wicket or Wicket-Spring bridge documentation .
For example can Wicket 7 be run with Spring 5, Wicket 9 with Spring 4 and so on.
Wicket 7.x uses Spring 4.1.x - https://github.com/apache/wicket/blob/wicket-7.x/pom.xml#L135
Wicket 8.x uses Spring 4.3.x - https://github.com/apache/wicket/blob/wicket-8.x/pom.xml#L137
Wicket 9.x uses Spring 5.3.x - https://github.com/apache/wicket/blob/wicket-9.x/pom.xml#L174
Wicket 10.x will use Spring 6.x - https://github.com/apache/wicket/blob/80726e2dae60e5893be0621761883f2dec20cac0/pom.xml#L185
You can manage the Spring version in your pom.xml and it may work or not depending on which Spring APIs you use in your application. Wicket's usage of Spring APIs is rather minimal and most probably you won't face problems.
I am using JPA 2.1 in my project (Hibernate 5.x) and deploying in IBM WAS 8.5.5.
Since IBM WAS 8.5.5 supports only JPA 2.0 by the container, There is persistence loader issue during application deployment.
Is it possible to configure custom JPA at app level in WAS.
I already tried - IBM WAS Documentation
You said you tried https://developer.ibm.com/wasdev/docs/can-i-use-jpa-2-1-on-websphere-application-server/, but what part of this document is not working? This is the page I would reference if you are trying to get JPA 2.1 running on 8.5.5.
Some alternate suggestions:
Traditional WebSphere v9 supports the JPA 2.1 specification level. I would recommend using WebSphere v9 for your project instead of 8.5.5 if you really need to use Hibernate 5.x
Hibernate 4.2 was the last version that supports JPA 2.0. You can downgrade to this version of Hibernate if you dont have to use JPA 2.1
Either of these solutions gain you container support and will provide the JPA API bundle for you. Whichever you go with, make sure not to bundle your Hibernate JPA persistence API bundles in your application. Hibernate repackages its API into "hibernate-jpa-2.x-api.Final.jar". I have seen this before as a conflict that customers build into their applications.
With class loading strategy, I was able to override the JPA 2.0 of container.
using the inputs from IBM Developers support.
I was tasked to assign to modify an application with RBAC(Role Based access control) for a project which uses an older spring mvc version 3.0.5.
We plan to integrate spring security for this task.
The question is, are there any older version of spring security we can use
that is compatible with the spring mvc we have?
Last Spring Security-3.1.0 supports spring 3.0.6. This version of spring security should work fine for your project.
Although your version should work fine with this version of spring security if you want you can do a minor version upgrade of spring. You can find the changelogs here https://spring.io/blog/2011/08/24/spring-3-0-6-is-now-available
And documentation for this version of the library can be found at this link spring-security-3.0.7-docs
But, please be cautious, it's not recommended to use older versions of security-related libraries since they might have known vulnerabilities.