cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Neil Palmer" <>
Subject RE: redirect at the end of a pipeline/match
Date Wed, 04 Jun 2003 18:25:19 GMT
I'm looking to do the same thing - I'm using Cocoon purely for it's 
XML generation/transformation capabilities, while my actual application
is using JBoss/Jetty & Struts.

Basically I have an admin app that allows you to marshall a business 
object via Castor, perform various transformations on it and then 
serialize the result to an XML file.  This XML file will then get 
pushed out to production for use on the front end customer facing app.
However, I'd love to be able to redirect back to the admin home page 
after the xml serializaton.  I'm not actually using Cocoon for any
content presentation.

I've only been using Cocoon (2.0.4) for a couple of months, so if
there's a better way of doing this, I'm all ears.  While the redirect
after the serialization isn't critical, it'd certainly be nice.


-----Original Message-----
From: Geoff Howard [] 
Sent: Wednesday, June 04, 2003 2:05 PM
Subject: Re: redirect at the end of a pipeline/match

What would the purpose be of sending xml back as a result and then
redirecting the client?  This "need" keeps coming up when using the
transformers with side effects, of which the sql transformer is one.

Again, why do you need to redirect?  Why not serve them the content
you want them to have right away?


At 01:46 PM 6/4/2003, you wrote:
>I'm looking for a clean way to 'redirect' a user back to a page, at the

>end of a pipeline.
><map:match pattern='comment'>
>    <map:generate src="xml/insert_comment.xml"/>
>    <map:transform type="sql">
>        <map:parameter name="use-connection" value="myconnection"/>
>    <map:transform>
>    <map:serialize type="xml"/>
>    <REDIRECT or something here/>
>map:redirect doesn't work because it skips the generate and transform. 
>Browsing through the mail archive someone suggest's using a meta
>tag in generated html. 
>This would work but it seems clunky.. There must be a cleaner way to 
>accomplish this.?

To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message