Thanks, Thiago.
I think I understand the logic/strategy: "If there's a context value
passed, it is the id of an object to be edited. If not, we're going to
create a new object". In the above code, just changing @Persist("entity")
to @PageActivationContext seems to achieve that....
Is that all? I guess my question was WHAT ELSE needs to be done to get this
production ready? Howard's quote seems to suggest something "smart" needed
within the onActivate method. I suppose the only thing needed in onActivate
is this.person = person; (???)
void onActivate(Person person)
{
this.person = person; // is this the only "smart" thing needed in
onActivate?
}
Is that all, or is there something else?
By now, I am almost convinced the answer is: YES, that is all that is
needed...(but just wanted to make absolutely sure about this, so I don't end
up with something flaky just because I did not do the intended "smart" thing
within onActivate()...;-)
Thanks again...and, please bear with me as I learn to adjust to "Code less,
deliver more"...
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Reuse-Edit-Create-tp5643323p5645453.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
