openjpa-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kevin Sutter <>
Subject Re: oracle clob exception
Date Wed, 29 Aug 2012 17:19:39 GMT
*>  The uniqueness of my situation is that i'm running in OSGI environment..

You probably hit the nail on the head...  I didn't see your connection
between the loading of the oracle.sql package and the osgi classloading
environment.  It's probably dependent on your osgi environment.  The
current context classloader seems to work in WebSphere's osgi runtime for
loading these oracle classes, but this wouldn't be the first disconnect
between various osgi environments.  Which osgi runtime are you running with?

I would suggest opening a JIRA.  Since you have a workaround, you can make


On Wed, Aug 29, 2012 at 10:36 AM, garpinc <> wrote:

> I'm using version 2.2.0.
> The uniqueness of my situation is that i'm running in OSGI environment..
> Basically I have a database bundle which has all the drivers and provides a
> service the can supply a jdbc DataSource.
> oracle.sql package is not exported.
> Then I have a client bundle that configures OpenJPA with a datasource
> provided by that service.
> In order to not get the described exception I had to do an optional
> dependency on the oracle.sql package which is not ideal since now the
> client
> bundle has to know about the oracle driver bundle.
> So I'm looking for some kind of workaround in JPA that would use the
> DataSource class path instead to find the oracle.sql.CLOB object..
> --
> View this message in context:
> Sent from the OpenJPA Users mailing list archive at

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message