tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steve Downey <steve.dow...@netfolio.com>
Subject Re: [5][PATCH]Run Watchdog from the jakarta-tomcat-5 build.xml
Date Wed, 14 Aug 2002 22:50:32 GMT
costinm@covalent.net wrote:

><SNIP/>
>
>
>Well, CatalinaService is not 'completed' - just started :-)
>
>What we do in 3.3 is have 2 setters, and at execute check if:
>- if only one is set, the other takes this value
>- if none is set, use discovery ( locate the base from the CLASSPATH )
>- if both are set, use that.
>
>If you want to implement this - great, if not I'll do it when I find 
>time ( or I need it ).
>
See attached patch. I added a method setHomeAndBase() and a couple of 
booleans to see if they were set via setters.

>
>>The next problem was that the task runs in VM. Ant's xercesImpl chokes 
>>on parsing the schemas. This is the known dependency on Xerces 2.0.1. 
>>Replacing the xercesImpl.jar in Ant fixed that, but that seems an ugly 
>>requirement.
>>
>
>Well... As I said, it is a major problem if we can't use any JAXP but 
>require a specific parser and version...
>
>One solution is to remove schema validation ( and validation in general )
>from tomcat runtime, and have a separate validation program that
>can be run on a webapp _before_ it is deployed on tomcat. 
>
>There are many other solutions - but requiring anyone using tomcat5
>to use Xerces2.0.1 and subjecting every user to hugely expensive
>and redundant validation is the worse.
>
With any luck, by the time Tomcat5 is released, XML parsers with good 
schema support will be more common, so it won't be such an issue. It is 
unfortunate that the current release of Xerces is broken.

Removing validation from the servlet container reference implementation 
somehow seems, well, wrong. I agree that doing validation at deployment 
is reasonable, rather than for each startup. Something like what the jsp 
compiler does.

>
><SNIP>
>
<java fork="false"> will run it in process, which gives problems with 
the shared environment. In particular I get:
     [java] INFO: Digester for server.xml created 587
     [java] java.lang.LinkageError: loader constraints violated when 
linking org/xml/sax/XMLReader class

<java fork="true"> will run it out of process, but the next task won't 
execute until tomcat finishes. Not good either.

I think the right answer is either Launcher, which uses [daemon] to 
start a background process, or Cactus, which introduces another 
dependency, and may still have some issues with the ant environment 
leaking through.

>
>
>Regarding output redirection, I think Patrick mentioned adding some
>methods in the startup code to redirect programmatically.
>
>Costin
>
>
>--
>To unsubscribe, e-mail:   <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
>For additional commands, e-mail: <mailto:tomcat-dev-help@jakarta.apache.org>
>
>



Mime
View raw message