You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Andrew Zhang (JIRA)" <ji...@apache.org> on 2006/08/15 05:47:14 UTC

[jira] Updated: (HARMONY-1051) [classlib][nio_char] Use system classloader as an alternative to load charset provider classes when thread's context classloader fails to load them.

     [ http://issues.apache.org/jira/browse/HARMONY-1051?page=all ]

Andrew Zhang updated HARMONY-1051:
----------------------------------

    Attachment: Harmony-1051.diff

Hi,

According to the mailing list discussion, Harmony will use system classloader to load configuration file and provider classes if context classloader failed to load them.

The patch will fix this problem. Would you please have a try? Thanks!

Best regards,
Andrew




> [classlib][nio_char] Use system classloader as an alternative to load charset provider classes when thread's context classloader fails to load them.
> ----------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HARMONY-1051
>                 URL: http://issues.apache.org/jira/browse/HARMONY-1051
>             Project: Harmony
>          Issue Type: Improvement
>          Components: Classlib
>            Reporter: Andrew Zhang
>         Attachments: Harmony-1051.diff
>
>
> As we dicussed on the mailing list[1],  using system classloader as an alternative to load charset provider classes when thread's context classloader fails to load them will be a good choice to follow RI while keeping compliant with spec.
> I'll upload a patch for this improvement soon.
> Thanks!
> Best regards,
> Andrew
> [1] mailing list thread: [classlib][nio-charset] RI is inconsistent with spec when loading charset provider

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira