<html>
<body>
At 21:50 15/04/2010, you wrote:<br>
<blockquote type=cite class=cite cite="">What are the exact steps that I
need to follow to reproduce <br>
a fresh Pier image and WAFlowConvenienceFunctionalTest?</blockquote><br>
Hi Lukas, all,<br><br>
I started looking at this and had some observations that I'd like to
share with you hereafter.<br>
I did the followings:<br>
1) Picked
<a href="http://www.seaside.st/distributions/Seaside-3.0a5.app.zip" eudora="autourl">
http://www.seaside.st/distributions/Seaside-3.0a5.app.zip<br>
</a>2) Loaded from
<a href="http://source.lukas-renggli.ch/pier2addons" eudora="autourl">
http://source.lukas-renggli.ch/pier2addons</a><br>
<x-tab> </x-tab>-
Pier-Blog-lr.138<br>
<x-tab> </x-tab>-
Pier-Setup-lr.83<br>
3) Executed *PRDistribution new register*<br>
4) Modified *aCommand execute* in *PRContentsWidget >>
onAnswerCommand:* as follows:<br>
<x-tab> </x-tab>[(aCommand
isKindOf: PRAddCommand)<br>
<x-tab> </x-tab><x-tab>
</x-tab>ifTrue:
[<x-tab> </x-tab>self call:
WAFlowConvenienceFunctionalTest new.<br>
<x-tab> </x-tab><x-tab>
</x-tab><x-tab>
</x-tab><x-tab>
</x-tab>self context
command answer: self context]<br>
<x-tab> </x-tab><x-tab>
</x-tab>ifFalse:
[aCommand execute] ]<br>
<x-tab> </x-tab><x-tab>
</x-tab><x-tab>
</x-tab>on: Error<br>
<x-tab> </x-tab><x-tab>
</x-tab><x-tab>
</x-tab>do: [ :err | ^
self component errors add: err ].<br><br>
5) Pointed my browser to
<a href="http://localhost:8080/pier/" eudora="autourl">
http://localhost:8080/pier/</a><br>
6) Logged-in as admin/pier<br>
7) Pressed the *Add* link in the Commands toolbar (to add a child to
/).<br>
8) Pressed the *Add* button in the dialog.<br><br>
At this point, Seaside / Pier render *What's your favorite Cheese?*
etc., which is what I was expecting. The Component of PRContentsWidget,
which is an MAContainerComponent, delegates its rendering to the
WAFlowConvenienceFunctionalTest instance, due to the #call:.<br><br>
Now, I followed visiting pages:<br>
9) Pressed the *About* link. The default content is displayed.
<br>
10) Pressed to "Home* link. Then, WAFlowConvenienceFunctionalTest
displays instead of the default content.<br>
11) Refreshed the *Home* page using my browser (Chrome),
WAFlowConvenienceFunctionalTest keeps displaying instead of the default
content.<br><br>
Since I didn't use the back button in (10) & (11), I would personally
expect to see the default content. Otherwise, how the user could get ride
of that component, without executing it until it *answers*, or creating a
new session? Does that make sense? <br><br>
Technically speaking, shouldn't those Delegations be released once the
page is refreshed (at least in the case of Pier as a CMS)?<br><br>
BTW, this relates to the 3rd point in my previous email on this topic,
copied below, although not exactly the same: <br>
<x-tab> </x-tab><i>3) The
user clicks on an item in the main menu (on the top), selected
arbitrarily (the behavior that follows does not depend on the menu item
selected). At this point, Seaside/Pier activate the component that was
#call:'ed at the begging of the execution of the flow model in step (2),
and was supposed to be activated during that stage (in place of that
error message). This activated component is actually the first in that
Sushi Store checkout process, namely *Fill cart*. Once launched in
this way, then the execution flows smoothly to the end.<br><br>
</i>It looks like the Delegation has been created, in spite of the
*GRPharoPlatform >> seasideCallbackMarker* error message reported
in the 2nd point of that email. I've some intuitions about the cause of
this error. I'll share it in a post that will follow.<br><br>
Regards,<br>
Reza<br>
<br><br>
</body>
</html>