We are upgrading tomcat version to 9.0.35 which is compatible with Java 8. We are using DROOL KIE web container war 6.5 which is deployed in tomcat. So question here is are these versions compatible.
Java 8 - KIE war 6.5 - Tomcat 9.0.3.
We have tried it in non-production environment and result looks fine. But since documentation of Drools is not clear we need this confirmation.
Related
After migrating the Eclipse (2021-9) workspace to Java 17, it is not possible any longer to add the Web project to the tomcat server.
Tomcat version is 9.0.54. All projects have Project Facet 17 and the related java 17 JRE.
Also the plugin 'Java 17 Support for Eclipse 2021-09 (4.21)' has been installed.
But adding the web project to the tomcat server is not working any longer. I get the message "There are no resources that can be added or removed from the server".
It only works when I set the project facet of this Web project back to Java 11 again. But that is not what we want.
So far I didn't find a solution for this problem. Do you know how to solve this issue?
Bug
This appears to be a known bug in Eclipse:
Bug 576466 - Can't add Java 17 WebApplication to Tomcat9
Workaround
As for a workaround, the author of the bug report mentions Eclipse does work properly if you switch to using Tomcat version 10.
FYI, versions of 9.x and 10.0 of Tomcat are special in that they are virtually identical, developed in parallel, the main difference being the switch in package names from javax.* to jakarta.* as part of compliance with Jakarta 9.0. See Transition from Java EE to Jakarta EE by Arjan Tijms.
Furthermore, Tomcat 10.1 is built to support Java 11, as part of compliance with Jakarta 9.1. Since you are using Java 17, I would suggest using Tomcat 10.1.x in your situation.
Currently, I have a JavaFX project running on JDK8 b181. The EJB's are also built on JDK8 b181 platform and deployed as an EAR on WebLogic 12.2.1. Everything works perfectly on NetBeans 8.2.
Now that we have decided to move everything to JDK9, I am not sure if all the technologies used above are compatible with 9. I highly appreciate if any experts can advice me on how to approach with this migration, especially for application server and EAR components.
I have done the below research:
Server: (Is there any vendor who supports JDK 9 for EAR deployment?)
The latest version of WebLogic 12.2.1.3 is still not compatible with JDK 9
The latest version of GlassFish 5 is still not compatible with JDK 9 (tried mapping AS_JAVA in asenv.conf file to JDK 9 and it did not work)
Tomcat 9 web server is compatible with JDK 9, but TomEE plugin to deploy EJBs as an EAR is still incompatible with JDK 9.
IDE:
Apache NetBeans9 is compatible with JDK 9. However, none of the enterprise modules (EJB, EAR) are migrated from NetBeans8. I have tried adding plugins in NetBeans 9 from NetBeans 8 repository, but still EJB projects only work on JDK 8.
At the first glance, Eclipse Photon seems to be compatible with JDK9. I have added e(fx)clipse plugin and was able to add JavaFX support. Still I could not deploy any EJB's (as an EAR built on JDK 9) on WebLogic 12.2.1.3.
Not sure for all the stack but TomEE 7.0.5 should run fine on JDK 9.
I am about to develop a simple web application which has only one registration page. I am planning to develop it with JSP, Servlet & Hibernate.
I am about to develop this application in JDK 1.8 & Tomcat 6 as Application Server. But problem is deployment server has IBM WebSphere & JDK 1.5 installed.
I will create .WAR file and extract it on IBM WebSphere.
I want to know what are potential that will come in each step from development to deployment process.
I have an updated EAR FILE which contains few java code changes and is currently deployed on WAS 6.1. Now we are in process of upgrading the websphere to 8.5. Will the same EAR file work on WAS 8.5? Will just compiling the code be sufficient to run on WAS 8.5. Do we have to do any changes to make it work on 8.5 version. And what version of jre and jdk does 8.5 supports.Please help
WAS 8.5 supports Java 6 and 7.
See this page, go to the Supported Software tab and scroll down to Java SDK. http://www-969.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProductByComponent?deliverableId=1337870535828&duComponent=Server_11854150A6C511E2A4CA497F0925FE1B
As Marged said in a comment, whether you'll need to make changes to your EAR depends on what is in it. The Knowledge Center has this page on migrating from previous versions to 8.5: http://www-01.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.nd.multiplatform.doc/ae/welc6topmigrating.html?lang=en
I am trying to add jersey to our (old) jboss project but I get "Unsupported classversion" when deploying to jboss - which points to a compile vs runtime version mismatch. In production and on our test servers, the application runs on java 6 but it is built using java 7. Corporate bureaucracy means that it will take months to upgrade the servers to java 7 but the code itself no longer compiles in java 6 due to some javaws dependencies. So for the foreseeable future, I am stuck with these versions.
All my changes work fine if they are compiled and run in java 7 but don't deploy if compiled in java 7 but run in java 6.
I have tried using the maven-compiler-plugin to force the target to be 1.6 but then I run into "source release 1.7 requires target release 1.7" errors.
I can see that at least one the jersey jar artifacts that is downloaded by maven is compiled with java 7 (51.0) and that presumably is the cause. Anyone have any tips as to how I can go forward with this?
Indeed, Downgrading the version of jersey to one compiled with java6 sorted the issue (kinda - I get some jersey problems now instead).
I extracted the class files from the .jar and ran "file" on one and I found that 2.6 version of jersey was the last to support java 6