[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now


Copile JDK1.4.2_10 & run with JDk1.3

Posted on 2006-03-20
Medium Priority
Last Modified: 2012-05-05
Dear Experts

We used the JDK1.4.2_10 when we build our product. But when we move to production by mistake the JAVA_HOME was pointed to JDK1.3. We application contains Servlets, EJBs etc.

is there any possibility to get the issues?


Question by:krishnasaikarthik
LVL 92

Accepted Solution

objects earned 400 total points
ID: 16243933
suggest either shifting production to 1.4.2
or shifting development to 1.3
LVL 92

Expert Comment

ID: 16243936
you can also use -target 1.3 compile option to produce 1.3 compatible class files but you could still have incompaibilities.
LVL 30

Assisted Solution

by:Mayank S
Mayank S earned 400 total points
ID: 16243948
Is it possible to change the JAVA_HOME in production? If not, you can compile on 1.4 with the -target 1.3 option to compile it to 1.3 version but that would also involve changing the deployed JARs, so at some or the other point the production system has to be brought down for a moment. The easier option is to bring it down for a smaller time, change the JAVA_HOME and then restart the application.
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

LVL 30

Expert Comment

by:Mayank S
ID: 16243955
>> is there any possibility to get the issues?

If you have used any methods/ classes which were introduced in 1.4, then yes. Otherwise it should be ok.
LVL 10

Assisted Solution

radarsh earned 400 total points
ID: 16243962
You most likely will end up getting an UnsupportedClassVersionError at runtime.
Also, some of the API used in 1.4 might not be available in 1.3. So, you might
have serious problems.

LVL 23

Assisted Solution

by:Siva Prasanna Kumar
Siva Prasanna Kumar earned 400 total points
ID: 16244317
i think if you are not using any java 1.4 Api you may not have any problem but even if you have any serialized components you may get serialization mismatch error.
and about the web side if you have used j2ee 1.3 with jdk 1.4 and now shifting only the jdk from jdk 1.4 to jdk1.3. no much diffrence may be seen as J@EE is the same yet.
LVL 12

Assisted Solution

Giant2 earned 400 total points
ID: 16244873
>by mistake the JAVA_HOME was pointed to JDK1.3
Correct this wrong pointing.
If you use Unix/Linux/Aix you can create a virtual directory pointing correctly.
Bye, Giant.

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

An old method to applying the Singleton pattern in your Java code is to check if a static instance, defined in the same class that needs to be instantiated once and only once, is null and then create a new instance; otherwise, the pre-existing insta…
Java Flight Recorder and Java Mission Control together create a complete tool chain to continuously collect low level and detailed runtime information enabling after-the-fact incident analysis. Java Flight Recorder is a profiling and event collectio…
Viewers will learn about arithmetic and Boolean expressions in Java and the logical operators used to create Boolean expressions. We will cover the symbols used for arithmetic expressions and define each logical operator and how to use them in Boole…
This theoretical tutorial explains exceptions, reasons for exceptions, different categories of exception and exception hierarchy.
Suggested Courses
Course of the Month20 days, 6 hours left to enroll

872 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question