We help IT Professionals succeed at work.

We've partnered with Certified Experts, Carl Webster and Richard Faulkner, to bring you a podcast all about Citrix Workspace, moving to the cloud, and analytics & intelligence. Episode 2 coming soon!Listen Now

x

Copile JDK1.4.2_10 & run with JDk1.3

krishnasaikarthik
on
Medium Priority
540 Views
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?

thanks
km.






Comment
Watch Question

Java Developer
CERTIFIED EXPERT
Top Expert 2010
Commented:
suggest either shifting production to 1.4.2
or shifting development to 1.3

Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts
Mick BarryJava Developer
CERTIFIED EXPERT
Top Expert 2010

Commented:
you can also use -target 1.3 compile option to produce 1.3 compatible class files but you could still have incompaibilities.
Mayank SPrincipal Technologist
CERTIFIED EXPERT
Commented:
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.
Mayank SPrincipal Technologist
CERTIFIED EXPERT

Commented:
>> 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.
Commented:
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.


________
radarsh
Siva Prasanna KumarPrincipal Solutions Architect
CERTIFIED EXPERT
Top Expert 2006
Commented:
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.
Commented:
>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.
Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.