Big +1 ! We can have a small ant-based script that can validate a webapp - find all the XMLs and TLDs and run schema and DTD validation on it.
Another nice thing we could do - if someone has the time - is adding 'Serializable' to Context and all other config objects and saving a snapshot. Then reuse the dependency checking from jasper and check if any of the files changed ( web.xml, jars, tlds ). On the first load or on change we could validate - and for the rest just load the .ser object. But it is not easy - turning validation off by default until we have a way to avoid duplicated validation is a good solution. Costin On Thu, 15 Aug 2002, Jean-francois Arcand wrote: > Hi, > > based on the mailling list feedback, I would like to propose the > following solution for the XML Parser DTD/Schema validation/namespace > aware problems: > > - Add the following attributes in server.xml under the HOST element: > > xmlValidation="false" > xmlNamespaceAware="false" > > and set them equal to false by default. This way, peoples will be able > to turn it on only if they need it, using the AdminTool or directly in > the server.xml file. > > It will still let the door open for: > > - "have a separate validation program that can be run on a webapp _before_ it is >deployed on tomcat" (Costin) > - keeping validation available when required (Steve) > - etc. > > Thanks, > > -- Jeanfrancois > > > > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>