You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Shawn Jiang (JIRA)" <ji...@apache.org> on 2010/05/05 07:16:04 UTC

[jira] Updated: (GERONIMO-5198) MultiParentClassLoader caching not found resources

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

Shawn Jiang updated GERONIMO-5198:
----------------------------------

    Fix Version/s: 2.2.1

> MultiParentClassLoader caching not found resources
> --------------------------------------------------
>
>                 Key: GERONIMO-5198
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-5198
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>    Affects Versions: 2.2
>         Environment: Linux 64 bit
>            Reporter: Marco Laponder
>             Fix For: 2.2.1
>
>
> We have extended the default classpath with a directory by specifying in the deployment plan an org.apache.geronimo.system.sharedlib.SharedLib gbean. So we are able to read application specific files from this directory.
> It is possbile for out application the resource  can not be found at a given time, but the resource exists at a later time because it has been added to the directory. However when geronimo doesn't find the resource its add its name to the 'resourcesNotFound' map in the MultiParentClassLoader.java:571 in the 2.2 branch.
> The result of this caching is that we cannot find the resource after it has been placed in the direcotry. Would it be possible to configure this behaviour, clear the not found cache or is there an other solution to this problem ?

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