cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 29152] New: - Different way of handling top level flowscript variables
Date Sat, 22 May 2004 15:31:38 GMT
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=29152>.
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=29152

Different way of handling top level flowscript variables

           Summary: Different way of handling top level flowscript variables
           Product: Cocoon 2
           Version: Current CVS 2.1
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Flowscript
        AssignedTo: dev@cocoon.apache.org
        ReportedBy: ouzo@wlkp.org


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.

Mime
View raw message