[jira] Resolved: (HARMONY-1940) [classlib][[pack200] Implementing adapter for standard factory lookup

["Paulex Yang (JIRA)" <ji...@apache.org>]

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

Paulex Yang resolved HARMONY-1940.
----------------------------------

    Resolution: Fixed

Alex, patch applied at revision r467417, thanks a lot for this enhancement, please verify that the problem is fully fixed as you expected.


> [classlib][[pack200] Implementing adapter for standard factory lookup
> ---------------------------------------------------------------------
>
>                 Key: HARMONY-1940
>                 URL: http://issues.apache.org/jira/browse/HARMONY-1940
>             Project: Harmony
>          Issue Type: Improvement
>          Components: Classlib
>            Reporter: Alex Blewitt
>         Assigned To: Paulex Yang
>            Priority: Trivial
>         Attachments: pack200-java-util-jar.patch, pack200-pack200adapter.patch
>
>
> This adds functionality to hook the pack200 factory to the harmony implementation such that Pack200.newPacker() and Pack200.newUnpacker() return instances of the harmony implementation.
> Note that I have discovered a bug in the standard Sun implementation in that when the system property is specified as the harmony implementation, the packer fails to find the class due to not being on the system boot classpath. I feel that the use of the ClassLoader.getSystemClassLoader() may result in the same situation for harmony, especially if the harmony code is shipped in a different Jar. The only solution for the Sun VM to use the harmony implementation is to put it on the system classpath.
> I'm largely recording that as an issue here since it may affect our s in the same way in the future.

-- 
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