On Mon, Jan 28, 2013 at 3:15 AM, Kalle Korhonen
<kalle.o.korho...@gmail.com>wrote:
>
> And what about onActivate(EventContext context)? If you could limit the
> number of accepted parameters(an annotation parameter perhaps?), then that
> might work. However, I'm often too much of a pragmatist to try to convince
> Howard of what the framework should or shouldn't do. I'm usually happy with
> the inherent "change it if you don't like it" flexibility of the framework.
> Perhaps this is a battle worth fighting though and I agree that the
> framework should have a built-in, low resource impact way of dealing with
> 404s.
>
There's no battle to fight nor win here.
BTW I want the same behavior for what is the current Index page and all the
others, for instance if I've a page called MyPage without an activation
context and I call the URL /mypage/some/activation/context this should
produce a 404 the same is valid if the page has an activation context like:
onActivate(Long longNumber)
{
...
}
and I call the URL /mypage/seeya ... I should call /mypage/1234567890
Objections? What other thinks? ...
Cheers
--
Massimo
