Hibernate – JPA2 Provider as Hibernate in Weblogic 12.1

hibernatejpa-2.0weblogic12c

I am getting below exception when we try to deploy our application with JPA2 Provider as Hibernate in weblogic 12.1

   Caused By: java.lang.ClassCastException: org.eclipse.persistence.jpa.PersistenceProvider cannot be cast to javax.persistence.spi.PersistenceProvider

    at javax.persistence.Persistence$1.isLoaded(Persistence.java:92)

    at org.hibernate.validator.internal.engine.resolver.JPATraversableResolver.isReachable(JPATraversableResolver.java:57)

I have below entries in weblogic.xml :

        <package-name>org.hibernate.*</package-name>

        <package-name>javax.persistence.*</package-name>

    </prefer-application-packages>

and below pre class path setting in weblogic server commEnv.cmd (common/bin).

 set PRE_CLASSPATH=%MW_HOME%\modules\javax.persistence_2.0.0.0_2-0.jar;

Application works fine in weblogic 11g with below pre class path setting.

PRE_CLASSPATH="/apps/Oracle/Middleware/modules/javax.persistence_1.0.0.0_2-0-0.jar:/apps/Oracle/Middleware/modules/com.oracle.jpa2support_1.0.0.0_2-0.jar"

There was as addition jar com.oracle.jpa2support_1.0.0.0_2-0.jar. This jar is missing in weblogic 12.1 modules directory.

Could anyone suggest how to resolve the persistence provider conflict issue in weblogic 12.1 ?

Hibernate Jar Versions : hibernate-core-4.2.0.Final.jar, hibernate-jpa-2.0-api-1.0.1.Final.jar, hibernate-validator-4.3.1.Final.jar

Best Answer

It worked after removing below package from weblogic.xml

 <package-name>javax.persistence.*</package-name>

Also PRE_CLASSPATH setting is not required for 12c

Related Solutions

Java – What are the possible values of the Hibernate hbm2ddl.auto configuration and what do they do

From the community documentation:

hibernate.hbm2ddl.auto Automatically validates or exports schema DDL to the database when the SessionFactory is created. With create-drop, the database schema will be dropped when the SessionFactory is closed explicitly.

e.g. validate | update | create | create-drop

So the list of possible options are,

validate: validate the schema, makes no changes to the database.
update: update the schema.
create: creates the schema, destroying previous data.
create-drop: drop the schema when the SessionFactory is closed explicitly, typically when the application is stopped.
none: does nothing with the schema, makes no changes to the database

These options seem intended to be developers tools and not to facilitate any production level databases, you may want to have a look at the following question; Hibernate: hbm2ddl.auto=update in production?

Parallelism in GPU – CUDA / OpenCL

Parallelism on GPUs is SIMT (Single Instruction Multiple Threads). For CUDA Kernels, you specify a grid of blocks where every block has N threads. The CUDA library does all the trick and the CUDA Compiler (nvcc) generates the GPU code which is executed by the GPU. The CUDA library tells the GPU driver and further more the thread scheduler on the GPU how many threads should execute the kernel ((number of blocks) x (number of threads)). In your example the top level function (or host function) executes only the kernel call which is asyncronous and returns emediatly. No threading library is needed because nvcc creates the calls to the driver.

A sample kernel call looks like this:

helloworld<<<BLOCKS, THREADS>>>(/* maybe some parameters */);

OpenCL follows the same paradigm but you compile yor kernel (if they are not precompiled) at runtime. Specify the number of threads to execute the kernel and the lib does the rest.

The best way to learn CUDA (OpenCL) is to look in the CUDA Programming Guide (OpenCL Programming Guide) and look at the samples in the GPU Computing SDK.

Related Topic