[
https://issues.apache.org/jira/browse/GERONIMO-2690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465370
]
Rakesh Midha commented on GERONIMO-2690:
----------------------------------------
Oh I missed to give some important points for the patch.
Please note:
1. The links are marked by "link::', so any class or classloader starting with
"link::" may not work properly, but I don't think we will have any classloader,
class or interface name starting with 'link::'
2. For dojo tree link loading 'afterExpand' event is used, ideally
'beforeExpand' should be used, but 'beforeExpand' event is never published in
current dojo version.
3. All the methods in ClassLoaderRegistry are synchronized for thread avoiding
concurent modification.
Thanks
Rakesh
> New view for all the classloaders and classes loaded in it
> ----------------------------------------------------------
>
> Key: GERONIMO-2690
> URL: https://issues.apache.org/jira/browse/GERONIMO-2690
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: console
> Affects Versions: 2.0
> Environment: Any
> Reporter: Rakesh Midha
> Assigned To: Kevan Miller
> Fix For: 2.0
>
> Attachments: classloader.gif, classloaderView2690.patch,
> classloaderViewLinks.patch, common.patch
>
>
> Looking into the classloader problems and knowing which classsloader loaded
> which class has always been a big problem in app servers.
> So many times we hit ClassNotFoundException and wonder why is it happening
> when the classes are available in my module. It may be because those classes
> are loaded by some other classloader.
> I think it would be nice if we can add a view in console which shows are the
> classloaders and the classes they loaded.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
