You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Rick Curtis (JIRA)" <ji...@apache.org> on 2010/11/22 21:52:13 UTC
[jira] Closed: (OPENJPA-814) code review: found some code/hack for
unsupported JDK 1.3.1
[ https://issues.apache.org/jira/browse/OPENJPA-814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Curtis closed OPENJPA-814.
-------------------------------
Resolution: Won't Fix
Assignee: Rick Curtis
Since this one is going to be hard to prove/disprove, I think it is better to leave the sleeping dog alone.
> code review: found some code/hack for unsupported JDK 1.3.1
> -----------------------------------------------------------
>
> Key: OPENJPA-814
> URL: https://issues.apache.org/jira/browse/OPENJPA-814
> Project: OpenJPA
> Issue Type: Question
> Components: kernel
> Affects Versions: 2.0.0-M2
> Reporter: Fernando Padilla
> Assignee: Rick Curtis
> Priority: Trivial
>
> I just found some code that says it's there only to support jdk 1.3.1, but I assume that is not supported any longer.
> JDBCConfigurationImpl
> // this static initializer is to get past a weird
> // ClassCircularityError that happens only under IBM's
> // JDK 1.3.1 on Linux from within the JRun ClassLoader;
> // while exact causes are unknown, it is almost certainly
> // a bug in JRun, and we can get around it by forcing
> // Instruction.class to be loaded and initialized
> // before TypedInstruction.class
> try { serp.bytecode.lowlevel.Entry.class.getName(); }
> catch (Throwable t) {}
> try { serp.bytecode.Instruction.class.getName(); }
> catch (Throwable t) {}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.