Re: redirect at the end of a pipeline/match
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 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 handles your select statement. or 2) have your pipeline aggregate two pipelines. One pipeline would be your insert, the other your select. In the final result, your xsl would ignore the output of the insert pipeline. The first has the advantage that you can react to the result of the sql transform and display different content. I tend to dislike the sql transformer for this kind of problem and prefer actions - the modular database actions are very powerful. Perhaps someone that uses the sql transformer for inserts could provide a more elegant solution. HTH, Geoff - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: redirect at the end of a pipeline/match
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 handles your select statement. or 2) have your pipeline aggregate two pipelines. One pipeline would be your insert, the other your select. In the final result, your xsl would ignore the output of the insert pipeline. The first has the advantage that you can react to the result of the sql transform and display different content. I tend to dislike the sql transformer for this kind of problem and prefer actions - the modular database actions are very powerful. Perhaps someone that uses the sql transformer for inserts could provide a more elegant solution. HTH, Geoff At 02:11 PM 6/4/2003, you wrote: 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: redirect at the end of a pipeline/match
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? 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? > > > > > > > > > > -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]
RE: redirect at the end of a pipeline/match
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. cheers, neil. -Original Message- 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 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 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:redirect doesn't work because it skips the generate and transform. >Browsing through the mail archive someone suggest's using a meta redirect >tag in generated html. >(http://marc.theaimsgroup.com/?l=xml-cocoon-users&m=105464887116737&w=2 ) > >This would work but it seems clunky.. There must be a cleaner way to >accomplish this.? > >-Daniel - 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]
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? -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]
Re: redirect at the end of a pipeline/match
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. > > > > > value="myconnection"/> > > > > > > map:redirect doesn't work because it skips the > generate and transform. > Browsing through the mail archive someone suggest's > using a meta > redirect tag in generated html. > (http://marc.theaimsgroup.com/?l=xml-cocoon-users&m=105464887116737&w=2) > > This would work but it seems clunky.. There must be > a cleaner way to > accomplish this.? > > -Daniel > > > > > - > 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]
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? Geoff 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:redirect doesn't work because it skips the generate and transform. Browsing through the mail archive someone suggest's using a meta redirect tag in generated html. (http://marc.theaimsgroup.com/?l=xml-cocoon-users&m=105464887116737&w=2) This would work but it seems clunky.. There must be a cleaner way to accomplish this.? -Daniel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
