I just read the tail end of the conversation, but I wanted to add something.
I try to use onActivate to capture parameters from the url, and maybe do minimal translation/validation of those inputs. But I do the actual work within the setupRender. That way it doesn't matter how many onActivates get called and what order, they are only there to translate url parmaters into page variables which then drive setupRender ( with proper if not nulls, etc ).
This might simplify your mental model of how the code is split up and is supposed to work.
You would have to put some thought though if you use a form on a page, since the setupRender is not called on form submit.. If you look at the different events that the form lifecycle provides, you'll see that you just have to refactor your setupRender logic into a third method that is called from setupRender and an approriate onEvent from the form ( onPrepareForForm, or onPrepareSubmitForForm, something like that ).
maxthesecond wrote:
Glad to know there is consensus about it ,I'll check the RequestFilter and let the onActivate for the page tasks (reloading objects.....) Thanks
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
