Return-Path: Delivered-To: apmail-xml-cocoon-users-archive@xml.apache.org Received: (qmail 10681 invoked by uid 500); 15 Nov 2001 08:55:59 -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 10670 invoked from network); 15 Nov 2001 08:55:58 -0000 Reply-To: From: "Luca Morandini" To: "Cocoon-users" Subject: RE: Cocoon: Few steps in sitemap? Date: Thu, 15 Nov 2001 09:56:29 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Importance: Normal X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Viktor, the example reads a row from the dbms (select-resource-db.xml) and presents it as a read-only (say, display-resource.html) or editable (edit-resource.html) HTML. Of course, only the second is invoked from the browser, the first one being an "internal" pipeline. Apart from this, my idea was just to show you that pipelines may be chained, hence avoiding the need for storing intemediate files. Best regards, --------------------------------------------- Luca Morandini GIS Consultant lmorandini@ieee.org http://utenti.tripod.it/lmorandini/index.html --------------------------------------------- > > > -----Original Message----- > > From: Skladov, Victor [mailto:Skladov@his.de] > > Sent: Thursday, November 15, 2001 9:42 AM > > To: cocoon-users@xml.apache.org; lmorandini@ieee.org > > Subject: AW: Cocoon: Few steps in sitemap? > > > > > > Hello Luca! > > > > Thank you for your reply! > > Could you please describe in few words what this example does? > > > > Regards, > > Viktor > > > > -----Urspr�ngliche Nachricht----- > > Von: Luca Morandini [mailto:l.moran@tin.it] > > Gesendet: Donnerstag, 15. November 2001 09:26 > > An: cocoon-users@xml.apache.org > > Betreff: RE: Cocoon: Few steps in sitemap? > > > > > > Viktor, > > > > I think this example may fit the first of your questions: > > > > > > > > > src="docs/all-parameters.xml"/> > > > > > > > value="noria-dev"/> > > > > > > > > > > > > > > > > > > > > > > src="stylesheets/resource-{1}-html.xsl"/> > > > > > > > > > > As you may notice the second (the one actually being > > invoked > > from the browser), calls the first one using > src="cocoon:/select-resource-db.xml"/> . > > > > The first may be called from another > > used to > > deliver PDF instead of HTML, hence avoiding the need for the storage of > > intermediate files. > > > > I use this for more complicated pipelines than the usual > > XML->XSL->HTML > > stuff. > > > > I hope this helps, > > > > --------------------------------------------- > > Luca Morandini > > GIS Consultant > > lmorandini@ieee.org > > http://utenti.tripod.it/lmorandini/index.html > > --------------------------------------------- > > > > > > > -----Original Message----- > > > From: Skladov, Victor [mailto:Skladov@his.de] > > > Sent: Thursday, November 15, 2001 9:08 AM > > > To: cocoon-users@xml.apache.org > > > Subject: Cocoon: Few steps in sitemap? > > > > > > > > > Hello! > > > > > > I am writing to you all once more, because I can't find a solution up > > > to now. > > > Does anybody know how can I tell Cocoon2 to execute not one step > > > (XSP+XSL->and output in a format that Cocoon accept, for example > > HTML), > > > but a few steps: > > > 1)generate from XSP with XSL a further file, say, TEX (it doesn't > > > matter!) > > > 2) generate from that file (TEX in our case) a further format, for > > > example PDF? > > > > > > OR: > > > Can Cocoon2 save output file? Can I force Cocoon execute my LINUX > > script > > > that lies on the server? > > > > > > I would be very grateful for any ideas! > > > > > > Regards, > > > Viktor > > > > > > --------------------------------------------------------------------- > > > 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: