As it does,
Tapestry will invoke the onPassivate method of that instance, which is like asking
"Hey, instance of the Another page, is there anything you want me to pass to another
instance of your page that will continue your work?".
You can see from the code that the onPassivate method will report the contents
of the message we have just set, and Tapestry will remember its answer. As soon
as it uses another instance of the Another page, it will pass the stored message as a
parameter to the onActivate method of the new instance, and this way we shall be
able to see the message properly displayed on the page.
But how will Tapestry remember the message if it does not create a session? Have a
look at the URL used to display the Another page:
http://localhost:8080/t5first/another/hi+there%21
The message was recorded into the URL while redirecting the user's browser to the
Another page, and so Tapestry was able to restore the message without ever creating
a session. This also means that the Another page can now be bookmarked, and it will
show you the message successfully, even if you come to read it after a few months!
Now imagine that this page was used to display a product from an online catalog,
and you will appreciate the benefits of using the activation context.
Pages:
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98