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] - Different way of handling top level flowscript variables
Date Mon, 24 May 2004 10:22:26 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





------- Additional Comments From ouzo@wlkp.org  2004-05-24 10:22 -------
The thing you have to do is to copy the directory provided to cocoon webapp's 
root directory (I assyme you already did that).

Now you issue:

http://localhost:8080/variable-test/page1.do

You will see the "login screen" first, then the page1 itself. 
The page1 contains links to another pages: to page2 and wizard page.

When you click on "page2" link in cocoon HEAD 2004-04-03 you get page2 content. 
In cocoon >= 2004-04-23 you get the login screen again, which means that the 
user variable has been nullified.

If you click "wizard" link you get the login screen same as described above but 
as you navigate through the wizard (so travel the same continuation tree) you 
do not get the login screen redisplayed (means user variable is not null).

Mime
View raw message