This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
I am struggling with the java.lang.UnsupportedClassVersionError error that I received from running my java program in IBM Websphere Rational Developer Edition version 7 and Websphere Application Server v7. I try to understand what does the error meant; so if you have any clue about what does the error mean, please let me know. I wonder if these errors related to the WAS or JRE given the fact that I am running on WAS 7 , RAD 7.5, and JRE v6 . Hope it help to shed some lights on figuring out what the error is.
The error is as follow :
java.lang.UnsupportedClassVersionError: org/eclipse/emf/ecore/resource/Resource$Factory$Registry (Unsupported major.minor version 49.0)
at java.lang.ClassLoader.defineClass0(Native Method)
at java.security.AccessController.doPrivileged1(Native Method)
Thank you so much Fred,
Yes, you are exactly right. I jjust checked and it turned out to be exactly what you said.
Since I am runiing on WAS 7 meaning I am compiling with Java 7 , right ? , and I check my java build path and I see Web Sphere V6 JRE.
Since I am new, please correct me if I am wrong. So based on what you were mentioning that I were compiling my program on WAS 7 but I ran it in v6 JRE ; therefore the error was caused by compiling on Java version 7 but running it onn JRE v6.
Thanks for your help, I am now understand it. One more question if you don't mind, since I am running on the JRE V6 , and compile my program on version 7 and now i want to get rid of the error then what should i do?
Please correect me if i am wrong. Could i import the Web Sphere V7 JRE into my java build path library in order to make it compatible with my WAS v7 ?
If it is the case, how could i import the Web Sphere V7 JRE into my java build path?
The 49.0 version indicates the class is compiled with Java 5.0 (Java 7 is 51.0), so you're not using Java 6 but Java 1.4 or below. Perhaps some older JRE nested itself in the PATH variable before your Java 6 JRE. Oracle database products are notorious for doing this.