Return-Path: Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 65948 invoked from network); 13 Oct 2000 14:03:59 -0000 Received: from rabbit.stu.uea.ac.uk (HELO roger.stu.uea.ac.uk) (139.222.197.41) by locus.apache.org with SMTP; 13 Oct 2000 14:03:59 -0000 Received: from brer ([139.222.197.100] helo=hydrogen) by roger.stu.uea.ac.uk with esmtp (Exim 3.12 #1 (Debian)) id 13k5RE-0005wy-00 for ; Fri, 13 Oct 2000 15:03:56 +0100 Received: from paulr by hydrogen with local (Exim 3.16 #1 (Debian)) id 13k5U4-0001sU-00 for ; Fri, 13 Oct 2000 15:06:52 +0100 Date: Fri, 13 Oct 2000 14:47:03 +0100 From: Paul Russell To: cocoon-dev@xml.apache.org Subject: Re: Move to Xalan2J Message-ID: <20001013144703.C6259@hydrogen.internal.luminas.co.uk> References: <39E696D1.FF670AEA@pwr.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <39E696D1.FF670AEA@pwr.ch>; from Giacomo.Pati@pwr.ch on Fri, Oct 13, 2000 at 07:00:01AM +0200 Organisation: Luminas Ltd. Resent-From: paulr@hydrogen.internal.luminas.co.uk Resent-Date: Fri, 13 Oct 2000 15:06:52 +0100 Resent-To: cocoon-dev@xml.apache.org Resent-Message-Id: Resent-Sender: Paul Russell X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N On Fri, Oct 13, 2000 at 07:00:01AM +0200, Giacomo Pati wrote: > Paul Russell (sorry, I've misspelled your name in the cvs > commits) has implemented a component manager for the general > components (not sitemap components) which respects the new > interfaces from the new avalon release. These interfaces are > used to mark classes as ThreadSafe, SingleThreaded, Poolable > or Recyclable. With this base implementation we are able to > (finally) use the Store to save objects for multiple uses (i.e > pregenerated or compiled stylesheets). Heh. That's okay, I'm used to it. There's also another slight issue. The code I sent you deals with handing out components from pools etc etc, however it doesn't deal with getting them back into the pools afterwards. I'm not entirely sure how to deal with this - I still feel it needs a subinterface to ComponentManager that lets it accept components which people have finished with. I've mentioned this to the Avalon peeps before I think, and not had any joy. Any thoughts? > Further, the component defined in a sitemap are now available > to sub sitemaps (sitemap component inheritance). This means > that you can use sitemap components defined in the parent > sitemap without the need to redeclare them. Funky :) > - Fully integration of the new avalon release. > - Specifying and implemeting the "Content Aggregation" from the RT series > - Going deeper into the "Status and profiling" RT from Paul Russell Happy to contribute on the status and profiling side, obviously. I'll try and look over the new sitemap.xsl asap and post a slightly more involved (and better written ;) e-mail about it... What's left to do on the avalon integration? Paul -- Paul Russell Technical Director, http://www.luminas.co.uk Luminas Ltd.