Olaf Heimburger's Blog

See this post as a follow-up on my  Make JDev 10.1.3 talk to Oracle AS 10.l.2 post from last year.

The Issue

Having applied patch 4676768 or related to your still existing Oracle
AS 10.1.2.x instance helps to communicate with newer Oracle AS 10.1.3
based applications. As long as these are behaving correctly.

In case of an exception you'll end up with a

oracle.oc4j.rmi.OracleRemoteException: Class not found: com.evermind.server.rmi.OrionRemoteException

This is quite unfortunate as the exception might contain valuable information for the application or the developer.

Approach 1

The usual reflex is to include the client library (oc4jclient.jar) from
OC4J 10.1.2.x. Although this works in most cases, this might lead to
other library or class version conflicts.

Approach 2

Create a simple library to be included in the class path. This library just contains the com.evermind.server.rmi.OrionRemoteException class from the aforementioned library. For good reasons you shouldn't do this either, as it might be a License Agreement violation and your lawyers should be pretty alert. I also hate to include unneeded libraries into the class path.

Approach 3

Ask the vendor to include the missing com.evermind.server.rmi.OrionRemoteException class into OC4J 10.1.3 class path. This is the best and therefore I've filed Bug 6252184 to get it solved.