Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 73391 invoked by uid 500); 2 May 2001 07:51:18 -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 73378 invoked from network); 2 May 2001 07:51:17 -0000 From: "Leo Sutic" To: Subject: RE: [C2] Make the map available to selectors Date: Wed, 2 May 2001 09:51:45 +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) In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-OriginalArrivalTime: 02 May 2001 07:51:28.0937 (UTC) FILETIME=[B21EB990:01C0D2DC] X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N > -----Original Message----- > From: giacomo [mailto:giacomo@apache.org] > Sent: den 1 maj 2001 21:20 > To: Cocoon Developer's List > Subject: Re: [C2] Make the map available to selectors > > > > > On Tue, 1 May 2001, Leo Sutic wrote: > > > All, > > > > I'd like the "map" object in the sitemap to be available to > selectors, thus > > allowing a selector to select depending on sitemap parameters. > > Couldn't you use it like: > > > > > > > ... > > Yes, but I don't see how the selector can get access to the parameters since: - Any tag that is a child of a tag in the sitemap is ignored by the sitemap.xsl stylesheet. - The selector doesn't receieve the "map" object which contains the parameters (only the objectModel and a selector pattern), thus the parameters given in your example would never reach the selector. I don't see how this can be solved either with a "factory" type selector or with a non-factory type, without changing the interface to pass along the "map" object. /LS > > Giacomo > > > > > + The objectModel is just as transient as the sitemap > parameters, and I see > > no difference between selecting depending on one or the other. > > > > + The sitemap parameters are available to all other sitemap components. > > (Generator, transformer, ...) > > > > And the argument against: > > > > - This breaks the current selector interface. > > > > Possible ways: > > > > 1) Include the sitemap parameters in the call to the selector. > > 2) Include the sitemap parameters in the object model. (Makes > little sense, > > as the object model is really the HTTP request object model, and not the > > sitemap object model). > > > > /LS > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org > > For additional commands, email: cocoon-dev-help@xml.apache.org > > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org > For additional commands, email: cocoon-dev-help@xml.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org