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
onActivat
Glad to know there is consensus about it ,I'll check the RequestFilter and
let the onActivate for the page tasks (reloading objects.)
Thanks
--
View this message in context:
http://www.nabble.com/T5-onActivate-tp17673637p17710792.html
Sent from the Tapestry - User mailing list archive at Nab
I have to agree with Filip and I'll state it a bit more strongly: if you
are using onActivate for access control your app will suffer from
significant maintenance issues that will only get worse and more complex
with each page you add, and even nastier if your access control logic's
requirements ev
That's a good point Filters...I'll think about it, unfortunatelly for me I've
been influenced by many samples where onactivate is used for the purpose I
do, in fact I begin the issue saying that I can't full understand the page
cicle model. From the semantical point of view onActivate seems to imp
Hi,
The documentation clearly states that they will all be called as well as
the order they will be called in.
I don't check login etc. in onActivate, I use request filters for that.
But it's your app, not mine, so do as you please. :)
-Filip
On 2008-06-07 12:58, maxthesecond wrote:
Well,
Well, in my case when I have two or more onActivate handlers I've seen all
them called one after the other wich of course is not what I expect ,besides
the fact of having just one onActivate frees you of having to check common
isues like for example loggin , or administrative rights in many places
Hi,
I frequently have multiple onActivate methods as well. Tapestry will
look at the context and see how many parameters there are - let's say
there are n parameters. It will then call the method with n parameters -
or if none can be found, the one with n-1 parameters, then n-2
parameters and
Renat Zubairov wrote:
>
> Why would you need to have multiple parameters in onActivate? Are you
> considering using Encoder?
> http://tapestry.apache.org/tapestry5/apidocs/org/apache/tapestry/PrimaryKeyEncoder.html
>
Well, it is simply an Update/Create page of a detail element belonging to a
