This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 26323 - Fails to read environment entries in web.xml.
Summary: Fails to read environment entries in web.xml.
Status: RESOLVED WONTFIX
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Tomcat (show other bugs)
Version: 3.x
Hardware: Macintosh Mac OS X
: P3 blocker (vote)
Assignee: Milan Kuchtiak
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-08-06 21:02 UTC by fitzgunnar
Modified: 2006-06-05 00:51 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description fitzgunnar 2002-08-06 21:02:31 UTC
I set up en env-entry in web.xml, and wrote a
jsp-page to read the entry. When executing, I got
the response below. When trying the same jsp-page
and web.xml-file on a separate Tomcat-installation
(under Solaris), everything works fine.

   MagnusG!

Starting tomcat. Check logs/tomcat.log for error
messages 
Add env-entry magnus  java.lang.String Gunnarsson
A test value
2002-08-06 09:52:15 - Ctx(  ): Exception in: R(  +
/election.jsp + null) -
javax.servlet.ServletException: Need to specify
class name in environment or system property, or
as an applet parameter, or in an application
resource file:  java.naming.factory.initial
        at
org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:459)
        at
_0002felection_0002ejspelection_jsp_3._jspService(_0002felection_0002ejspelection_jsp_3.java:116)
        at
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:119)
        at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
        at
org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:177)
        at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:318)
        at
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:391)
        at
org.netbeans.modules.web.tomcat.JspServlet.service(JspServlet.java:91)
        at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
        at
org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:404)
        at
org.apache.tomcat.core.Handler.service(Handler.java:286)
        at
org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372)
        at
org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:797)
        at
org.apache.tomcat.core.ContextManager.service(ContextManager.java:743)
        at
org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpConnectionHandler.java:210)
        at
org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416)
        at
org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:498)
        at java.lang.Thread.run(Thread.java:496)
Root cause:
javax.naming.NoInitialContextException: Need to
specify class name in environment or system
property, or as an applet parameter, or in an
application resource file: 
java.naming.factory.initial
        at
javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:643)
        at
javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:246)
        at
javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:283)
        at
javax.naming.InitialContext.lookup(InitialContext.java:350)
        at
_0002felection_0002ejspelection_jsp_3._jspService(_0002felection_0002ejspelection_jsp_3.java:86)
        at
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:119)
        at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
        at
org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:177)
        at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:318)
        at
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:391)
        at
org.netbeans.modules.web.tomcat.JspServlet.service(JspServlet.java:91)
        at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
        at
org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:404)
        at
org.apache.tomcat.core.Handler.service(Handler.java:286)
        at
org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372)
        at
org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:797)
        at
org.apache.tomcat.core.ContextManager.service(ContextManager.java:743)
        at
org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpConnectionHandler.java:210)
        at
org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416)
        at
org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:498)
        at java.lang.Thread.run(Thread.java:496)
Comment 1 _ rkubacki 2002-08-07 14:29:20 UTC
NB.3.3.2 doesn't contain tomcat4.0 plugin by default. Is it really
what you use? If you run tomcat32 that is bundled in NB3.3.x than you
have problem that server.xml is modified (simplyfied) and you have to
add your entries here.

It is very similar with NB3.4 and Tomcat4.0 that is bundled but it is
easier to edit server.xml file or use external instalation of tomcat