tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Olivier Lamy (*$^¨%`£) (JIRA) <j...@apache.org>
Subject [jira] [Updated] (MTOMCAT-90) useNaming not very useful; perhaps use StandardServer to make it more useful
Date Mon, 04 Nov 2013 03:37:17 GMT

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

Olivier Lamy (*$^¨%`£) updated MTOMCAT-90:
------------------------------------------

    Fix Version/s: backlog

> 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.1#6144)

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


Mime
View raw message