I don't know what I did the first time, but whatever I did wrong I must not have had enough patience to look at it closer. The request parameters ARE displayed with the request generator after the db action. Thank you again for your help!
--- Samuel Bruce <[EMAIL PROTECTED]> wrote: > Thank you once again. > > Before I created this post to cocoon-users, I tried > using the request generator after the mod-db action > and all of the request parameters were gone (weren't > displayed with xml serializer). Before the mod-db > action they were all there (using the request > generator). That's why I created this thread. > Maybe I did something wrong. I'll try again - work > on > it some more. If I'm successful, I'll let you know. > If > not, I'll send my pipeline and xsl. > > Thanks so much for your assistance and patience with > a > newbie! > > --- Christian Haul > <[EMAIL PROTECTED]> wrote: > > On 03.Mar.2003 -- 06:43 PM, Samuel Bruce wrote: > > > Thanks for responding and sorry for the > ambiguity > > of > > > my post. Your reply was helpful. > > > > > > The parameters that I am referring to are > request > > > parameters sent from a post in an HTML form to a > > > pipeline in my sitemap. That pipeline has a > mod-db > > > action. > > > I'd like to capture one of the input parameters > > from > > > the form to be available as a parameter in an > XSLT > > > > > transformer after that input parameter has been > > used > > > by the mod-db action. > > > Is it possible? My interpretation of your > response > > > along with the behavior that I see is that the > > request > > > parameter is consumed by the mod-db action. > > > > This is absolutely possible! Request parameter are > > read-only and are > > not removed after reading them. BTW none of the > > input modules removes > > a value. Conceptually, they are only for reading > > values, not modifying > > state. Although this is not enforced, all current > > ones obey this > > principle. > > > > You can verify that the parameter is still there > for > > example by using > > the request generator in the same pipeline as you > > have the action. > > > > If you can't make it work, include the pipeline > and > > your xsl file > > (head and template that uses the parameter). > > > > Chris. > > -- > > C h r i s t i a n H a u l > > [EMAIL PROTECTED] > > fingerprint: 99B0 1D9D 7919 644A 4837 7D73 > FEF9 > > 6856 335A 9E08 > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: > > [EMAIL PROTECTED] > > For additional commands, e-mail: > > [EMAIL PROTECTED] > > > > > __________________________________________________ > Do you Yahoo!? > Yahoo! Tax Center - forms, calculators, tips, more > http://taxes.yahoo.com/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > __________________________________________________ Do you Yahoo!? Yahoo! Tax Center - forms, calculators, tips, more http://taxes.yahoo.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
