You can check the manifest.mf (in the META-INF) directory. This should usually contain the version used with which the jar was build
(for example entries like: Created-By: R28.2.0-79-146777-1.6.0_29-20111005-1808-windows-ia32 (Oracle Corporation) or Build-Jdk: 1.4.2_09
indicate which JDK was used).
When the build JDK is higher then the version you are using you are in trouble, but usually a jar (or application) build with an older
JDK can run in a newer version. Can you run your application in JDK6? - then you can also use the new wlclient.jar
Hi Rene, really appreciate your answer...
yes it run in JDK6 because wlclient.jar/wlthint3client.jar from web logic 12 c is build from JDK6.
In my case, i have a constraint that I have to use JDK5 (not 6) to connect to WebLogic 12c in which the wlclient.jar/wlthint3client.jar provided (by weblogic 12c) is not supported JDK5...
So how to connect to Weblogic 12c using JDK5 ?
You could try connecting to WebLogic12c by using a wlclient.jar that is provided with an older version of WebLogic, for example 9.2
A version can be downloaded here: http://www.oracle.com/technetwork/middleware/ias/downloads/wls-main-097127.html
If you have Oracle support, you can also try if they can build you a version with JDK5.
got it, Thanks Vijaya.
Have you ever meet this issue when using wlclient.jar in my webapplication. but it can works well in my local main method. below is exception when running in jboss.
javax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.INITIALIZE vmcid: 0x0 minor code: 0 completed: No]