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] Closed: (HARMONY-3398) [classlib][swing] UIDefaults.getUIClass() uses wrong classloader
Date Mon, 19 Mar 2007 18:46:32 GMT

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

Vasily Zakharov closed HARMONY-3398.
------------------------------------


Thanks, Alexey, the patch applied fine.

Verified, closing.


> [classlib][swing] UIDefaults.getUIClass() uses wrong classloader
> ----------------------------------------------------------------
>
>                 Key: HARMONY-3398
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3398
>             Project: Harmony
>          Issue Type: Bug
>          Components: Classlib
>            Reporter: Vasily Zakharov
>         Assigned To: Alexey Petrenko
>         Attachments: Harmony-3398-fix.patch, Harmony-3398-test.patch, Harmony-3398-test.patch
>
>
> For now getUIClass(String) uses ClassLoader.getSystemClassLoader() while it should pass
null to getUIClass(String, ClassLoader) instead, as the spec states:
> Returns: the Class object returned by getUIClass(uiClassID, null)
> Also, getUIClass(String, ClassLoader), if passed null classloader, now passes that null
to class.forName(), which makes third-party classes loaded by non-system classloader unavailable
for this method. It looks like using Thread.currentThread().getContextClassLoader() instead
is a proper solution. Reasons for using "false" in Class.forName() are also unclear.
> 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.

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


Mime
View raw message