Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 82812 invoked by uid 500); 10 Jan 2003 15:33:40 -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 82786 invoked from network); 10 Jan 2003 15:33:40 -0000 Message-ID: <53482.64.214.127.50.1042212818.squirrel@netarcana.com> Date: Fri, 10 Jan 2003 10:33:38 -0500 (EST) Subject: Re: RequestDispatcher with Cocoon From: "Andy Lewis" To: In-Reply-To: <3E1EE735.8010205@anyware-tech.com> References: <20030109125419.GC3915@expresso.localdomain> <20030110141544.GB1677@bremen.dvs1.informatik.tu-darmstadt.de> <39740.64.214.127.50.1042208676.squirrel@netarcana.com> <43163.64.214.127.50.1042209027.squirrel@netarcana.com> <3E1EDDE5.8010402@verizon.net> <3E1EE735.8010205@anyware-tech.com> X-Priority: 3 Importance: Normal X-MSMail-Priority: Normal Cc: Reply-To: ajl@ascii27.net X-Mailer: SquirrelMail (version 1.2.6) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N If I actually get it working, I would certinaly contribute it. Yeah, ugly, but probalby no really CLEAN way to achieve it. At any rate, many thanks for the guidance - I'll go with a reader. I suspected that using the wrong componenet would cause me grief.... > Vadim Gritsenko wrote: > >> Andy Lewis wrote: >> >>> I have a need to, under specific circumstances, do a >>> RequestDispatcher.forward out of Cocoon. I've >>> not found any support for this in Cocoon. Alternatives won't work since I need to do this >>> while >>> preserving request attributes. I would expect to be able to code this as an Action without >>> extreme >>> difficulty, but I thought I would thorw the idea to the list first and see if anyone has any >>> ideas, comments, or suggestions...(something other than "No! Don't do it!" :) >>> Many thanks.... >>> >> >> Why do I think that reader is much better place for something like this (...assuming that >> it's possible...)? > > > Because forwarding delegates the production of the output to the target resource. But Cocoon > expects the sitemap to produce something or an error is displayed. > > So the only place where such forwarding is possible is in a Cocoon component that feeds the > output with abitrary binary data, and Cocoon names it a reader ;-) > > Andy, would you like to contribute a "ForwardReader", how ugly and servlet-tied as it may be ? > > Sylvain > > -- > Sylvain Wallez Anyware Technologies > http://www.apache.org/~sylvain http://www.anyware-tech.com { XML, Java, Cocoon, > OpenSource }*{ Training, Consulting, Projects } > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: > cocoon-dev-unsubscribe@xml.apache.org > For additional commands, email: cocoon-dev-help@xml.apache.org -- "The heights of genius are only measurable by the depths of stupidity." --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org