You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@commons.apache.org by "Emmanuel Bourg (JIRA)" <ji...@apache.org> on 2014/04/24 15:22:18 UTC

[jira] [Updated] (BCEL-6) Repository#lookupClass no longer returns JavaClasses added with Repository#add

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

Emmanuel Bourg updated BCEL-6:
------------------------------

      Description: 
This call is delegated to SyntheticRepostitory loadClass. This method doesn't check for loaded classes. This prevents memory only JavaClass's to be verified. Repository#add adds such JavaClass's to the loaded classes hash, but the validator only calls lookupClass. one of the two has to check for loaded classes, for two reasons.
a) performance
b) verifying classes hold in memory

  was:
This call is delegated to SyntheticRepostitory loadClass. This method doesn't 
check for loaded classes. This prevents memory only JavaClass's to be verified.
Repository#add adds such JavaClass's to the loaded classes hash, but the 
validator only calls lookupClass.
one of the two has to check for loaded classes, for two reasons.
a) performance
b) verifing classes hold in memory

         Priority: Major
      Environment:     (was: Operating System: other
Platform: All)
    Fix Version/s: 5.1
         Priority:   (was: P3)
         Severity:   (was: normal)

> Repository#lookupClass no longer returns JavaClasses added with Repository#add
> ------------------------------------------------------------------------------
>
>                 Key: BCEL-6
>                 URL: https://issues.apache.org/jira/browse/BCEL-6
>             Project: Commons BCEL
>          Issue Type: Bug
>          Components: Main
>    Affects Versions: 5.0
>            Reporter: Peter Schneider
>            Assignee: Apache Commons Developers
>             Fix For: 5.1
>
>
> This call is delegated to SyntheticRepostitory loadClass. This method doesn't check for loaded classes. This prevents memory only JavaClass's to be verified. Repository#add adds such JavaClass's to the loaded classes hash, but the validator only calls lookupClass. one of the two has to check for loaded classes, for two reasons.
> a) performance
> b) verifying classes hold in memory



--
This message was sent by Atlassian JIRA
(v6.2#6252)