Remy Maucherat wrote: >> I agree that using ant replace is a hack - the right solution would be to >> read the XML with DOM, insert the elements in the right place, and save >> back ( DOM - so we don't loose comments ). Or even read it as a file, and >> use regexp. No problem if we save the original web.xml in the process. > > I see modifying the original web.xml as a problem.
Not sure what you mean by "original" web.xml. From the point of view of tomcat, the "original" is the modified web.xml which includes declarations for all jsps. What you mean by "original" - i.e. the incomplete web.xml that relied on tomcat-specific JspServlet to function - is a development artifact. > If you don't want the explicit extra XML file, I would instead create a > new extra deployment descriptor in the work directory during the deploy > procedure. That way, the feature is hidden, but you can't deploy the > compiled webapp to another server without modifying the deployment > descritptor yourself. > An additional note: I think the order of elements is irrelevant with the > new spec, so that simplifies things. It is not in the old spec - and it is a good practice to maintain backward compatibility, i.e. people will probably develop apps that run in 2.3 and 2.4 containers for a while. Not to mention that the order is irrelevant only in the 2.4 web.xml which also uses schema. I plan to stick with the 2.3 descriptor for a while, xml schema is one of the worst technologies that I know. Costin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
