Ah ... thanks James.
I didn't realize that rendering a page would invoke onPassivate for the
pages included via *link tags.
I need to look for and watch this happen ... thanks very much.
-Luther
On Tue, Dec 9, 2008 at 1:38 AM, James Hillyerd <[EMAIL PROTECTED]> wrote:
> (I'm still learning t
onPassivate() to return project.getId() ...
> >> which,
> >> is naturally used by ViewProject.Activate(Integer projectId) which
> >> is called
> >> next.
> >>
> >> Does that seem like the right way to do this? I don't nee
--
View this message in context:
http://www.nabble.com/passivate-activate-tp20908072p20914947.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL
on't need to
>> @Persist as
>> the example has done - since with this method, I can cause
>> onPassivate to
>> return what onActivate needs ... and I really don't need to save
>> this info
>> after the request is handled... But, is it safe to assum
Do these links help?
http://localhost:8080/jumpstart/examples/input/forms1
http://localhost:8080/jumpstart/examples/navigation/onactivateandonpassivate/3
http://localhost:8080/jumpstart/examples/navigation/whatiscalledandwhen
Regardng pooling, you should assume the page instance you set up is
(I'm still learning to anyone feel free to correct me!)
Think of it this way: onPassivate() is used to generate links to your a
page. Anytime you to t:pagelink, t:actionlink, or t:form - they all create
an instance of your page (even if you don't specify a context), then call
onPassivate on it.
Question about the flow.
I GET ViewProject.tml with an activation context of "1" which invokes:
ViewProject.onActivate(Integer projectId)
I echo the projectId to the screen as a context for a CreateIssue pagelink.
I visit or GET CreateIssue.tml which invokes:
CreateIssue.onActivate(Intege
