Can you upgrade your Apache Commons Lang 2.6 to Apache Commons Lang 3.5 ?
See https://commons.apache.org/proper/commons-lang/download_lang.cgi .
If you're asking whether it is currently possible to use UCanAccess with Apache Commons Lang 3.x instead of 2.x, the answer is "No".
If you're asking whether UCanAccess can be modified to use Apache Commons Lang 3.x instead of 2.x, it's not really a matter of modifying UCanAccess. UCanAccess depends on Jackcess, and Jackcess depends on Commons Lang, so it's up to the Jackcess development team to decide if and when they want to make such a change.
Recently there was just such a Feature Request for Jackcess; you may want to leave a comment there to indicate your support.
Related
we are planning to migrate our Tomcat from 8.5 to 10/11 version.
at the moment we are using Java 8, we are planning to use Java 17 .
I wanted to know if any one has previously migrated and what were the concerns regarding that.
I am aware that javax needs to be changed to jakarta series.
in our 8.5 tomcat we are using following maven dependencies
spring - 4.3.25.RELEASE
jackson
googleapi
graph
aws amazon jdk
javax servlet
mysql connector 5.1.44
log4j
slf4j
jsoup
unirest
httpcomponents
should we also need to update these dependencies to latest version? to be compatible with latest Tomcat 10
any other issues I need to be aware of ? I will post more on the same thread as I face issues while miggrating, appreciate the feedback and support from you guys. Thanks
Solution/ best way to migrating and also any tools that does it automatically? issues faced be individuals and how they resolved while migrating.
Doing migration spring-integration-Kafka 1.1.2 to 3.3.1. In the project, we are using an XML-based Kafka configuration. After changing to the 3.3.1 version. Getting So many errors in the XML file. like <int-kafka:producer-context id="kafkaProducerContext"> not getting tag. Is there any way to solve this problem?. Or is I need to use java based configuration?
It has had a complete rewrite based on the spring-kafka project since 2.0.
Version 3.3.1 was still a stand-alone extension: https://github.com/spring-projects/spring-integration-kafka
The documentation (including XML configuration, which is now simpler) is a chapter in the Spring for Apache Kafka Documentation; it uses version 2.5.7 by default; the latest 2.5.x is currently 2.5.12.
https://docs.spring.io/spring-kafka/docs/2.5.12.RELEASE/reference/html/#spring-integration
spring-integration-kafka is now part of the Spring Integration project (since 5.4) and is no longer an extension project.
https://docs.spring.io/spring-integration/docs/current/reference/html/kafka.html#kafka
I have a RESTful web service application in java deployed on google app-engine which uses jersey 1.18.6.
I want to use postmark java client to send transactional emails from it.
When I integrated it, i was seeing the following exception:
javax.ws.rs.core.Response$Status$Family.familyOf(I)Ljavax/ws/rs/core/Response$Status$Family
From what I could find, I think this error was because of there were two different (and probably incompatible) version of jersey being used ,1.18.6 for jersey-server, jersey-guice and jersey-bundle and 2.25.1 for jersey-client (by postmark).
Then I tried to make the jersey version 1.18,6 throughout, so in the my main project pom, while including the dependency for postmark, I excluded the jersey-client (by added exclusions header) and separately added jersey-client dependency in my main project .
But then I got the following error:
java.lang.NoClassDefFoundError: javax/ws/rs/core/MultivaluedHashMap
This is I think the class MultivaluedHashMap is present only in jax-rs 2.x versions (which is compatible with jersey 2.x versions)
So my questions are:
Is there a version of postmark java client library which uses jersey 1.x instead of jersey 2.x?
If no then what options do I have other than migrating my main project from jersey 1.x to jersey 2.x. I don't want to do that since we will have to migrate not just the jersey dependencies but I think some other things like guice, shiro etc. which would be time consuming. Also it doesn't really seem optimal to modify multiple existing dependencies just to include one additional module.
There isn't. The very first commit of the project's pom.xml already used Jersey 2.25.1
as Mureinik mentioned above, when we worked on the library, our plan at Postmark was to use newer library versions, since they are better options in long run.
On our Github page Rupert made good suggestions, from which I find separate ClassLoader a good choice. I will play a bit with the library code in next couple of days on compatibility, however we are always in favour of using newer libraries for our codebase.
please check out my latest comment on Github issues page for possible solution for using older Jersey version https://github.com/wildbit/postmark-java/issues/11
It should be pretty easy to port the library to Jersey 1.x by porting only the HttpClient class on your side.
Is there any Spring 5.0.6.RELEASE osgified version patch available? We have to to do quick release so need to upgrade older spring but currently our framework uses OSGI based container, though spring has officially stopped supported OSGI. Is it possible to have patched version of latest Spring framework?
Though I know it's better to convert to Spring based container but since time doesn't allow I'm in search of any osgified version of Spring jars.
Apache Servicemix produces osgified versions of a lot of well known libraries, Spring included: https://github.com/apache/servicemix-bundles
Currently the latest osgfied version of Spring is "5.0.5.RELEASE", with "5.0.6.RELEASE" probably due to come in the near future. Otherwise, getting servicemix pom.xml for 5.0.5.RELEASE and manually changing Spring version should work (from 5.0.5 to 5.0.6 there should be just internal implementation changes).
I'm running JbossFuse/Karaf version 2.3.0.redhat-60024 and it comes with spring 3.1.3.RELEASE.
How to update the spring version to 3.2.4.RELEASE?
Thanks
Spring 3.1.3 is included in the features XML shipped with that Fuse ESB release, i.e. system/org/apache/karaf/assemblies/features/standard/2.3.0.redhat-60024/standard-2.3.0.redhat-60024-features.xml
A newer version of that features XML (not redhat specific) contains the features definitions for Spring 3.2.4, see standard-2.3.3-features.xml.
The easiest way to install Spring 3.2.4 libraries then would be:
features:addurl mvn:org.apache.karaf.assemblies.features/standard/2.3.3/xml/features
features:install spring/3.2.4.RELEASE
Another option is to simply copy & paste the items you want from that file and add them to a new features XML, or append to one of the ones already included with Fuse ESB under the system directory. See here for more information about creating your own features XML file.