Normally weblogic 12c doesnt support jax-rs 2.0 but by the help of jax-rs shared library which comes with weblogic itself it is possible to upgrade jax-rs version from 1.1 to 2.0. The problem is library implementation is jersey 2.5 which doesnt satisfy my needs. I found a link about upgrading jersey version on weblogic which looks a lil bit complex. Is it enough to replace jersey jars 2.5 with my jersey version 2.13? Do i need to do anything else?
I have created a simple maven project to produce the war file with the 2.19 jersey shared library for weblogic.
I have tested it with weblogic 12.1.3
You can clone from here weblogic-jax-rs
After cloning run mvn package to produce the war and then deploy it to the server.
Of course you must specify the new implementation version in your weblogic.xml which is now 2.19
If you are not familiar with maven you can download the war file from here
As of weblogic 12.2.1 - there is jersey 2.21.1 bundled with it so no additional installations are required.
weblogic 12.2.1.1 comes with jersey 2.22.1
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.
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 am developing a plugin for an application that is deployed in Weblogic 10.3.6. I need to use jersey 2.25 api in the plugin. The application ships jersey 1.8 in its APP-INF/lib folder. So, when I deploy the plugin the classes are all mixed up and throws class cast exception. I cannot modify the application. I have deployed the jersey 2.25 jars in DOMAIN_HOME/lib folder. Is there a way to use the new libraries instead of the supplied one in the application? If it is not possible can you suggest me any workaround to do so?
Do you deploy a share-lib which is based on jersey related jars. Remove that share lib. And try again, you may be success. But 10.3.6 don't support jersey 2.25.
In using bleumix liberty with jax-rs1.1 ( inclusive jersey 1.8)
But I get 415 errors media not supported when I use it.
It works on tomcat, but bluemix liberty gives an error.
Any thoughts
Regards
Marc
Liberty jax-rs 1.1 based on Apache Wink, not Jersey. Is your jax-rs implementation using wink? Verify you are providing a wink implementation. Also, remove all the wink jars from your war to avoid conflicts and use what's provided by Liberty. You can either remove them manually from the war WEB-INF/lib, or change your pom.xml and add <scope>provided</scope> for the wink dependencies so that they are not packaged with the war. If you want to use Jersey instead, you will have to disable jax-rs 1.1 by providing a customized server.xml feature set.
The Liberty for Java starter application shows a basic implementation example in src/com/ibm/cloudoe/samples/HelloResource
I'm trying to deploy an existing app to tc-server. I have been using this app on tomcat for a couple of years and the production version already runs on tc-server. I have installed the version of tc-server that comes with spring insight. Everything goes well until I deploy a war file that has a dependency on spring integration. I'm getting a no class def found error and it is complaining about a class called
org/springframework/integration/transformer/AbstractMessageProcessingTransformer
I opened up the spring integration jar that is bundled with my war in the WEB-INF lib and did not see that class.
I poked around in the tomcat instance that I created with the bat files in tc-server and see a later version of spring-integration i.e.
.\insight\collection-plugins\insight-plugin-spring-integration-1.9.2.SR1.jar
Since my war is now getting a class not found exception (whereas it deploys fine on my normal tomcat 6.29 ) I'm assuming that this other version of spring-integration is being seen by my app somehow. My app is configured to use spring-integration-1.0.4.
Does anyone know how to get around this problem?
1.0.4 is an extremely old version (3+ years old) the current release is 2.2.4. That class was introduced in 2.0.0.
So you probably have a classpath issue - insight needs a more recent version of Spring Integration on the classpath.
The insight plugin version (1.9.2.x) is not related to the Spring Integration version (but it needs a much more recent version than 1.0.4).