db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Craig Russell (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JDO-488) Use of JDK 1.6 with TCK: ClassLoader.loadClass cannot load arrays in JDK 1.6
Date Wed, 16 May 2007 21:02:16 GMT

     [ https://issues.apache.org/jira/browse/JDO-488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Craig Russell resolved JDO-488.

       Resolution: Fixed
    Fix Version/s: JDO 2 maintenance release 1
         Assignee: Craig Russell

svn ci --force-log -m JDO-488 Update for Java 1.6 loading array classes by special name, e.g.
Patch submitted by David Ezzio (thanks). --username clr --password ******* --non-interactive
--config-dir /Users/clr/.netbeans/5.5/config/svn/config --targets /tmp/targets_checkin_922
Sending        /Users/clr/apachejdo/jdo/trunk/tck20/src/java/org/apache/jdo/tck/util/signature/SignatureVerifier.java
Transmitting file data .
Committed revision 538728.

> Use of JDK 1.6 with TCK: ClassLoader.loadClass cannot load arrays in JDK 1.6
> ----------------------------------------------------------------------------
>                 Key: JDO-488
>                 URL: https://issues.apache.org/jira/browse/JDO-488
>             Project: JDO
>          Issue Type: Bug
>          Components: tck2
>    Affects Versions: JDO 2 final
>         Environment: Use of JDK 1.6 when running TCK.
>            Reporter: David Ezzio
>         Assigned To: Craig Russell
>             Fix For: JDO 2 maintenance release 1
>         Attachments: jdoLoadClass.patch
> In JDK 1.5 and prior versions of Java 2, the name returned by Class.getName() could be
used with ClassLoader.loadClass to load array types.  This behavior was considered a bug that
has been fixed in JDK 1.6.  As a result, calls using encoded array names such as "L[java.lang.Object;"
now fail with a ClassNotFoundException.
> See Sun's Java CR 6446627 (http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6446627)
et alia.  
> The recommended practice (and the only available option in JDK 1.6) is to use Class.forName(name,
verify, classloader) to load a class with a specific class loader within the application.

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

View raw message