cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vadim Gritsenko <va...@reverycodes.com>
Subject Re: Redirect to GET, strange bug
Date Mon, 07 Apr 2008 17:29:24 GMT

On Apr 1, 2008, at 5:06 AM, Tobia Conforto wrote:
> AFAIK cocoon.exit() is the recommended way to call  
> FOM_Cocoon.suicide()
>
> It's mentioned here http://cocoon.apache.org/2.1/userdocs/flow/api.html#exit 
>  (while suicide isn't) and its implementation is:
>
> FOM_Cocoon.prototype.exit = function() {
> 	FOM_Cocoon.suicide();
> }

How interesting :)


> In fact, using FOM_Cocoon.suicide() yields the same results as  
> cocoon.exit(), that is, "ProcessingException: Attempted to process  
> incomplete pipeline".
>
> Do you have any idea what's causing this message?
>
> Who is attempting to process which incomplete pipeline?  I'm issuing  
> a global, client-side redirect, and stopping the flow.  Why is  
> Cocoon complaining?

Not quite sure. Most probably your problem is elsewhere, not with this  
javascript. There might be something wrong with how sitemap is  
implemented...


>> Also, it is often a good idea to invalidate the form processing  
>> continuation tree, to free up memory and--even if user manages to  
>> submit the form again--he will receive 404.
>
>
> Interesting.  How do I do this?

Like this:

   var bookmark = form.showForm(path, data);
   ...
   bookmark.invalidate();


Vadim

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org


Mime
View raw message