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 name="some_identifier" value="who_knows"/> </map:transform> <map:serialze/> </map:act> <map:generate src="failed.xml"/> <map:serialze/> </map:match> If you dont want to view the serialization.. why serialize it? ----- Original Message ----- 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 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 type="sql"> > <map:parameter name="use-connection" value="myconnection"/> > <map:transform> > <REDIRECT or something here/> > </map:match> > > -Daniel > > Geoff Howard wrote: > > > 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? > > > > Geoff > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]