Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 97911 invoked from network); 14 Aug 2002 19:59:47 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 14 Aug 2002 19:59:47 -0000 Received: (qmail 11373 invoked by uid 97); 14 Aug 2002 19:59:48 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@jakarta.apache.org Received: (qmail 11216 invoked by uid 97); 14 Aug 2002 19:59:47 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Developers List" Reply-To: "Tomcat Developers List" Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 11144 invoked by uid 98); 14 Aug 2002 19:59:45 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) X-Authentication-Warning: costinm.sfo.covalent.net: costin owned process doing -bs Date: Wed, 14 Aug 2002 12:55:41 -0700 (PDT) From: costinm@covalent.net X-X-Sender: costin@costinm.sfo.covalent.net To: Tomcat Developers List Subject: Re: [5][PATCH]Run Watchdog from the jakarta-tomcat-5 build.xml In-Reply-To: <3D5AB2C1.2030900@sun.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Wed, 14 Aug 2002, Jean-francois Arcand wrote: > The problem should occurs only with Xerces 2.0.2. Is 2.0.2 bundle with > ANT 1.5? If you try with the current Xerces nightly build, it should > work. This is a big paint because Xerces 2.0.2 seems to be used > everywhere....The only solution will be to set the schema validation > off, or detect the Xerces version and throw an exception before starting > parsing a file. Turn schema validation off, and leave it off. Tomcat5 working with a single parser is not good. And while you're doing that, turn also DTD validation off and leave it off unless a user wants to enable it explicitely. Validation should be done by a deploy tool or build tool ( offline ). Or by tomcat if a mechanism to avoid duplicated validation is provided. Costin > > -- Jeanfrancois > > > > > > > In any case, after doing that, Catalina service starts up, but doesn't > > seem to be able to find the servlet apis to compile JSP pages. As an > > added irritation, stdout isn't redirected to catalina.out, and it is > > quite noisy. > > > > So, my current patch may not be the best possible, but it does have > > the advantage of working. > > > > I think it will make more sense to use the launcher as the basis for a > > task to run tomcat. Running it in process leads to a lot of state > > leaking over. For testing I think it's safer to run it as much as > > possible in its own environment. > > > > This is what I was using for the tomcat5 task: > > > location="${java.home}/../lib/tools.jar" /> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > classname="org.apache.catalina.startup.CatalinaService" > > classpathref="tomcatcp" /> > > > home="${tomcat.build}" > > base="${basedir}/tmp/tomcat" > > wait="false"/> > > > > > > costinm@covalent.net wrote: > > > >> On Wed, 14 Aug 2002, Steve Downey wrote: > >> > >>> This patch starts up a copy of tomcat with the watchdog war files, > >>> runs watchdog against it, and shuts down tomcat afterwards. It uses > >>> the Launcher to run tomcat in the background, and puts the webapps, > >>> work, logs and conf directories in a tmp dir so as not to muck up > >>> the build. > >>> > >>> The only part I really don't like is that there isn't a good way to > >>> know that tomcat is up and running, so for now there's a sleep > >>> between launching tomcat and starting the watchdog tests. > >>> > >> > >> For tomcat5 ? Well, it is - if you use the task ( take a look at > >> build2.xml ). The task will start tomcat inprocess, and will return > >> after all the startup is done ( and continue with the next task ). > >> > >> ( unless you have wait="true" ) > >> > >> Costin > >> > >> > >> > >> > >> -- > >> To unsubscribe, e-mail: > >> > >> For additional commands, e-mail: > >> > >> > >> > > > > > > > > > > -- > > To unsubscribe, e-mail: > > > > For additional commands, e-mail: > > > > > > > -- > To unsubscribe, e-mail: > For additional commands, e-mail: > > -- To unsubscribe, e-mail: For additional commands, e-mail: