PaaS Partner Community

  • September 2, 2015

How to fix java.io.InvalidClassException error when accessing Oracle ACM Case API via Jdeveloper by Vikram Bailur

Juergen Kress
PaaS Partner Adoption

clip_image002Here is a quick and useful tip. This was an error I got when I was running a custom java client to query the Oracle Adaptive Case Management API.

From a sort-of related metalink on Oracle which says :

Although the problem couldn't be recreated by the development team on demand, from the exception is clear that the root cause of the problem is the differnce of the version of the org.eclipse.persistence jar distributed with Oracle JDeveloper and Oracle WLS.

I figured this was something to do with the version of eclipselink libraries currently running on the soa server were different from Jdeveloper install.

In my JDeveloper project, I had some libraries and classpath pointing to my JDeveloper install and some others pointing to my SOA middleware home install for example. Read the complete article here.

SOA & BPM Partner Community

For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn image[7][2][2][2] Facebook clip_image002[8][4][2][2][2] Wiki

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.