harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vasily Zakharov (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HARMONY-3420) [classlib][swing] UIDefaults.ProxyLazyValue.createValue() uses wrong classloader
Date Mon, 19 Mar 2007 11:11:32 GMT

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

Vasily Zakharov updated HARMONY-3420:

    Patch Info: [Patch Available]

> [classlib][swing] UIDefaults.ProxyLazyValue.createValue() uses wrong classloader
> --------------------------------------------------------------------------------
>                 Key: HARMONY-3420
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3420
>             Project: Harmony
>          Issue Type: Bug
>          Components: Classlib
>            Reporter: Vasily Zakharov
>         Assigned To: Alexey Petrenko
>         Attachments: Harmony-3420-fix.patch, Harmony-3420-test.patch
> UIDefaults.ProxyLazyValue.createValue() uses Class.forName(className) to instantiate
the underlying class, which makes third-party classes loaded by non-system classloader unavailable
for this method. It looks like using Class.forName(className, true, Thread.currentThread().getContextClassLoader())
instead is a proper solution.
> The test in the attached test patch passes on RI but fails on Harmony, and works fine
after the attached fix patch is applied.
> This issue was discovered while investigating issue HARMONY-3385. See also a similar
issue in HARMONY-3398.

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

View raw message