openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin Sutter (JIRA)" <>
Subject [jira] Issue Commented: (OPENJPA-429) Recent changes have caused problems building with IBM JDK
Date Tue, 13 Nov 2007 14:49:05 GMT


Kevin Sutter commented on OPENJPA-429:

I've narrowed the problem down to the @ReadOnly annotation processing.  Although we have had
this annotation for quite some time in OpenJPA, some recent test additions just surfaced this
problem.  Entity class org.apache.openjpa.persistence.jdbc.annotations.ExtensionsEntity uses
the @ReadOnly annotation.  For some reason, the IBM JDK is having problems loading the UpdateAction
class necessary for the "value" parameter.  I've tried experimenting with this annotation
definition and usage to see if I could workaround the problem, but nothing yet.  I will follow
up with the IBM JDK team to see how we can get this resolved.

I am currently running with SR5 of the IBM JDK:

java full version "J2RE 1.5.0 IBM Windows 32 build pwi32dev-20070511 (SR5)"

According to the posts that Mike made on the dev mailing list, he also tried with a newer
version of the JDK.  I will need to verify that before I can post a problem report to the
IBM JDK anyway.


> Recent changes have caused problems building with IBM JDK
> ---------------------------------------------------------
> common.concepts.key: OPENJPA-429
> common.concepts.url:
>common.concepts.project: OpenJPA
>common.concepts.issuetype: Bug
>common.concepts.components: build / infrastructure
>    Affects Versions: 1.1.0
>issue.field.reporter: Kevin Sutter
> This started on the dev mailing list:
> Trunk (1.1.0) is not building with the IBM JDK.  It is building okay with the Sun JDK.
 It's not always consistent, but an example call stack is as follows:
> 2000  test  WARN   [main] openjpa.Enhance - Type "class org.apache.openjpa.enhance.TestEnhancementConfiguration"
has no metadata; enhancing as persistence aware. If you intended for "class org.apache.openjpa.enhance.TestEnhancementConfiguration"
to be persistence-capable, then this means that OpenJPA could not find any metadata for "class
> This can happen if the directory containing your metadata is not in your CLASSPATH, or
if your metadata files are not named properly. See the documentation on metadata placement
for more information.
> java.lang.ClassFormatError
>         at java.lang.ClassLoader.defineClassImpl(Native Method)
>         at java.lang.ClassLoader.defineClass(
>         at java.lang.ClassLoader.defineClass(
>         at org.apache.openjpa.lib.util.TemporaryClassLoader.loadClass(
>         at org.apache.openjpa.lib.util.TemporaryClassLoader.loadClass(
>         at
>         at$000(
>         at$AnnotationInvocationHandler.invoke(
>         at $Proxy27.value(Unknown Source)
>         at org.apache.openjpa.persistence.AnnotationPersistenceMetaDataParser.parseReadOnly(
>         at org.apache.openjpa.persistence.AnnotationPersistenceMetaDataParser.parseMemberAnnotations(
>         at org.apache.openjpa.persistence.AnnotationPersistenceMetaDataParser.parseClassAnnotations(
>         at org.apache.openjpa.persistence.AnnotationPersistenceMetaDataParser.parse(
>         at org.apache.openjpa.persistence.PersistenceMetaDataFactory.load(
>         at org.apache.openjpa.meta.MetaDataRepository.getMetaDataInternal(
>         at org.apache.openjpa.meta.MetaDataRepository.getMetaData(
>         at org.apache.openjpa.enhance.PCEnhancer.<init>(
>         at
>         at org.apache.openjpa.ant.PCEnhancerTask.executeOn(
>         at org.apache.openjpa.lib.ant.AbstractTask.execute(
>         at
>         at
>         at
>         at org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(
>         at org.apache.maven.plugin.antrun.AntRunMojo.execute(
>         at org.apache.maven.plugin.DefaultPluginManager.executeMojo(
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
>         at org.apache.maven.DefaultMaven.doExecute(
>         at org.apache.maven.DefaultMaven.execute(
>         at org.apache.maven.cli.MavenCli.main(
>         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.codehaus.classworlds.Launcher.launchEnhanced(
>         at org.codehaus.classworlds.Launcher.launch(
>         at org.codehaus.classworlds.Launcher.mainWithExitCode(
>         at org.codehaus.classworlds.Launcher.main(
> [INFO]
> ------------------------------------------------------------------------
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Error executing ant tasks
> Embedded error: java.lang.ClassFormatError

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

View raw message