cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Oliver <res1c...@verizon.net>
Subject Re: Call continuations from flow instead of sitemap
Date Sat, 03 Apr 2004 21:58:51 GMT
These ContinuationsManager API should _not_ be used in a flowscript. Use 
the sitemap to invoke your continuation, please.

Is it possible to solve your problem by using a helper function to send 
the page:

function sendPageAndWait(uri, biz, ttl) {
  cocoon.response.setHeader( "Expires", "-1" );
  cocoon.response.setHeader( "Cache-Control", "no-cache" );
  cocoon.response.setHeader( "Pragma", "no-cache" );
  return cocoon.sendPageAndWait(uri, biz, ttl);
}

Or perhaps Reinhard's intercepted flowscript could help here...

 
Chris



Leszek Gawron wrote:

>On Thu, Apr 01, 2004 at 02:39:05PM -0500, Vadim Gritsenko wrote:
>  
>
>>Leszek Gawron wrote:
>>
>>    
>>
>>>I have this snipped in one of my .js files :
>>>
>>>
>>>      
>>>
>>...
>>
>>    
>>
>>>function runContinuation( action ) {
>>>
>>>
>>>      
>>>
>>Provided that "action" contains continuation ID and not actual 
>>continuation object... you need to lookupWebContinuation from the 
>>ContinuationsManager component, this will give you WebContinuation 
>>object. Once you have it... Something like this should be able to invoke it:
>>
>>   var wk = contManager.lookupWebContinuation(action);
>>   var c = wk.getContinuation();
>>   c(c);
>>    
>>
> You have to do c(); Otherwise you get some errors about uninitialized
>FOM_Request. This also does not work if you have page local variables. I have
>filed a bugzilla report at
>http://issues.apache.org/bugzilla/show_bug.cgi?id=28179
>
>	lg
>  
>


Mime
View raw message