You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "David Jencks (JIRA)" <ji...@apache.org> on 2009/10/23 19:55:59 UTC

[jira] Commented: (GERONIMO-4926) Fix ConfigurationMonitorGBean management of PCRegistry class.

    [ https://issues.apache.org/jira/browse/GERONIMO-4926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12769327#action_12769327 ] 

David Jencks commented on GERONIMO-4926:
----------------------------------------

It seems to me that geronimo should not be doing this kind of stuff, the osgi framework should.

> Fix ConfigurationMonitorGBean management of PCRegistry class. 
> --------------------------------------------------------------
>
>                 Key: GERONIMO-4926
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4926
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: osgi
>    Affects Versions: 3.0
>            Reporter: Rick McGuire
>
> The ConfigurationMonitorGBean maintains a cache of active configuration class loaders and when a configuration is shutdown, it tells the openjpa PCRegistry to remove any cached classes associated with that class loader.  This won't work any more because there is no such thing as a configuration class loader.   It might be possible to get the bundle for the class loader, then request the list of managed classes and iterate through the classes looking for any class that might be defined using a BundleReference class loader for that bundle.  If one is found, then that classloader can be used for the deregister() operation. 
> For now, the insertion of the map entries is disabled. 

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