I created an edit block - and wired up a GenericSelectModel. All is well and fine.
I populate that select model with a query from the database - so now, I'd like to move that query from getModel or getEncoder to a lifecycle method. I took a look and found this page on COMPONENT rendering: http://tapestry.apache.org/tapestry5/guide/rendering.html and I tried the literal method void setupRender but it never gets invoked. I also tried @SetupRender but still, no invocation when I visit the page. I dug around a bit more and found the PAGE lifecycle docs: http://tapestry.apache.org/tapestry5/guide/lifecycle. At the bottom of the page appear three methods and I implemented void pageAttached() and it worked! So here are my questions. Does an edit block act like a page and not a component? And, am I missing something or is a PAGE lifecycle signficantly different than a COMPONENT lifecycle? I had read and made the assumptions that PAGEs were actually COMPONENTs themselves and because they are special maybe I could see a PAGE having *additional* lifecycle methods - but I wasn't ready for none of the COMPONENT lifecycle methods to trip. Am I missing something or am I safe in saying that PAGEs generally have 3 lifecycle hooks and only well-defined COMPONENTS have the setupRender ... etc *render* cycle events. Thanks, -Luther
