Gadget blog, Android KitKat, stock firmware, Unboxing, Toggle Mod Major Crashing Bug Fixed, Android Jelly Bean, Studio Mobile, Apk + DATA, How To Set, Unlocker Photo In WhatsApp, Majestic Tab Firmware Flash File

OC4JClient - The SCAM

OC4JClient - The SCAM - welcome to the blog Gadget Blog we provide information about the latest gadgets, which we provide for you for a while, now we discuss about OC4JClient - The SCAM we have collected a lot of information about this article from many reliable sources, so please see:

Articles : OC4JClient - The SCAM
full Link : OC4JClient - The SCAM

You can also see our article on:


OC4JClient - The SCAM

You'd think that when Oracle packages a jar called oc4jclient.jar, you'd be safe using it within your client (ejb client, jms client) applications with no problems whatsoever.... well, if you did, you'd be ...well...WRONG!
You might also encounter stacktraces like these after deploying your EJB/JMS client:

Exception in thread "main" java.lang.NoClassDefFoundError: com/evermind/server/jms/EvermindXAConnectionFactory
at com.evermind.server.jms.ConnectInfo.getPass(ConnectInfo.java:98)
at com.evermind.server.jms.EvermindQueueConnectionFactory.createQueueConnection(
EvermindQueueConnectionFactory.java:83)


There are a number of things to note before you even try to use the oc4jclient.jar:

  1. Oracle packages the client in a zip file. This file contains the oc4jclient.jar file and al lot of additional supporting libraries that it needs. Just check out the manifest.mf file present in oc4jclient.jar to marvel at the horrendous dependency list.

  2. In addition to the above, you will need to download an additional jar (ojdl.jar) required for the oc4jclient's internal logging purpose!. (How daft can this be!)

  3. You CANNOT distribute the OC4JClient (and its supporting libraries like dms.jar, optic.jar etc) unless you are an Oracle Customer and your client is an Oracle Customer. So be extremely careful while packaging and deploying your application.


  4. The OC4JClient (oc4jclient.jar along with supporting jars) is INADEQUATE if you want to build a client application that uses JMS (not OJMS). For this to work, you'll have to add oc4j.jar (i.e. the entire core runtime of the application server) just to make a standalone JMS client run (How clever is that?!)

The above definitely holds true for Oracle10gAS 10.1.2.02. I believe that with 10.1.3, some of these problems have been alleviated. However.....
The next time you develop an oc4j client application please keep the above points. This will avoid significant pain grief especially when trying to liaise with metalink/oracle tech support.



so much information about OC4JClient - The SCAM

just so much information about OC4JClient - The SCAM, hopefully can provide benefits for you,

you just read the information about OC4JClient - The SCAM if this article feel useful for you please bookmark or share again with link https://everythingnbeyondblog.blogspot.com/2007/03/oc4jclient-scam.html thanks.

Tag :
Share on Facebook
Share on Twitter
Share on Google+
Tags :

Related : OC4JClient - The SCAM

1 komentar: