You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by "Benson Margulies (JIRA)" <ji...@apache.org> on 2014/11/29 02:32:12 UTC

[jira] [Closed] (MTOMCAT-90) useNaming not very useful; perhaps use StandardServer to make it more useful

     [ https://issues.apache.org/jira/browse/MTOMCAT-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benson Margulies closed MTOMCAT-90.
-----------------------------------
    Resolution: Invalid

No longer relevant.

> useNaming not very useful; perhaps use StandardServer to make it more useful
> ----------------------------------------------------------------------------
>
>                 Key: MTOMCAT-90
>                 URL: https://issues.apache.org/jira/browse/MTOMCAT-90
>             Project: Apache Tomcat Maven Plugin
>          Issue Type: Bug
>    Affects Versions: 1.1
>            Reporter: Benson Margulies
>             Fix For: backlog
>
>
> While the Tomcat 'Embedded' class has 'useNaming', it's not useful. This is because the rest of Tomcat won't actually set up the full JNDI foundation unless the NamingContextListener is deployed inside of a container that implements Server or Context. The plugin does not use StandardServer to be a server, and nothing in the plugin will add the NamingContextListener to a context.
> One possible response here is to remove the option; another is to add StandardServer, a third is to add that listener to the context when useNaming is turned on. 
> I suppose that it's hypothetically possible for someone to use context.xml to add the NamingContextListener.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org