Hi.
Tapestry sets @ActivationRequestParameter fields on page instance before
calling "activate" handler. But it seems that this ordering is only
respected when both fields and activate handler are on the same page class,
but in subclass-superclass cases, superclass "activate" handler is called
prior to setting subclass @ActivationRequestParameter fields. Should I
register this as bug?
If anyone is interested in my case here it is:
I have a case where all my pages extend superclass where I have global
onActivate() handler with some common validation functionality, and also
allows subclass pages to add specific validation via overriding method,
something like this:
# page superclass code:
private Object onActivate(Object[] context) {
..some global validation logic ...
return doPageSpecificValidation(context);
}
protected Object doPageSpecificValidation(Object[] context) {
// ... empty by default, override for some specific page validation
logic
return null;
}
So, in my subclass page I wanted to override "doPageSpecificValidation"
method and use some @ActivationRequestParameter field from that subclass,
but alas, these are not set yet.
BTW, request filters can sometimes be quite cumbersome for achieving the
same goal (validation), so that's why I use subclassing.
Regards,
Vjeran
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
