openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simon Droscher (JIRA)" <>
Subject [jira] Commented: (OPENJPA-384) ClassCastException when trying to load OpenJPA 1.0.0 based webapp in WebLogic 10
Date Wed, 26 Sep 2007 14:45:50 GMT


Simon Droscher commented on OPENJPA-384:

Just to be clear - it isn't through any configuration of mine that weblogic.kodo.WebLogicLogFactory
gets involved. It is something WebLogic is doing automatically.

In fact, if  I explicity try to set my openjpa.Log configuration to anything, a warning comes
up in the startup along the lines of

<BEA-160202><You have specified a openjpa.Log setting in your configuration for persistence
unit "myopenjpa". This setting will be ignored, and all log messages will be sent to the WebLogic
logging subsystem. Trace-level logging is controlled by the various JPA-specific debug settings
in config.xml, or via the WebLogic console.>

It is possible there may be an undocumented "tweak" in the OpenJPA 0.9.7 included with WebLogic
10 that BEA have made to facilitate this redirecting of the log output. If I take the OpenJPA
1.0.0 jar out of my WEB-INF/lib and just use the WebLogic shipped 0.9.7, this error doesn't
occur. However, this is not an option as my application relies on some of the 1.0.0 bug fixes
and API changes.

> ClassCastException when trying to load OpenJPA 1.0.0 based webapp in WebLogic 10
> --------------------------------------------------------------------------------
>                 Key: OPENJPA-384
>                 URL:
>             Project: OpenJPA
>          Issue Type: Bug
>    Affects Versions: 1.0.0
>         Environment: WebLogic 10
>            Reporter: Simon Droscher
> I am trying to deploy a web application which uses OpenJPA 1.0.0 into a WebLogic 10 environment.
The application deployment (and subsequent startup) fails with the following error:
> {code}java.lang.ClassCastException: weblogic.kodo.WebLogicLogFactory
> 	at org.apache.openjpa.lib.conf.ConfigurationImpl.getLogFactory(
> 	at org.apache.openjpa.lib.conf.ConfigurationImpl.getLog(
> 	at org.apache.openjpa.conf.OpenJPAConfigurationImpl.getConfigurationLog(
> 	at org.apache.openjpa.persistence.PersistenceProductDerivation$ConfigurationProviderImpl.setInto(
> 	at org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.newInstance(
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> 	at java.lang.reflect.Method.invoke(
> 	at org.apache.openjpa.kernel.Bootstrap.invokeFactory(
> 	at org.apache.openjpa.kernel.Bootstrap.newBrokerFactory(
> 	at org.apache.openjpa.persistence.PersistenceProviderImpl.createContainerEntityManagerFactory(
> 	at org.apache.openjpa.persistence.PersistenceProviderImpl.createContainerEntityManagerFactory(
> 	at weblogic.deployment.PersistenceUnitInfoImpl.createEntityManagerFactory(
> 	at weblogic.deployment.PersistenceUnitInfoImpl.<init>(
> {code}
> There doesn't seem to be any details or documentation on running apps based on newer
versions of OpenJPA under WebLogic 10 (which packages OpenJPA 0.9.7 as part of Kodo).

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message