cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Lundquist ...@wrinkledog.com>
Subject Re: Sitemap problem... help! :-)
Date Sun, 30 Jan 2005 20:27:18 GMT

On Jan 30, 2005, at 3:07 AM, Leszek Gawron wrote:

>>>
> You should have errors in your log files when getting this kind of 
> InvalidContinuationException:
>
>>         if (!kont.interpreterMatches(interpreterId)) {
>>             getLogger().error(
>>                     "WK: Continuation (" + kont.getId()
>>                             + ") lookup for wrong interpreter. Bound 
>> to: "
>>                             + kont.getInterpreterId() + ", looked up 
>> for: "
>>                             + interpreterId);
>>             return null;
>>         }
>

Yep... too bad I'm using 2.1.6 :-)

>
> What you request is not a trivial change. Currently it is the 
> interpreter that is resolved first (based on current sitemap context). 
> Then it is interpreter's responsibility to lookup and resume a proper 
> continuation. I do not know if it is possible to invert the behaviour:
> - first the continuations gets looked up
> - the sitemap context is changed based on the interpreter info stored 
> in continuation (the id is not enough as it is a resource path that 
> would have to get parsed every time)
> - the flow interpreter bound to sitemap is being invoked with ready to 
> go WebContinuation.

That's just what I had in mind! :-)
—mark


Mime
View raw message