Re: Tomcat 3.2 - Default web.xml not being read

2000-12-14 Thread Barbara Nelson
web.xml is no longer used/supported in 3.2. The main reason - the code that merged the "default" web.xml with the application web.xml was very bad, slow and hard to maintain. It was commented out until someone wants to fix it. A second reason - probably more important from a user

Re: Tomcat 3.2 - Default web.xml not being read

2000-12-14 Thread cmanolache
Given that the default web.xml is not being read, how do you enable Jikes as the JspCompiler? That setting used to be in web.xml. What's the syntax to specify it in server.xml, or did we lose this functionality for Tomcat 3.2? (If so, could it be put back, or define a syntax in server.xml

Re: Tomcat 3.2 - Default web.xml not being read

2000-12-14 Thread cmanolache
Given that the default web.xml is not being read, how do you enable Jikes as the JspCompiler? That setting used to be in web.xml. What's the syntax to specify it in server.xml, or did we lose this functionality for Tomcat 3.2? (If so, could it be put back, or define a syntax in

Re: Tomcat 3.2 - Default web.xml not being read

2000-12-14 Thread Bojan Smojver
I just compiler the attached file into a class, put the class into the webserver.jar (to avoid changing CLASSPATH for testing) and modified server.xml file with: ContextInterceptor className="tc3.JasperOptions" sendErrToClient="false" keepgenerated="false" / after the WebXmlReader

RE: Tomcat 3.2 - Default web.xml not being read

2000-12-14 Thread Barbara Nelson
Thank you for the fast turnaround :-) I'll try it out. Barbara. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 14, 2000 1:44 PM To: '[EMAIL PROTECTED]' Cc: '[EMAIL PROTECTED] org' Subject: Re: Tomcat 3.2 - Default web.xml not being read