You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Rakesh Midha (JIRA)" <ji...@apache.org> on 2007/01/05 08:15:27 UTC

[jira] Commented: (GERONIMO-2689) New View for JNDI name in all the contexts

    [ https://issues.apache.org/jira/browse/GERONIMO-2689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462421 ] 

Rakesh Midha commented on GERONIMO-2689:
----------------------------------------


Attached is the common.patch and jndiview2689.patch which implements JNDI Viewer console view. 

The jndi.gif file shows how this view will look.

This patch adds console-standard.JMXViewer entity in portlet registry and also adds all the required redirections and entries in web.xml.

The approach is to use componentContext gbean attribute from each component to get the context for component and than show it in dojo tree. To load dojo tree nodes lazily, the StringTree instances are converted to JSON string, and setChildren is called to lazy loading of childrens on expension. 

It adds JNDIViewPortlet.java, which getJSONTrees() build the json tree using kernel getattribute method on component gbeans.

To use the patches first apply common.patch which adds StringTree.java and TreeDocIcon.css
and than apply jndiview2689.patch. The common patch is also used in JIRA 2690 and 2691.

> 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: Rakesh Midha
>             Fix For: 2.0
>
>         Attachments: 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