This content has been marked as final. Show 6 replies
811829 wrote:Maybe. If your code uses the newly reserved keyword 'enum' then you will have to make some changes. You'll figure that out quite quickly and the fix is as simple as using an IDE to do some rename actions. Other than that it depends on how much you leave as defaults; if you employ very specific configuration switches then it shouldn't change much. Newer JVMs do change their default settings however (for example: which garbage collector is used) so you may see some changes in behavior because of that. But then again: maybe not.
We are supporting one application which is using Java files (.jsp,.xml,.java) of V1.4.2.
Now we have a new request to upgrade the existing application from V1.4.2 to V1.6.
Could you please let me know:
(1) Will there be any change in code when migrating from one version to other version?
(2) Is Java V1.6 supportable in Window Server 2008 R2?Check the download page. Is there a download for the CPU architecture of your server? If not - well there is no secret download page.
(3) Is Java V1.6 supportable in RHEL 5.3?You'd have to ask RedHat. Java can be installed on any flavor of Linux though; either "official" or OpenJDK. But you will want to install what RedHat recommends you to install, using their own software management solutions.
(4) Any upgrade approach document?No. Upgrade steps also depend on what software you are running. The steps are going to be very different and more complicated when you're running a JavaEE enterprise application server for example, and then you'd need to look for a guide from that server's vendor.
I agree with the previous posts. You need to research any issues that come up as they occur. I suggest you be sure that you are able to compile and deploy the application before you change the version of Java. Then, recompile/deploy it with the new version of Java. You're IDE will probably do a good job on telling you what the problems are. Fix all errors first. Then, you can look at resolving any depreciated warnings the IDE provides (although you don't absolutely have to fix them, it's still a good idea to do so).
811829 wrote:That seems like a really bad idea to me.
(2) Is Java V1.6 supportable in Window Server 2008 R2?
Given that you are upgrading then you should upgrade to 1.7 because it is really likely that 1.6 will start the end of life cycle this year. So you are using an unsupported version now and you would be upgrading to a version that will become unsupported a small time window (certainly less than with the window between 1.4 and 1.6.)
(4) Any upgrade approach document?Rather simple actually
- Build it
- Do a full regression test
- Do a full QA test
- Provide for a rollback strategy when applying it to production.