I am not dead set against anything.. although I think flow is ruled out
because this project is running on 2.0.4. I will probably implement some
actions, they seem to be the cleanest way to accomplish this. Thanks
very much for your help!
-Daniel
Geoff Howard wrote:
If you are dead set agains
If you are dead set against using actions or flow, then I'd recommend
continuing your pipeline with the select data you want. Probably the
best way to do this is
1) after the first sql transform, insert an xsl transform that replaces the
results of the insert with a cinclude of a pipeline that han
From: "Daniel McOrmond" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, June 04, 2003 10:11 AM
Subject: Re: redirect at the end of a pipeline/match
> Drop the xml serialization. I don't want to send that back as a result.
> What I do want to do is di
ssage-
From: Geoff Howard [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 04, 2003 2:05 PM
To: [EMAIL PROTECTED]
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
Drop the xml serialization. I don't want to send that back as a result.
What I do want to do is display a page that now includes the new
information which came from this database insert. Does this make sense?
-Daniel
Geoff Howard wrote:
What would the purpose be of sending
Looks like flowmap would be the cleanest way of
handling this, but it's still in development and not
that well documented.
--- Daniel McOrmond <[EMAIL PROTECTED]> wrote:
> I'm looking for a clean way to 'redirect' a user
> back to a page, at the
> end of a pipeline.
>
>
>
>
>
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
