Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 74761 invoked by uid 500); 1 May 2001 08:44:33 -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 74741 invoked from network); 1 May 2001 08:44:31 -0000 From: "Leo Sutic" To: Subject: RE: [C2] Allowing actions to select transformer type Date: Tue, 1 May 2001 10:44:55 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 In-Reply-To: X-OriginalArrivalTime: 01 May 2001 08:44:43.0046 (UTC) FILETIME=[F78B5460:01C0D21A] X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N All, if Sylvain is correct, and there are caching issues associated with this, the change could potentially break Cocoon. (I believe he's right - if the pipelines change depending on their content, caching may be difficult. But I haven't really thought this through.) After reading the posts by Giacomo and Sylvain, I'm -1 on substitution in type attributes as well. However, if I modify my suggestion to the 3rd possible patch I described in my original email: > > 2) Create a new selector that tests on sitemap parameters. As I will only have to choose between 2 or max 3 different transformers (all of which are known in advance), this will solve my problem. Would this merge better with Cocoon? I figure it'd be something like: ... ... ... /LS --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org