Uploaded image for project: 'Application Server 3 4 5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-7146

org.apache.catalina.core.StandardServer of the JBoss-web.deployer systematicaly returns NULL against getGlobalNamingContext() call.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Major Major
    • No Release
    • JBossAS-4.2.2.GA, JBossAS-4.2.3.GA
    • Naming
    • None
    • Compatibility/Configuration

      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?

              starksm64 Scott Stark (Inactive)
              eisgotoh Hideo GOTO (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: