ElasticSearch Client vs Base JVM version - java

I have an existing project that I want to use ElasticSearch in.
The core ElasticSearch requires Java 8, which isn't a problem since it will run in a different JBoss than the existing project we want to integrate with.
However, the ElasticSearch client will be integrated in the existing JBoss, which runs Java 7. Does anyone know the Java version requirement for the client? We are unable to upgrade this Java version due to other circumstances.

According to documentation you can use 8 or 7, however 8 is preferred.

Related

Custom JRE with Java EE(Jakarta)

After added the great feature of Java Module that can run custom JRE for specific application developed and Jakarta for develop the web application or enterprise application which can run Jakarta 9 , I can't understanding method to create web application with java! the question is if I need java 11(or 8) to create web application and Jakarta 9 do I need the Custom JRE that create with module ?
No, it is no required. Actually, the spec is silent in the way or application is deployed.
Currently, there is no more concept of JRE, using newer JDKs, only JLinked images, where you can select only the modules you need.
For now, only Java 8 is supported officially, with support for Java 11 coming shortly.
The specification doesn't mention anything about the Java module system. However, if you want to use modules, you could that a look at the Piranha Cloud project.
https://piranha.cloud
[Disclaimer: Piranha Cloud developer here]

Compiler alert/warning for versions higher than Java 8

I am building applications using OpenJDK11, Maven.
As my application will be used by clients who are using Java 8 and still not migrated to Java 11,
I need to know is there a way I can get alerts at compile time if my application is using higher version of Java 8.

Using Apache Cassandra with a java application build over Java 11?

Newbie to Cassandra. I understand current versions of Cassandra do not support Java 11.
Can you run Cassandra using Java 8 and access the instance with a Java application built over and running on Java 11?
If so, how can it be done? Can you show a simple example?
I'm looking to build a POC on my laptop for an L&L.
Thanks in advance for any and all assistance.
Cassandra and the application connecting to it run on different JVMs, so their versions are independent. Since the app will use a driver, you need to find one that works on Java 11. Either just try it out or search the projects' documentation for supported Java versions.
Looks like DataStax' driver is build on 9 to 14, so I would give that one a try.

what version of OpenNTF Domino API can I use?

I would like to use the OpenNTF Domino API but to me it is not clear which version I can use?
The version of the extension library on the Domino server is 9.0.1.v00_00_20151122-0905 (upgrade pack 1).
If you're using Domino 9.0.1 Feature Pack 8, then 4.0.0 is the way to go. Otherwise, 3.2.1 is the right one.
The plan is for 3.2.x to get critical fixes (which is what 3.2.1 itself was over 3.2.0) but otherwise remain as-is, while future development will happen on the 4.x+ Java 8 path.
The version of ODA will depend primarily on the Domino server version. It sounds like you're running Domino 8.5.3 and we've not specifically developed against that version. There was a lot of new functionality added in 9.0, specifically around NoteCollections, which is spread throughout the API. I did compile a version some years ago for 8.5.3, but it was never heavily tested or officially released. The server in question was upgraded to 9.0 before the project went live, so I'm not sure if I even have that version any more.
Version 4.0.0 is the first specifically compiled for 9.0.1 FP8 and will not work on previous versions. That's because it includes the new core Domino APIs (encryption, ID Vault etc) added with FP8. It's not currently compiled for Java 8, but work on that has already begun in the develop branch.
Version 3.2.1 is the recommended version for 9.0.1 up to FP7. It will still work on FP8, but only if there is no intention of using the new Domino APIs added with FP8. It will work with the base Extension Library as long as the Graph API REST functionality isn't required (not a regular requirement at this time), for which ExtLib 9.0.1_v00_17 is required. That's because additional hooks were added to the core Domino REST service functionality in ExtLib.
For any general discussion about ODA, there is an OpenNTF Domino API channel in the OpenNTF Slack. The OpenNTF Slack team can be joined from the main OpenNTF website home page.

Apache Thrift java minimum requirement

Apache Thrift page suggests minimum java version requirement as 1.7 .
My app uses java version 1.6.95.
Still I was able to compile and use apache thrift.
Anyone has any idea about what this minimum version requirement is for?
The minimum Java version statement provided on the Apache Thrift web site is set by the community. This statement means that the committers will accept patches that use Java features which require Java 7. So while it may be the case that you can use 6 with the code version you have, you may also find that newer versions of Thrift will not work.
For example I think the TZLibTransport will be a problem as of 2015-05-29, it uses SYNC_FLUSH which is a 1.7 feature: https://github.com/apache/thrift/blob/bb98e97fd3c82117c87d23e3fb6b8bbd800784f2/lib/java/src/org/apache/thrift/transport/TZlibTransport.java.
New commits may create further incompatibilities with Java 6.
So if you are using Java 6 and everything is working for you that is good but I would be cautious when updating Thrift or using new parts of Thrift.
The referenced min ver doc page is:
https://thrift.apache.org/docs/install/
which comes from:
https://github.com/apache/thrift/blob/1568aef7d499153469131449ec682998598f0d3c/doc/install/README.md

Categories