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/
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
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.
map:match pattern='comment'
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?
map:match pattern='comment'
map:generate src=xml/insert_comment.xml/
map:transform
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
Maybe I am off base here.. But wouldn't his solution be to take his xsp or
whatever that does the database insert and make it into an action?
map:match pattern='comment'
map:act type=insert_comment/
map:generate src=result.xml/
map:transform src=result.xsl
map:parameter
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
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
