openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "garpinc (JIRA)" <>
Subject [jira] [Commented] (OPENJPA-646) JDK problems with defineClass and enum class types
Date Tue, 30 Jul 2013 22:19:50 GMT


garpinc commented on OPENJPA-646:

Yes. I'm indicating that this issue is related to OpenJPA-2399. I discovered how to enable
the javaagent aspect of the test case. This allowed me to first replicate the issue referenced
in this JIRA and then I did the prescribed uncomment in the TemporaryClassLoader that resulted
in the fix. Then I changed the test class to an enum class and I got the symptoms of OpenJPA-2399..
Feel free to contact me on skype with handle garpinc to follow up. I got diverted temporarily
to a different project but now i'm back dealing with this issue again.
> JDK problems with defineClass and enum class types
> --------------------------------------------------
>                 Key: OPENJPA-646
>                 URL:
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: kernel
>    Affects Versions: 1.2.0
>            Reporter: Kevin Sutter
>            Assignee: Kevin Sutter
>             Fix For: 1.2.1, 1.3.0
>         Attachments: openjpa-646.patch,
> This Issue was first presented on our dev mailing list:
> I have also shared some additional experiences with Abe to get his views, but haven't
heard anything back yet.  So, I will create this JIRA Issue and work it from there.
> The original problem was limited to the Sun JDK.  But, in a soon-to-be-available update
to the IBM JDK, the same problem surfaces.  At least the same exception is presented.  The
actual call stack is different due to the different Sun and IBM packages, but it's a similar
> Basically, we are having a problem with our TempClassLoader attempting to use the defineClass()
method on the CascadeType enum class.  Our javax.persistence.CascadeType version doesn't experience
this problem because we use Class.forName() to load the javax classes.  In this scenario,
I have an alt.persistence.CascadeType that falls into our normal class definition processing
and attempts to use defineClass().  This method invocation completes okay.  But, later when
our code attempts to access the metadata associated with this type, we get the ArrayStoreException
from the JDK.
> I will post both a simple project that reproduces the problem as well as a "hack" patch
that gets us around the problem.  I also have a PMR opened against the IBM JDK to see if they
can help resolve it.
> Kevin

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message