>>While converting some applications from 3.3.1 to 4.1.12 I noticed >>some little problems. > > > Wot? 3.3.1 isn't good enough for you any more. ;-)
You're kidding, I'm preparing the future, which may be TC 5 for us if we could avoid JDK 1.4 to be mandatory. And I'd like to do some internals benchmarks ;) > Without testing, in theory you can put your jar in common/lib, and change > the classname for "default" in conf/web.xml and the only bugs will be yours. > :) Note, that this is more than you can do with 3.3.1. > > >>2) We also used to include external entities in web.xml which live >> outside webapp dir : >> >> ie : >> >><?xml version="1.0" encoding="ISO-8859-1"?> >><!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application >>2.2//EN" >> "http://java.sun.com/j2ee/dtds/web-app_2.2.dtd"; > > [ > >><!ENTITY % settings SYSTEM "../../../settings.xml"> %settings; >>]> >> >>... >> >>Digester find settings.xml only when it's located in WEB-INF or >>webapp directories (ie ROOT/WEB-INF/settings.xml or ROOT/settings.xml). >> >>How could I make it find the settings.xml outside webapps area ? >>via conf/catalina.policy ? >> > > > This has always been a headache for me on all Tomcat versions. However, I > don't think that internal-entities can be used at all (usefully). When you need to set some properties outside webapps, ie system settings used by web applications, you need it. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
