Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 5426 invoked by uid 500); 9 Feb 2002 13:40:49 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 5414 invoked from network); 9 Feb 2002 13:40:49 -0000 Message-ID: <3C6523F5.6CCD11E3@apache.org> Date: Sat, 09 Feb 2002 14:28:21 +0100 From: Stefano Mazzocchi X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: cocoon-dev@xml.apache.org Subject: Re: [C2.0.1] Precompiled XSP's and Sitemap's for WAR deployment. References: <20020208192535.99714.qmail@web12807.mail.yahoo.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Davanum Srinivas wrote: > > Team, > > Please try the new "-Dbuild.precompile=true" option in the build script. It will generate Java > Source(s) for all XSP's and Sitemap's in WEB-INF/classes and even compiles them. These > pre-generated files will be then be added to cocoon.war. > > The feature is mainly targeted at production Servlet Engines that accept WAR files. The assumption > is that all the "dynamic" stuff like updating sitemap's, xsp's on the fly and regenerating > .java/.class from *.XSP and *.XMAP are not really needed one the development cycle is over. Uh, cool. Which reminds me of an idea I had a while back: we could create a 'deploy my stuff for production' build process that could also *precompile* the XML files using my SAX-compilation thing. That would have two major side effects: 1) performance: parsing a compiledXML file is somewhat 8/10 times faster than using a non-validating parser (tried with both xerces and crimson, careful: your mileage may vary) 2) unmodificability: these XML files become binary and you can't modify them in production even if you wanted to. I think this is a good thing since if people change things on production and then a new build is deployed on top, the changes are gone. Sure, the above is bad practice but would you bet it will happen? making those 'production XML' binaries, we might save lots of pain, don't you think? -- Stefano Mazzocchi One must still have chaos in oneself to be able to give birth to a dancing star. Friedrich Nietzsche -------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org