[
https://issues.apache.org/jira/browse/GERONIMO-2689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevan Miller reassigned GERONIMO-2689:
--------------------------------------
Assignee: Kevan Miller (was: Rakesh Midha)
Rakesh, I'll see if I can get this integrated, today. A few comments:
1) you've added "Finalize()" methods to the ClassLoaders. Assume this should be
"finalize()". I'd probably prefer to use destroy() or a combination of
destroy()/finalize(). Would have to convince myself that there weren't any
circular references that could keep the weak reference alive. Would be great if
we could track un-GC'ed classloaders...
2) The patch had some disparities with current source. All hunks succeed, but
seemed to have been generated from slightly downlevel source.
I'll follow up on Paul's comment about using plug-ins.
> New View for JNDI name in all the contexts
> ------------------------------------------
>
> Key: GERONIMO-2689
> URL: https://issues.apache.org/jira/browse/GERONIMO-2689
> 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: allviews.patch, common.patch, jndi.gif,
> jndiview2689.patch, navigation.gif
>
>
> So many times we hit the Exception NamingNotFound, most of the times it
> happens because of user error, missing references, wrong names or path or
> user working in different context and system looking in some other context.
> I think it would be nice if in a console we can have a view of what all names
> are binded or available in contexts of each application / module or component.
--
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
