Return-Path: Delivered-To: apmail-xml-cocoon-users-archive@xml.apache.org Received: (qmail 2827 invoked by uid 500); 10 Apr 2002 09:27:30 -0000 Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-users@xml.apache.org Delivered-To: mailing list cocoon-users@xml.apache.org Received: (qmail 2804 invoked from network); 10 Apr 2002 09:27:29 -0000 From: "Carsten Ziegeler" To: Subject: RE: Problem with ParameterSelector Date: Wed, 10 Apr 2002 11:29:52 +0200 Message-ID: MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <000801c1e070$96e53fd0$85966586@Pachelbel> X-Mimeole: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal X-MIMETrack: Itemize by SMTP Server on PBSN1/Systeme und Netzwerke(Release 5.0.8 |June 18, 2001) at 10.04.2002 11:27:40, Serialize by Router on PBSN1/Systeme und Netzwerke(Release 5.0.8 |June 18, 2001) at 10.04.2002 11:27:41, Serialize complete at 10.04.2002 11:27:41 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hi, I'm not sure if I understand you correctly..but let's give it a try. If you use something like this: > > > then you define a parameter for the action itself, this means the act() method of the action gets this parameter. This parameter is not available to any other component. An action can return a Map (key-value-pairs) and this information can be retrieved by all components nested inside the "map:act" tag, so > > > would work, if some of your actions returned a map containing a key "method" with the appropriate value. Please note that it is "{method}" and not "{$method}", the Javadoc is unfortunately wrong. HTH Carsten > -----Original Message----- > From: Volker Schneider [mailto:volker.schneider@danet.de] > Sent: Wednesday, April 10, 2002 11:18 AM > To: cocoon-users@xml.apache.org > Subject: RE: Problem with ParameterSelector > > > Sorry, I mean request attributes... > > -----Original Message----- > From: Volker Schneider [mailto:volker.schneider@danet.de] > Sent: Mittwoch, 10. April 2002 11:16 > To: cocoon-users@xml.apache.org > Subject: RE: Problem with ParameterSelector - ask for a to tag to set > request attributes > > > Meanwhile I've found a workaround for this: > > For setting parameters you can set request attributes within the > action and > use the RequestAttributeSelector for selecting the pipeline. I think it > could be helpful to write a special action which can set an arbitrary > request attribute for this purpose, so that there will be a > mechanism to set > request attributes inside the sitemap. > > By the way, is there a tag like for sitemap parameter > which can > set a request parameter? Is it possible to provide this with the > new cocoon > release? > > Regards, > - Volker - > > -----Original Message----- > From: Volker Schneider [mailto:volker.schneider@danet.de] > Sent: Dienstag, 9. April 2002 14:00 > To: cocoon-users@xml.apache.org > Subject: Problem with ParameterSelector > > > Hi colleagues, > > I have big problems to get the ParameterSelector working. I want to set a > parameter inside an action set and execute different pipelines > dependent on > this value. I looked into the documentation samples and into the > ParameterSelector class itself and took the samples from there. I > spent many > hours to get it working but it will not work :-( > > Please help me, I can't believe that there isn't a way to do that with > cocoon: > > > > > > > > > > > ... > > > > > > > > > > > > > > > > > > > > > > I tried the "parameter-selector-test"-value as {method} and {$method} as > said in the class comment. Both does not work. > > Who can help? > > Best regards > - Volker - > > > > > --------------------------------------------------------------------- > Please check that your question has not already been answered in the > FAQ before posting. > > To unsubscribe, e-mail: > For additional commands, e-mail: > > > --------------------------------------------------------------------- > Please check that your question has not already been answered in the > FAQ before posting. > > To unsubscribe, e-mail: > For additional commands, e-mail: > > > --------------------------------------------------------------------- > Please check that your question has not already been answered in the > FAQ before posting. > > To unsubscribe, e-mail: > For additional commands, e-mail: > --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. To unsubscribe, e-mail: For additional commands, e-mail: