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 07:57:27 UTC

[jira] Updated: (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:all-tabpanel ]

Rakesh Midha updated GERONIMO-2689:
-----------------------------------

    Attachment: jndi.gif
                jndiview2689.patch
                common.patch

> 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
>
>
> 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