org.apache.catalina.core.StandardServer of the JBoss-web.deployer systematicaly returns NULL against getGlobalNamingContext() call. ----------------------------------------------------------------------------------------------------------------------------------- Key: JBAS-7146 URL: https://jira.jboss.org/jira/browse/JBAS-7146 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Naming Affects Versions: JBossAS-4.2.3.GA, JBossAS-4.2.2.GA Environment: Linux Fedora8(x386), Fedora8(x86_64) + jdk1.6.0_12 ( JBoss 4.2.2.GA and 4.2.3.GA just as it is unziped). Reporter: Hideo GOTO Assignee: Scott M Stark I am testing migration of an application running on standard Tomcat5/6 to JBoss AS. The application uses <GlobalNamingResources><resouce>definition in the server.xml. While testing, I found out that the getGlobalNamingContext() systematicaly returns NULL, although it is documented in JBoss-web's Java DOC just same as in the Tomcat's one Is it an intended behavior due to JBoss's proper JNDI concern? If yes, any alternative? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira