we are using a very old version of java installed previously in our server (version 1.4) and according to this case we used a very old version of iText2.1
Our main vendors planned to upgrade the server and they will upgrade the java version to 8.
Question: should i upgrade my application which uses the iText2.1, or it will work fine with the new Java ver.? and what version should i use then?
Note:i've tried to raise this question in the itext blog but they put the stackoverflow link for any technical question. , so please be kind and help me.
The above comment is really an answer:
I know that in recent versions of iText (I think 5.5.7 or 5.5.8) we made some small changes for Java 7 and Java 8. The minimum for iText 5.x.x is Java 5. Anything older than 5.0.0 is totally unsupported, sorry. iText 2.1.0 is from March 2008, that's 8 years ago.
Using Eclipse
I am Using 1.8_45 with iText5.7
No Exception and warning with it .
So Upgrade
and if you are not upgrade your iText2.1 with java 1.8_45
so it's give you Exception
yes you can easily upgrade your versions
1.8_45 to 66 jdk
with
iText5.7
Related
I have already read on documents saying that Hibernate version 5 is compatible with Java 11. but
Is Hibernate ORM version 4 also compatible with Java 11?
if not: What changes are required to upgrade?
Hibernate 4 is not compatible with Java 11 and was declared, for quite some years now, as ”end-of-life“, practically since end of 2015.
Full Java 11 support was announced with Hibernate version 5.4:
Hibernate ORM now supports JDK 11 out of the box.
Hibernate 5.3 lists Java 11 as supported in the latest release 5.3.22. Moreover, Hibernate 5.6 is also Java 11 compatible. This might be the last version in the javax namespace, yet it supports the transition to the new jakarta namespace.
Pointers on what changed or needs changes in your project are found via this question or in my answer to a similar question, related to migration from version 4.3 to version 5.2. Many things in that answer should guide you along the path.
Could you please help in finding out if JRE 8 would be compatible with weblogic 10.3?
We have a swing based application deployed on weblogic 10.3 server. We want to upgrade our JRE so wanted to check if JRE 8 would be able to run apps deployed on weblogic 10.3
Java 8 is supported on WebLogic Server 12.1.3. It is not supported on 10.3.6, 12.1.1, or 12.1.2.
See https://blogs.oracle.com/WebLogicServer/entry/weblogic_server_12_1_3
Java 8 is not yet supported in Weblogic server (till Weblogic 12.1.2).
It would be supported in future release.
https://community.oracle.com/thread/3539686
Bit old topic, but just came across this issue myself and have a bit more to add to it. As with the existing answers, it can't be used to install directly- the oracle installer will complain.
However, it is possible to install using an earlier JDK (6 or 7 are supported in 10.3.6), and then swap to JDK8 under the covers. I expect you could also use a custom install to bypass the installer entirely.
This obviously isn't supported - but it does run. If you try to use certain JDK8 features though, they tend not to work (such as newer jdbc drivers - 4.2 simply won't run), so there isn't much benefit to this in normal use cases.
As per the latest update Weblogic 12C is compatible with JDK 8.
https://docs.oracle.com/en/middleware/fusion-middleware/weblogic-server/12.2.1.4/notes/whatsnew.html#GUID-960100E8-DFC1-49E5-8CED-1EC1D883A42F
Is WSO2 API Manager certified against Suse EE SP3 and Oracle Java JDK7 ?
http://docs.wso2.org/display/AM160/Installation+Prerequisites
Whatdoes de * means with JDK7
In a technical point of view, the WSO2 products should be able to run on Oracle JDK 7. I do not think anyone has especially tested on Suse EE SP3.
As long as it runs on Oracle JDK, the products should work fine.
The 1.7.* means that any Java 7 update should work. For example: 1.7.51 -> Java 7 Update 51
However we have faced issues specific to a Java update. For example, there is an issue with Java 7 update 45. You will encounter JAXP00010001 error after a certain number of requests to API Manager.
I would recommend you to use the latest JDK from Oracle. AFAIK, we haven't encountered any issue with latest JDK.
I hope this helps.
I found this page stating that Java 8 support for Juno is deffered, but I can't find more information how soon people can exspect to be able to write first closures in Eclipse and get productive with that stuff.
Has someone got insight how long we still have to wait? The Java7 features were in 3.7 really quickly, that's why it's kind of odd that this task is deferred.
Any comments, ideas? Or maybe even a good workaround?
One of the key reasons that Java 8 support was deferred is that Java 8 will be available after Eclipse Juno is released. A major release of Eclipse couldn't be shipped with functionality reliant on an unfinished Java release.
Java 7 support went through a similar issue with Eclipse Indigo. Tooling for Java 7 proceeded in a branch that was merged into main indigo stream after Java 7 shipped, so you saw tooling support in Indigo SR1.
I would expect a similar situation for Java 8. There may be a branch open for this work already. The best place to check in on the status is in the bug that is referenced from the document that you found.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=380190
Java 8 will be released at some point after mid 2013, so there is still quite some time to go :-) Full support in Eclipse for Java 8 should not be expected before Java 8's release date, it was the same for Java 7 support.
Currently, there is no branch open for this work. However, whenever that does happen you can expect to see a few blog posts about it :-)
You may give IntelliJ Idea a try which has preliminary suport for it, see http://confluence.jetbrains.com/display/IDEADEV/IDEA+12+EAP
I am developing software on a machine with the latest JDK update (e.g. jdk1.6.0_24). Do the machines where the software is running also need the corresponding JRE update version? Or would it suffice to have an older version (e.g. jre1.6.0_10) installed?
Just the major version (1.6.0) needs to match for Java. It's fine if the update version (10 and 24) is different, the spec is still the same. Although ideally the place where the software will run has the latest update for bug fixes, security fixes and performance improvements.
You do not need to worry, if both are the same major version, which is your case, both are Java 6.
However, if you are releasing your software to a client machine, I would suggest you to read the incompatibilities between Java 6 and other Java versions. And, if there is an incompatibility, mention it in your product document.
Please read this document: Java 6 Compatibility