Correct me if I'm wrong, but I believe the reason for this is that by the time the generator is executed, the pipeline has already been set up and can't be altered. The docs kind of make a big deal of this in a few places. Part of the reason actions exist is to allow you to make decisions before pipeline setup. Does that help explain Vadim's emphatic answers?
Geoff Howard > -----Original Message----- > From: Vadim Gritsenko [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, July 30, 2002 9:26 PM > To: [EMAIL PROTECTED] > Subject: RE: Can a Generator set a sitemap param? > > > > From: Justin Fagnani-Bell [mailto:[EMAIL PROTECTED]] > > > > Hi List, > > > > Is it possible for a Generator to set sitemap parameters? > > No. > > > I have a > > Generator that's pulling content from a database and > applying a theme, > > the settings for the themes are also stored in the database. The > themes > > are .xsl files and I'd like to be able to set a parameter with the > name > > of the file. > > > > It seems like I could alter the Parameters object passed to setup(). > But > > I'm guessing that either this wouldn't work or would be seriously > > frowned upon... > > Will have no effect. > > > > The reason I don't really want to write an action is that I > don't see > > that it really performs an action. The generator based on > it's queries > > knows which stylesheet to select, I don't really want to perform the > > query twice. > > PS You can do it once, in action. > > Vadim > > > If writing an action is really the proper way to do it, I can be > talked > > into it... > > > > Thanks, > > Justin > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
