On Wed, Feb 13, 2013 at 12:12 PM, Thiago H de Paula Figueiredo < [email protected]> wrote:
> The issue you should look at is: >> https://issues.apache.org/**jira/browse/TAP5-2070<https://issues.apache.org/jira/browse/TAP5-2070> >> > > Could you please describe the patch logic instead of just linking to it? > C'mon Thiago, the patch is not that long and the logic is easy. BTW If it's configured, the framework would check the correct (exact in term of number and type of parameters) activate method and if not found it will answer with a 404. The 3 types of special parameters (List, Object[] and EventContext) are handled as they are now, that's the part I like less. PageActivator and the logic for matching events inside ComponentEvent do the rest. Cheers -- Massimo
