Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
From: bugzilla@apache.org
To: dev@cocoon.apache.org
Subject: DO NOT REPLY [Bug 36322]  -
    Continuation, sendPage and Rhino 1.6r1
Message-Id: <20050831092456.69488E1@ajax.apache.org>
Date: Wed, 31 Aug 2005 11:24:56 +0200 (CEST)

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=36322>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=36322


------- Additional Comments From sylvain@apache.org  2005-08-31 11:24 -------
Weird... After some debugging, it looks like JS contexts get mixed up somewhere
in Rhino, as the "cocoon" object which is used as the continuation call scope in
handleContinuation() is not the same as the one on which the
jsGet_continuation() call is done.

The use case here is that a <map:call function> sends a page whose processing
calls itself a <map:call continuation>. We have nested flowscript calls.

I don't have time to investigate further ATM, but a workaround is to change the
POST URL to "form" so that we don't have nested flowscript calls when calling
continuations.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.