Return-Path: Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm Delivered-To: mailing list cocoon-users@xml.apache.org Received: (qmail 27916 invoked from network); 1 Feb 2000 17:15:11 -0000 Received: from pop.systemy.it (194.20.140.28) by 63.211.145.10 with SMTP; 1 Feb 2000 17:15:11 -0000 Received: from apache.org (pv17-pri.systemy.it [194.21.255.17]) by pop.systemy.it (8.8.8/8.8.3) with ESMTP id SAA26420 for ; Tue, 1 Feb 2000 18:15:08 +0100 Message-ID: <3896F3AF.689FD391@apache.org> Date: Tue, 01 Feb 2000 15:54:39 +0100 From: Stefano Mazzocchi Organization: Apache Software Foundation X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,it MIME-Version: 1.0 To: cocoon-users@xml.apache.org Subject: Re: redirect References: <9d7b9aa04c1b52abd59c3deadf94707838967637@> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Eric SCHAEFFER wrote: > > Youps, very strange. > Note on Cocoon functionment : > > Request => Producer : XML document => Processors (loop) => Formatters (loop) > => Response > > The way your XML document is created shouldn't change the problem... > > I suppose you use Cocoon 1.6.1, Xerces 1.1, Xalan 0.19.2 ... > Have you 'register' the redirect processor in cocoon.properties ? (add the > line processor.type.redirect=class) > Note: my redirect processor belong to the > 'org.apache.cocoon.processor.redirect' package. It can (and should) be > changed, otherwise, you should place it in the jar file... > > But you can do redirect also in XSP. > Just write an XSP page like this : > > > > > language="java" > xmlns:xsp="http://www.apache.org/1999/XSP/Core" > > > > > response.sendRedirect("/test.xml"); > document = null; > return; > > > ??? response.sendRedirect("/test.xml"); the above should be enough. (if not, it's a bug) > My processor is not really a good solution, because it parses the document > to found a redirect pi. If you don't have one, it consums time for nothing. > XSP is better (pages are transformed in java classes, compiled and then > executed to produce the XML document). > > And if you want to create dynamic pages, DCP is dying... Have a look at XSP. > Really cool. You can create tag libraries, and then there's no XSP code in > any XML file. Yes, Eric is right. I suggest all of you to forget about DCP since it will be deprecated in future releases (starting from 1.7 probably). -- Stefano Mazzocchi One must still have chaos in oneself to be able to give birth to a dancing star. Friedrich Nietzsche -------------------------------------------------------------------- Come to the first official Apache Software Foundation Conference! ------------------------- http://ApacheCon.Com ---------------------