New OC4JClient - The SCAM By Patricbensen - is the information you are looking for, and in the blog All Specs Gadget we have provided her, all right in this article titled New OC4JClient - The SCAM By Patricbensen we will discuss it in full, in addition to the information we have also provided a lot of info about the latest gadgets and a wide range of tips and tricks that according to the gadget you are using, well please continue reading:

Articles: New OC4JClient - The SCAM By Patricbensen
Full Link : New OC4JClient - The SCAM By Patricbensen
Artikel oracle,

New OC4JClient - The SCAM By Patricbensen

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.

Information New OC4JClient - The SCAM By Patricbensen has finished we discussed

says the article New OC4JClient - The SCAM By Patricbensen, we beharap be useful to you in finding repensi about the latest gadgets and long.

Information on New OC4JClient - The SCAM By Patricbensen has finished you read this article and have the link https://patricbensen.blogspot.com/2007/03/new-oc4jclient-scam-by-patricbensen.html Hopefully the info we deliver is able to address the information needs of the present.