Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
We have one scenario where we don’t want to change the server JVM which is running on Java 1.4. But the client is using Java 1.5, and we are getting exceptions while calling the EJB. We are not sure whether it’s our application issue or an EJB server-client JVM compatibility issue.
You deal with forward compatibility (FC) because you are trying to run new client (1.5) with old server (1.4). Java is not guarantee FC. It’s just guarantee backward compatibility (BC) as described in Incompatibilities in J2SE 5.0 since 1.4.2 (mirror at http://www.oracle.com):
Note: Sun documentation writers call the term backward compatibility as upward compatibility (they describe it as “class files built with version 1.4.2 compilers will run
correctly in JDK 5.0”) , but this is a mistake, because: backward==downward (wiki) and forward==upward (wiki).