Re: Allowing redirects in handle-errors
On Apr 22, 2004, at 12:30 AM, leo leonid wrote: and what about calling a function map:when test=invalid-continuation map:call function=restart ... /map:call /map:when or a saved continuation ? duh :) that works perfectly. thanks! -pete
Re: Allowing redirects in handle-errors
On 20.04.2004, at 18:28, peter royal wrote: On Apr 20, 2004, at 12:22 PM, Tony Collen wrote: If a URL with an invalid continuation ID is invoked, I would like to take the user to the start of the process rather than displaying an error page. AFAIK, this needs a redirect-to in the handle-errors block. I can think of several ways of working around this block, but I was curious as to what others do in this situation, and if might warrant a revote on the change :) -pete Hmm. Could generate a page that has a manual redirect, e.g.: meta http-equiv=refresh content=0;url:http://foo/ ? yea, that's one of the ways of working around it, but seems hacky :) i could also create a custom Action since that gets a handle to a Redirector. -pete and what about calling a function map:when test=invalid-continuation map:call function=restart ... /map:call /map:when or a saved continuation ? /leo
Allowing redirects in handle-errors
Yes, resurfacing a topic from last year, http://marc.theaimsgroup.com/?l=xml-cocoon-devm=105231353428562w=2 .. a change I voted -1 on at the time, no less! He's my current situation, and afaik, a redirect in handle-errors is what I need, but I may be wrong. For a particular segment of my application, I am storing the continuation ID for flow as a request parameter in the URL. If a URL with an invalid continuation ID is invoked, I would like to take the user to the start of the process rather than displaying an error page. AFAIK, this needs a redirect-to in the handle-errors block. I can think of several ways of working around this block, but I was curious as to what others do in this situation, and if might warrant a revote on the change :) -pete
Re: Allowing redirects in handle-errors
peter royal wrote: Yes, resurfacing a topic from last year, http://marc.theaimsgroup.com/?l=xml-cocoon-devm=105231353428562w=2 .. a change I voted -1 on at the time, no less! He's my current situation, and afaik, a redirect in handle-errors is what I need, but I may be wrong. For a particular segment of my application, I am storing the continuation ID for flow as a request parameter in the URL. If a URL with an invalid continuation ID is invoked, I would like to take the user to the start of the process rather than displaying an error page. AFAIK, this needs a redirect-to in the handle-errors block. I can think of several ways of working around this block, but I was curious as to what others do in this situation, and if might warrant a revote on the change :) -pete Hmm. Could generate a page that has a manual redirect, e.g.: meta http-equiv=refresh content=0;url:http://foo/ ? Tony
Re: Allowing redirects in handle-errors
On Apr 20, 2004, at 12:22 PM, Tony Collen wrote: If a URL with an invalid continuation ID is invoked, I would like to take the user to the start of the process rather than displaying an error page. AFAIK, this needs a redirect-to in the handle-errors block. I can think of several ways of working around this block, but I was curious as to what others do in this situation, and if might warrant a revote on the change :) -pete Hmm. Could generate a page that has a manual redirect, e.g.: meta http-equiv=refresh content=0;url:http://foo/ ? yea, that's one of the ways of working around it, but seems hacky :) i could also create a custom Action since that gets a handle to a Redirector. -pete
Re: Allowing redirects in handle-errors
peter royal wrote: i could also create a custom Action since that gets a handle to a Redirector. How about a redirecting seriliazer (possibly if certain conditions are met in the SAX stream, e.g. xpath predicate)? andy -- [EMAIL PROTECTED] / [EMAIL PROTECTED] Absinthe makes the hog Jane Fonda
