We are using Weblogic 10, so maximum Java allowed there is Java 1.5
I inherited the code using EJB3
So, I will have to work on it within a realm of my Java 1.5 limitation.
I think, original designers had in mind to use Hibernate for implementing Data access, and
at some point we will migrate to JBOSS, so would like to keep Hibernate as a choice
There is one sitting in a project - version 3.2.1.ga. Same is a version for hibernate-entitymanager.jar
What is the latest version of Hibernate that I can use for this? I understand there were some changes in it.
Hibernate 3.x workes with JDK 4 and 5,
The 4.x requires 6.
I think you should go with HIbernate 3.6.x. The last version in 3.x was 3.6.10.
You will not find it on hibernate site you will to goto sourcefoge.net to get this version.
here's the link
Related
We are currently using spring 3.2.9. We are thinking of upgrading that to a newer version. When I checked the documentation it says that
Along with 4.0 M1, we’ve released Spring Framework 3.2.3, containing
fixes for recently reported issues but also coming with OpenJDK 8 runtime
support. Spring Framework 3.2.x will support deployment on JDK 8 runtimes
for applications compiled against JDK 7 (with -target 1.7) or earlier.
Does that imply that I can't compile on Java 8?
Should I use spring version 4.0.x if I wanna compile with Java 8?
There is a best effort support of JDK8 in the 3.2.x line, as of 3.2.9+.
See SPR-11656 for initial support in 3.2.9 and SPR-11979 for bytecode support improvements in 3.2.10. Please note the support limitations explained in the comments.
For comprehensive support of JDK8, please upgrade to Spring 4.x - there's a dedicated wiki page explaining the upgrade path, and the Spring team made great efforts to make that upgrade experience really easy.
As per my observations, you can actually use spring 3 with code compiled in Java 8, as long as you do not use new java8 syntax in there (like lambdas) in the paths scanned.
So, you can use new APIs (streams ...), but not new syntax (lambdas...).
When I tried, I ended up with startup errors like org.springframework.beans.factory.BeanDefinitionStoreException: Failed to read candidate component class
Versions of the Spring Framework that are older than 4.0M1 do not work with classes that are compiled for Java 8.
Spring tries to Proxy these classes by reading class files, which won't work if they're "too new". If your #Service classes are compiled with Java 8 as the target, Spring will fail to load the classes on startup.
This means that you will have to upgrade to Spring 4.x.x, if you want to target Java 8 (and use lambdas, default implementations and so on).
I encountered this problem myself a few months ago with a project that uses Spring 3.x.x.
I just need clarifications related to JBoss Application Server. I've developed a project which is compiled in Java 6. And it is deployed in Jboss 5 version. Till now I didn't find any problem with the application. But I want to know will there be any possibility that Jboss will have any backward compatibility problem. Or does Jboss needed upgradation with respect to Java version. Any suggestion would be appreciable.
Thanks,
Marshal.
Even if JBoss 5 is compiled with Java 5 there shouldn't be compatibility problems at a language level.
As for the libraries there might be a problem but those that JBoss requires should have been taken care of. This leaves you with core libraries that JBoss might have replaced in its class loader hiearchy and thus might have an older version. In that case you could put those libraries into your application and effectively override the JBoss versions on a per-application basis. We did that with some XML libs (IIRC JAXB was one of them).
As an alternative - as suggested by #Geziefer - use a JBoss 5 version specifically compiled for Java 6.
which are the minimum requirements to run a java web application with spring 2.5 and Hibernate 3? I mean, referred to Tomcat version, Mysql version, and Java EE version. I use Java EE 6, Mysql 14.14 distrib 5.1.41 and Tomcat 7 but i need to know the lowest version in which can be run
It would run on a reasonably low version of everything:
spring runs on tomcat 5.5 for sure, which is way old (and might even run on 5.5)
hibernate's MySQL Dialect should be fine with MySQL 4.1
For exact compatibility you should check release notes, but it is unreasonable to use so old version of these technologies anyway.
Now we have a project with java 1.4 and ejb 2.1 running on jboss 3.2.1. We are trying to update up to java 6 and ejb3.1, but we are doing it in steps. So my question is simple, can we use ejb2.1 on jboss6?
In theory, yes. EJB 2.x is still part of the current JavaEE spec, and JBoss6 supports it fully.
However, JBossAS 3.x and 6.x are architecturally very different to each other. Do not assume the upgrade will be a smooth one, it may well feel like migrating to a completely new appserver.
We are planning to upgrade our Tomcat from 4.1.31.
Our's is an Axis 1.4 application where we have our web services.
Request you to suggest the latest stable version of Tomcat 5 or Tomcat 6 suitable for our application. And the things to consider while upgrading.
Will the existing 1.4 Java code base works smoothly on Tomcat 5 or 6?
And going further we may write the code in JDK 1.5 as well. So, having Java 1.4 code and Java 1.5 code together, will create any problems?
Kindly suggest.
Please share your upgradation experiences.
Thank You :)
Tomcat 6.0.26 is the latest stable release.
It requires JRE 5.0 or later, so if you are truly stuck on 1.4, you'll need to download the latest 5.5 release, which requires a compatability package to run on 1.4.
My advice: bite the bullet and make the necessary changes for your application to function on 1.6. It is only going to get more and more painful to upgrade (and to continue to code in 1.4) as time goes on.
Go to Java (1.)6; it really makes doing web services like yours easier and it's really widely available now.
If you are going to upgrade I would recommend first doing some tests with java 6 + the existing codebases. If that seems to work, go to Tomcat 6.
Perhaps also upgrade some Axis libraries while you're at it, or leave it as is if it still works.
In my experience you can get to trouble by migrating to Java 5 (and thus 6), especially with XML. My memory has something like a class name clash between Java 5 and an old version of Xerces, but I could be mistaken.