On Mon, Jan 28, 2013 at 6:12 AM, Massimo Lusetti <mluse...@gmail.com> wrote:
> On Mon, Jan 28, 2013 at 3:04 PM, Thiago H de Paula Figueiredo < > thiag...@gmail.com> wrote: > I think Steve's code assumes that, if a page has a method handling the > > activate event, no matter its parameters or lack thereof, then the page > > handles the context itself, is responsible for taking any actions related > > to it and Tapestry shouldn't do any redirection for itself. I think > that's > > a very reasonable assumption. No hoops to jump through, just good > > documentation. > I would go further, if a page define one or more onActivate methods it > clearly states what activation contexts (one or more) it accepts and which > don't. So that information can be used to extract information about which > URL is correct and which not. > But even without that an intermediate solution is more then acceptable and > I think is due. > Sure, I'll rephrase my "battle worth fighting" to "case worth arguing". As evident from responses though, it's not easy to pick a winner from the proposed half solutions. I think it's going to come down to being able to somehow handle 404s with onActivate(EventContext) present. If we could at least tell the max number of accepted context parameters that'd likely address a large number of cases. I agree with Massimo though, a completely new annotation just for this doesn't sound very lucrative. Perhaps a new attribute to @OnEvent - although I don't know if it can be as useful for other than activate event types. Kalle
