Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Cannot Reproduce
-
2.1.8
-
None
-
None
-
Operating System: other
Platform: Other
-
29152
Description
Initially I have described the problem here: http://marc.theaimsgroup.com/?
t=108473104700002&r=1&w=2
Now I have prepared a little test case I will attach and it looks like there is
a different visibility of top level flowscript variables:
- In cocoon HEAD 2004-04-03 if you set a top level flowscript variable in one
continuation chain, starting another chain does not make it disappear. The
value is still there.
- I tested the same test case with cocoon HEAD 2004-04-23 and later. Here the
top level variable is only visible in the same continuation chain. If you
request to call another function, the top level variable is null. Because of
this you cannot use top level variables to store some current user context - it
will not last too long. You have to use session.
It may not be a bug but an explicit change. I filed this report because I
hadn't not get any response on cocoon-dev that this is intentional.
Test case follows.
t=108473104700002&r=1&w=2
Now I have prepared a little test case I will attach and it looks like there is
a different visibility of top level flowscript variables:
- In cocoon HEAD 2004-04-03 if you set a top level flowscript variable in one
continuation chain, starting another chain does not make it disappear. The
value is still there.
- I tested the same test case with cocoon HEAD 2004-04-23 and later. Here the
top level variable is only visible in the same continuation chain. If you
request to call another function, the top level variable is null. Because of
this you cannot use top level variables to store some current user context - it
will not last too long. You have to use session.
It may not be a bug but an explicit change. I filed this report because I
hadn't not get any response on cocoon-dev that this is intentional.
Test case follows.