views:

336

answers:

5

With the upcoming end of life (EOL) of Java 5.0. We need to upgrade our enterprise application to work with Java 6. The application can be deployed on both WebLogic, WebSphere & JBoss. (It's up to the customer's choice)

Does anyone have an experience with such an upgrade? What issues should we encounter? What pitfalls we should avoid?

+2  A: 

Why, I would follow the JavaSE 6 Adoption Guide!

http://java.sun.com/javase/6/webnotes/adoption/adoptionguide.html

The upgrade usually is pretty straight forward...

altCognito
Not much of a problem in this case.
Tom Hawtin - tackline
I thought the enum keyword was introduced in Java 5. Shouldn't be an issue moving from 5 to 6.
duffymo
Good point, sigh... What a day. Removed...
altCognito
A: 

Your biggest problem will be with the WebSphere, WebLogic etc.

Are they all certified to run on Java 6.

I am surprised that Java 5 is EOL so quickly - in practice Sun will offer patches for years.

Fortyrunner
The new practice is not to offer *free* support for so many old versions. Support is available through Java for Business.
Tom Hawtin - tackline
Wow. Just looked at the Sun policies for EOL. They have been much more aggressive with 1.5 retirement than 1.4 was. Lucky we moved onto 1.6 nearly two years ago.
Fortyrunner
WebLogic 10.3 is the first version that ships with JDK 6. The earlier releases of 10.x ship with JDK 5.
duffymo
+1  A: 

One problem you may encounter is if you use JAXB 2.1. See this link for details.

kgiannakakis
+1  A: 

At my last job, we had to do this; it was put off for a long time. When we got to doing it, it took no time at all in the grand scope of things. A few interfaces expanded to add new functionality, the enum keyword was used and promptly refactored, etc.; nothing major. We supported the same app-servers you do, and they all work just fine with Java6. The whole thing turned out to be something an intern could do.

geowa4
Thanks, that's sound encouraging
LiorH
that's just my experience. your system might be different.
geowa4
A: 

Can't do anything specific to WebLogic, WebSphere, or JBOSS. You have to include whatever special config each one needs in the distro at all times.

The only way I find I can migrate between app servers without changes is to use Spring. I can move a WAR from Tomcat to WebLogic without issues, but only if I include the META-INF/context.xml for Tomcat and weblogic.xml for WebLogic.

duffymo