Tomcat's default web.xml
Hi there Can anyone point to a place where I can see the basic layout of the Tomcat web.xml. The located at TOMCAT_HOME/conf/web.xml Kind Regards Schalk Neethling Web Developer.Designer.Programmer.President Volume4.Development.Multimedia.Branding emotionalize.conceptualize.visualize.realize Tel: +27125468436 Fax: +27125468436 email:[EMAIL PROTECTED] web: www.volume4.com This message contains information that is considered to be sensitive or confidential and may not be forwarded or disclosed to any other party without the permission of the sender. If you received this message in error, please notify me immediately so that I can correct and delete the original email. Thank you.
RE: Tomcat's default web.xml
The reason I ask this is, I am very comfortable with the web.xml structure and use it on a daily basis but, I am currently developing a site for a client hosted by a third party and there seems to be a problem with processing JSP's. When you click on a link to a JSP page, it start to load in the status bar but the page never shows up. I have even left it to try and load it for more that an hour with no success. Therefore I am trying to see whether their web.xml is set-up correctly to process JSP's. Kind Regards Schalk Neethling Web Developer.Designer.Programmer.President Volume4.Development.Multimedia.Branding emotionalize.conceptualize.visualize.realize Tel: +27125468436 Fax: +27125468436 email:[EMAIL PROTECTED] web: www.volume4.com This message contains information that is considered to be sensitive or confidential and may not be forwarded or disclosed to any other party without the permission of the sender. If you received this message in error, please notify me immediately so that I can correct and delete the original email. Thank you. :: -Original Message- :: From: Schalk [mailto:[EMAIL PROTECTED] :: Sent: Tuesday, March 23, 2004 9:02 PM :: To: [EMAIL PROTECTED] :: Subject: Tomcat's default web.xml :: Importance: High :: :: Hi there :: :: :: :: Can anyone point to a place where I can see the basic layout of the Tomcat :: web.xml. The located at TOMCAT_HOME/conf/web.xml :: :: :: :: Kind Regards :: :: Schalk Neethling :: :: Web Developer.Designer.Programmer.President :: :: Volume4.Development.Multimedia.Branding :: :: emotionalize.conceptualize.visualize.realize :: :: Tel: +27125468436 :: :: Fax: +27125468436 :: :: email:[EMAIL PROTECTED] :: :: web: www.volume4.com :: :: :: :: This message contains information that is considered to be sensitive or :: confidential and may not be forwarded or disclosed to any other party :: without the permission of the sender. If you received this message in error, :: please notify me immediately so that I can correct and delete the original :: email. Thank you. :: :: - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Is there a way to make a default web.xml?
No, not with Tomcat. -Original Message- From: Brandon Cruz [mailto:[EMAIL PROTECTED]] Sent: Friday, August 24, 2001 7:17 AM To: [EMAIL PROTECTED] Subject: Is there a way to make a default web.xml? Is there a way to make a default web.xml file that will work across all contexts/virtual hosts? Brandon
RE: Is there a way to make a default web.xml? --Tomcat 3.x
Sorry, forgot to mention tomcat version 3.x -Original Message- From: Brandon Cruz [mailto:[EMAIL PROTECTED]] Sent: Friday, August 24, 2001 9:17 AM To: [EMAIL PROTECTED] Subject: Is there a way to make a default web.xml? Is there a way to make a default web.xml file that will work across all contexts/virtual hosts? Brandon
Re: Is there a way to make a default web.xml? --Tomcat 3.x
Someone correct me if I'm wrong plz =) but I believe the web.xml in $TOMCAT_HOME/conf is applied to all web apps. I think I read on the dev list (from Larry) that this feature was removed in 3.x to increase app portability === that relying on a default web.xml reduces the portability of an application. However, this behavior is indeed present in TC4. - r On Fri, 24 Aug 2001 09:22:32 -0500 [EMAIL PROTECTED] wrote: Sorry, forgot to mention tomcat version 3.x -Original Message- From: Brandon Cruz [mailto:[EMAIL PROTECTED]] Sent: Friday, August 24, 2001 9:17 AM To: [EMAIL PROTECTED] Subject: Is there a way to make a default web.xml? Is there a way to make a default web.xml file that will work across all contexts/virtual hosts? Brandon
Re: Is there a way to make a default web.xml? --Tomcat 3.x
Hi Rob, 3.2.x still has web.xml in $TOMCAT_HOME/conf. I haven't tried 3.3 yet. Thanks, --jeff - Original Message - From: Rob S. [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, August 24, 2001 7:42 AM Subject: Re: Is there a way to make a default web.xml? --Tomcat 3.x Someone correct me if I'm wrong plz =) but I believe the web.xml in $TOMCAT_HOME/conf is applied to all web apps. I think I read on the dev list (from Larry) that this feature was removed in 3.x to increase app portability === that relying on a default web.xml reduces the portability of an application. However, this behavior is indeed present in TC4. - r On Fri, 24 Aug 2001 09:22:32 -0500 [EMAIL PROTECTED] wrote: Sorry, forgot to mention tomcat version 3.x -Original Message- From: Brandon Cruz [mailto:[EMAIL PROTECTED]] Sent: Friday, August 24, 2001 9:17 AM To: [EMAIL PROTECTED] Subject: Is there a way to make a default web.xml? Is there a way to make a default web.xml file that will work across all contexts/virtual hosts? Brandon
RE: Is there a way to make a default web.xml? --Tomcat 3.x
The $TOMCAT_HOME/conf/web.xml is still there (for example purposes?) but it isn't read. To avoid confusion, this file has been removed in Tomcat 3.3. Larry -Original Message- From: Jeff Kilbride [mailto:[EMAIL PROTECTED]] Sent: Friday, August 24, 2001 3:38 PM To: [EMAIL PROTECTED] Subject: Re: Is there a way to make a default web.xml? --Tomcat 3.x Hi Rob, 3.2.x still has web.xml in $TOMCAT_HOME/conf. I haven't tried 3.3 yet. Thanks, --jeff - Original Message - From: Rob S. [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, August 24, 2001 7:42 AM Subject: Re: Is there a way to make a default web.xml? --Tomcat 3.x Someone correct me if I'm wrong plz =) but I believe the web.xml in $TOMCAT_HOME/conf is applied to all web apps. I think I read on the dev list (from Larry) that this feature was removed in 3.x to increase app portability === that relying on a default web.xml reduces the portability of an application. However, this behavior is indeed present in TC4. - r On Fri, 24 Aug 2001 09:22:32 -0500 [EMAIL PROTECTED] wrote: Sorry, forgot to mention tomcat version 3.x -Original Message- From: Brandon Cruz [mailto:[EMAIL PROTECTED]] Sent: Friday, August 24, 2001 9:17 AM To: [EMAIL PROTECTED] Subject: Is there a way to make a default web.xml? Is there a way to make a default web.xml file that will work across all contexts/virtual hosts? Brandon
RE: Is there a way to make a default web.xml? --Tomcat 3.x
I don't think it is read in 3.2.1 either. So does that pretty much mean that we have to make an additional web.xml file and web application for every virtual host? All I really want to do is supress directory listings. Is there another way to do this...maybe on the apache side? Brandon -Original Message- From: Larry Isaacs [mailto:[EMAIL PROTECTED]] Sent: Friday, August 24, 2001 3:04 PM To: '[EMAIL PROTECTED]' Subject: RE: Is there a way to make a default web.xml? --Tomcat 3.x The $TOMCAT_HOME/conf/web.xml is still there (for example purposes?) but it isn't read. To avoid confusion, this file has been removed in Tomcat 3.3. Larry -Original Message- From: Jeff Kilbride [mailto:[EMAIL PROTECTED]] Sent: Friday, August 24, 2001 3:38 PM To: [EMAIL PROTECTED] Subject: Re: Is there a way to make a default web.xml? --Tomcat 3.x Hi Rob, 3.2.x still has web.xml in $TOMCAT_HOME/conf. I haven't tried 3.3 yet. Thanks, --jeff - Original Message - From: Rob S. [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, August 24, 2001 7:42 AM Subject: Re: Is there a way to make a default web.xml? --Tomcat 3.x Someone correct me if I'm wrong plz =) but I believe the web.xml in $TOMCAT_HOME/conf is applied to all web apps. I think I read on the dev list (from Larry) that this feature was removed in 3.x to increase app portability === that relying on a default web.xml reduces the portability of an application. However, this behavior is indeed present in TC4. - r On Fri, 24 Aug 2001 09:22:32 -0500 [EMAIL PROTECTED] wrote: Sorry, forgot to mention tomcat version 3.x -Original Message- From: Brandon Cruz [mailto:[EMAIL PROTECTED]] Sent: Friday, August 24, 2001 9:17 AM To: [EMAIL PROTECTED] Subject: Is there a way to make a default web.xml? Is there a way to make a default web.xml file that will work across all contexts/virtual hosts? Brandon
Problem changing default web.xml : conf/web.xml is not processed
Hi there, I have a problem changing the web.xml in the conf dir (conf/web.xml). I wanted to configure some central stuff there and wondered why it isn't working. Then I placed a wrong tag with no closing tag into the web.xml. The sax-parser must throw an exception with this file. But nothing happened. I tested the same wrong tag in an webapps web.xml file. There I got the exception. My conclusion is now, that the default web.xml is not proccessed! I wonder why, because the server.xml file is in the same directory. If server.xml is found by tomcat, why not the default web.xml. I can post a log-trace if you are intereseted, but I don't see any informative help in it. Be method opening the default web.xml does not log anything. Any comments, how I can make tomcat reading and processing the default web.xml are welcome. Kind regards Guido --- This message is intended for the adressee or its representative only. Any form of unauthorized use, publication, reproduction, copying or disclosure of the content of this e-mail is not permitted. If you are not the intended recipient of this e-mail message and its contents, please notify the sender immediately and delete this message and all its attachments subsequently.
RE: Problem changing default web.xml : conf/web.xml is not processed
You didn't mention which version of Tomcat you were running. The thing is, in some version, conf/web.xml became a SAMPLE, not a DEFAULT. You should not count on conf/web.xml to be used because that doesn't follow the J2EE standard. You MUST make a copy of the web.xml and put it into each webapp context's WEB-INF directory. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Friday, July 06, 2001 12:34 AM To: [EMAIL PROTECTED] Subject: Problem changing default web.xml : conf/web.xml is not processed Hi there, I have a problem changing the web.xml in the conf dir (conf/web.xml). I wanted to configure some central stuff there and wondered why it isn't working. Then I placed a wrong tag with no closing tag into the web.xml. The sax-parser must throw an exception with this file. But nothing happened. I tested the same wrong tag in an webapps web.xml file. There I got the exception. My conclusion is now, that the default web.xml is not proccessed! I wonder why, because the server.xml file is in the same directory. If server.xml is found by tomcat, why not the default web.xml. I can post a log-trace if you are intereseted, but I don't see any informative help in it. Be method opening the default web.xml does not log anything. Any comments, how I can make tomcat reading and processing the default web.xml are welcome. Kind regards Guido --- This message is intended for the adressee or its representative only. Any form of unauthorized use, publication, reproduction, copying or disclosure of the content of this e-mail is not permitted. If you are not the intended recipient of this e-mail message and its contents, please notify the sender immediately and delete this message and all its attachments subsequently.
Re: Default web.xml
we also found this to be the case when setting up mime types. I think it's a 'feature' - if you create a new context, only the local web.xml has any effect. Rob pretty - Original Message - From: Timothy Shadel [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, June 15, 2001 8:07 PM Subject: Default web.xml I have a quick question about how the default web.xml found in the conf directory is supposed to act. The Tomcat User's guide says it acts as a default web.xml for all web applications. I tried to add the following to it: servlet-mapping !-- This was there by default -- servlet-name jsp /servlet-name url-pattern *.jsp /url-pattern /servlet-mapping servlet-mapping !-- I added this -- servlet-name jsp /servlet-name url-pattern *.tem /url-pattern /servlet-mapping because we wanted to logically separate our JSP files used as templates from those providing major content. However, accessing a valid JSP file that's been renamed with a .tem extension returns only the actual file contents instead of being translated as a JSP. The same servlet-mapping tag works perfectly in an application's web.xml. Am I supposed to be able to modify the web.xml in the conf directory and have it affect all applications, or is it only supposed to work with the one that comes with Tomcat by default? Thanks, Tim Shadel
Re: Default web.xml
In tomcat 3.2.x, the web.xml in the conf directory is not used at all. I fact, you can completely remove it with no ill effects. Internally, Tomcat 3.2.x compiles in some defaults; mime mappings, the JSP servlet mapping, etc. In your application's web.xml specify anything that you need too override the defaults. I believe I read the Tomcat 4.0 will once again have a default web.xml. I'm not sure about Tomcat 3.3, however. Check the Tomcat mailing list archives for more info - Original Message - From: Timothy Shadel [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, June 15, 2001 3:07 PM Subject: Default web.xml I have a quick question about how the default web.xml found in the conf directory is supposed to act. The Tomcat User's guide says it acts as a default web.xml for all web applications. I tried to add the following to it: servlet-mapping !-- This was there by default -- servlet-name jsp /servlet-name url-pattern *.jsp /url-pattern /servlet-mapping servlet-mapping !-- I added this -- servlet-name jsp /servlet-name url-pattern *.tem /url-pattern /servlet-mapping because we wanted to logically separate our JSP files used as templates from those providing major content. However, accessing a valid JSP file that's been renamed with a .tem extension returns only the actual file contents instead of being translated as a JSP. The same servlet-mapping tag works perfectly in an application's web.xml. Am I supposed to be able to modify the web.xml in the conf directory and have it affect all applications, or is it only supposed to work with the one that comes with Tomcat by default? Thanks, Tim Shadel
Default web.xml
I have a quick question about how the default web.xml found in the conf directory is supposed to act. The Tomcat User's guide says it acts as a default web.xml for all web applications. I tried to add the following to it: servlet-mapping !-- This was there by default -- servlet-name jsp /servlet-name url-pattern *.jsp /url-pattern /servlet-mapping servlet-mapping !-- I added this -- servlet-name jsp /servlet-name url-pattern *.tem /url-pattern /servlet-mapping because we wanted to logically separate our JSP files used as templates from those providing major content. However, accessing a valid JSP file that's been renamed with a .tem extension returns only the actual file contents instead of being translated as a JSP. The same servlet-mapping tag works perfectly in an application's web.xml. Am I supposed to be able to modify the web.xml in the conf directory and have it affect all applications, or is it only supposed to work with the one that comes with Tomcat by default? Thanks, Tim Shadel
RE: Default web.xml
What version of tomcat are you running? --- Michael Wentzel Software Developer Software As We Think - http://www.aswethink.com
RE: Default web.xml
After much difficulty I did manage to get Tomcat3.2.2 to run servlets jsp, but only with JDK1.3.1 not JDK1.3.0_02 I suspect an incompatibility problem -Original Message- From: Michael Wentzel [mailto:[EMAIL PROTECTED]] Sent: Friday, June 15, 2001 3:05 PM To: '[EMAIL PROTECTED]' Subject: RE: Default web.xml What version of tomcat are you running? --- Michael Wentzel Software Developer Software As We Think - http://www.aswethink.com
Re: Default web.xml
What is the error message you are getting? - Original Message - From: cathy moffatt [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, June 15, 2001 4:09 PM Subject: RE: Default web.xml After much difficulty I did manage to get Tomcat3.2.2 to run servlets jsp, but only with JDK1.3.1 not JDK1.3.0_02 I suspect an incompatibility problem -Original Message- From: Michael Wentzel [mailto:[EMAIL PROTECTED]] Sent: Friday, June 15, 2001 3:05 PM To: '[EMAIL PROTECTED]' Subject: RE: Default web.xml What version of tomcat are you running? --- Michael Wentzel Software Developer Software As We Think - http://www.aswethink.com
Re: Default web.xml
I get this with both Tomcat 3.2.1 and 3.2.2. I'm using JDK 1.2.2. No error message appears. I just get the full text of the JSP file as if it were a text file (i.e. NO preprocessing at all) when I access /basic/login.tem Here are excerpts from the stderr.log (I've got Tomcat setup as a 2000 service on my development machine). The log shows two contexts: 1) /basic where no special JSP setup has been made, but the changes to the DEFAULT web.xml have been made. 2) /teacherapplication where the exact same servlet-mapping tag in the default web.xml was also placed in the APPLICATION's web.xml. Log excerpt # 1) 2001-06-15 12:57:21 - ContextManager: SimpleMapper1: SM: extension map /basic/*.jsp Ct (jsp(org.apache.jasper.servlet.JspServlet/null) ) Log excerpt # 2) 2001-06-15 12:57:21 - ContextManager: SimpleMapper1: SM: extension map /teacherapplication/*.jsp Ct (jsp(org.apache.jasper.servlet.JspServlet/null) ) 2001-06-15 12:57:21 - ContextManager: SimpleMapper1: SM: extension map /teacherapplication/*.tem Ct (jsp(org.apache.jasper.servlet.JspServlet/null) ) The log seems to show that there isn't an extension mapping being created for all contexts - just the one where I explicitly told it to in the APPLICATION web.xml. That's why I'm wondering if Tomcat is *supposed* to create the extension mapping based on the default web.xml, or if it's only supposed to use the DEFAULT provided with Tomcat without changes (i.e. is this a bug or a feature). Thanks, Tim Shadel Luba Powell [EMAIL PROTECTED] 06/15/01 02:06PM What is the error message you are getting? - Original Message - From: cathy moffatt [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, June 15, 2001 4:09 PM Subject: RE: Default web.xml After much difficulty I did manage to get Tomcat3.2.2 to run servlets jsp, but only with JDK1.3.1 not JDK1.3.0_02 I suspect an incompatibility problem -Original Message- From: Michael Wentzel [mailto:[EMAIL PROTECTED]] Sent: Friday, June 15, 2001 3:05 PM To: '[EMAIL PROTECTED]' Subject: RE: Default web.xml What version of tomcat are you running? --- Michael Wentzel Software Developer Software As We Think - http://www.aswethink.com Timothy Shadel I have a quick question about how the default web.xml found in the conf directory is supposed to act. The Tomcat User's guide says it acts as a default web.xml for all web applications. I tried to add the following to it: servlet-mapping !-- This was there by default -- servlet-name jsp /servlet-name url-pattern *.jsp /url-pattern /servlet-mapping servlet-mapping !-- I added this -- servlet-name jsp /servlet-name url-pattern *.tem /url-pattern /servlet-mapping because we wanted to logically separate our JSP files used as templates from those providing major content. However, accessing a valid JSP file that's been renamed with a .tem extension returns only the actual file contents instead of being translated as a JSP. The same servlet-mapping tag works perfectly in an application's web.xml. Am I supposed to be able to modify the web.xml in the conf directory and have it affect all applications, or is it only supposed to work with the one that comes with Tomcat by default? Thanks, Tim Shadel
Re: Tomcat 3.2 - Default web.xml not being read
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 perspective - is that it direct user to un-portable web applications. If you want your application to be portable ( i.e. to be able to take it and deploy it on a different container ) you need to have all the mappings, etc in your application web.xml file. As long as you use the "default" web.xml your application can't be portable. In addition, there was no rule about the interaction between setting in the application web.xml and the server web.xml - it just happen based on hacks in the code. A third reason is the fact that tomcat already has a configuration file - server.xml, and it's confusing to use 2 different styles, and server.xml has far more options on setting the server. To add another argument here, one idea in tomcat is that the server shouldn't depend on any particular cofiguration file format - it should be possible to embed tomcat in an application using JNDI or windows registry for configuration, and tomcat shouldn't require any special configuration file. Web.xml was a big obstacle for this. ( if you look at EmbededTomcat, it is possible to start tomcat without any configuration file at all, using only API calls. If we would use web.xml then this will become much harder or impossible ) Costin 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 for it?). Thanks, Barbara Nelson.
Re: Tomcat 3.2 - Default web.xml not being read
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 for it?). I'll try to write a small interceptor that sets the compiler and other options for jasper ( probably next week it'll be ready ). ( that will not require a new release of tomcat - you just install the interceptor in the classpath and add it to tomcat.jar ). I think Larry is also working on something - he sent a proposal few days ago about how to enable debugging ( and pass options to jasper ). It'll probably be part of a 3.2.x bug-fix release, as it requires some changes in the existing code. As a workaround you can use the web.xml in your web application. Costin
Re: Tomcat 3.2 - Default web.xml not being read
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 for it?).
I'll try to write a small interceptor that sets the compiler and other
options for jasper ( probably next week it'll be ready ). ( that will not
require a new release of tomcat - you just install the interceptor in the
classpath and add it to tomcat.jar ).
Ok, I don't think it'll be ready next week - you can use it today, it took
10 minutes to write and test :-)
You can set all the options that jasper knows - compile the interceptor (
you need tomcat jars in CLASSPATH ), add it to CLASSPATH, and then
add in your server.xml ( after WebXmlReader ):
ContextInterceptor
className="tc3.JasperOptions"
keepGenerated="true"
jspCompilerPlugin="org.apache.jasper.compiler.JikesJavaCompiler"
/
( run javadoc and read all other options you can set ).
It should work with any tomcat 3.2 - in 3.3 there is already one
( JspInterceptor ) that does a much better integration ( and is faster
than the servlet used in 3.2 ).
Costin
/*
*
*
* The Apache Software License, Version 1.1
*
* Copyright (c) 1999 The Apache Software Foundation. All rights
* reserved.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
*
* 1. Redistributions of source code must retain the above copyright
*notice, this list of conditions and the following disclaimer.
*
* 2. Redistributions in binary form must reproduce the above copyright
*notice, this list of conditions and the following disclaimer in
*the documentation and/or other materials provided with the
*distribution.
*
* 3. The end-user documentation included with the redistribution, if
*any, must include the following acknowlegement:
* "This product includes software developed by the
*Apache Software Foundation (http://www.apache.org/)."
*Alternately, this acknowlegement may appear in the software itself,
*if and wherever such third-party acknowlegements normally appear.
*
* 4. The names "The Jakarta Project", "Tomcat", and "Apache Software
*Foundation" must not be used to endorse or promote products derived
*from this software without prior written permission. For written
*permission, please contact [EMAIL PROTECTED]
*
* 5. Products derived from this software may not be called "Apache"
*nor may "Apache" appear in their names without prior written
*permission of the Apache Group.
*
* THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED
* WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
* OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
* DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR
* ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
* SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
* LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
* USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
* ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
* OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
* OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
* SUCH DAMAGE.
*
*
* This software consists of voluntary contributions made by many
* individuals on behalf of the Apache Software Foundation. For more
* information on the Apache Software Foundation, please see
* http://www.apache.org/.
*
* [Additional notices, if required by prior licensing conditions]
*
*/
package tc3;
import org.apache.tomcat.core.*;
import org.apache.tomcat.core.Constants;
import org.apache.tomcat.util.*;
import java.io.*;
import java.net.*;
import java.util.*;
/**
* To set Jasper options. Needs to be installed just after WebXmlReader.
*
*
* Supports all of the existing options in EmbededServletOptions.
*
* @author [EMAIL PROTECTED]
*/
public class JasperOptions extends BaseInterceptor {
public JasperOptions() {
}
Hashtable args=new Hashtable();
/**
* Are we keeping generated code around?
*/
public void setKeepGenerated( String s ) {
args.put( "keepgenerated", s );
}
/**
* Are we supporting large files?
*/
public void setLargeFile( String s ) {
args.put( &quo
Re: Tomcat 3.2 - Default web.xml not being read
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 section and restarted Tomcat and Apache. The errors are still going to the browser and generated java files are still there. I was hoping this file would fix the problem I had with init parameters but it doesn't. I must be doing something really silly... Any ideas? Bojan [EMAIL PROTECTED] wrote: 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 for it?). I'll try to write a small interceptor that sets the compiler and other options for jasper ( probably next week it'll be ready ). ( that will not require a new release of tomcat - you just install the interceptor in the classpath and add it to tomcat.jar ). Ok, I don't think it'll be ready next week - you can use it today, it took 10 minutes to write and test :-) You can set all the options that jasper knows - compile the interceptor ( you need tomcat jars in CLASSPATH ), add it to CLASSPATH, and then add in your server.xml ( after WebXmlReader ): ContextInterceptor className="tc3.JasperOptions" keepGenerated="true" jspCompilerPlugin="org.apache.jasper.compiler.JikesJavaCompiler" / ( run javadoc and read all other options you can set ). It should work with any tomcat 3.2 - in 3.3 there is already one ( JspInterceptor ) that does a much better integration ( and is faster than the servlet used in 3.2 ). Costin Name: JasperOptions.java JasperOptions.javaType: Plain Text (TEXT/PLAIN) Encoding: BASE64
RE: Tomcat 3.2 - Default web.xml not being read
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 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 for it?). I'll try to write a small interceptor that sets the compiler and other options for jasper ( probably next week it'll be ready ). ( that will not require a new release of tomcat - you just install the interceptor in the classpath and add it to tomcat.jar ). Ok, I don't think it'll be ready next week - you can use it today, it took 10 minutes to write and test :-) You can set all the options that jasper knows - compile the interceptor ( you need tomcat jars in CLASSPATH ), add it to CLASSPATH, and then add in your server.xml ( after WebXmlReader ): ContextInterceptor className="tc3.JasperOptions" keepGenerated="true" jspCompilerPlugin="org.apache.jasper.compiler.JikesJavaCompiler" / ( run javadoc and read all other options you can set ). It should work with any tomcat 3.2 - in 3.3 there is already one ( JspInterceptor ) that does a much better integration ( and is faster than the servlet used in 3.2 ). Costin
