Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: <044c01c3c58e$edaa1340$273965c1@ifb.interfacebusiness.de>
From: "Frank Taffelt" <frank.taffelt@interface-business.de>
To: <dev@cocoon.apache.org>
References: <03e701c3c4bb$d8f21ca0$273965c1@ifb.interfacebusiness.de>
 <3FE087E8.3070002@upaya.co.uk>
Subject: Re: Permanently redirect from flow
Date: Thu, 18 Dec 2003 18:46:55 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

> I have no problem with this. Can you suggest how you would do it? Have
> you looked into the code to see how it could be implemented?

the connection between flow and cocoon is
\src\java\org\apache\cocoon\components\flow\javascript\fom\FOM_Cocoon.java:

/************* original snippet ********************/
public void jsFunction_redirectTo(String uri) throws Exception {
 // Cannot use environment directly as TreeProcessor uses own version of
redirector
 // environment.redirect(false, uri);
 PipelinesNode.getRedirector(environment).redirect(false, uri);
}


adding a new function add permanent to the flow layer

/************* new code ***********************
public void jsFunction_redirectTo(boolean permant, String uri)
  throws Exception {
  if (permant)
    PipelinesNode.getRedirector(environment).globalRedirect(false, uri);
  else
    // the old way
   jsFunction_redirectTo(uri);
 }

this enhancement should not break any existing code.

the usage from flow would be:

// the old style redirect as ever -> HTTP 302
cocoon.redirectTo('abc');

// using the new redirect routine -> HTTP 301
cocoon.redirectTo(true,'abc');


Frank