Hi Thiago,

unfortunately the context is not empty. I checked the request URL in chrome
dev-tools and it contains the context parameters. I debugged the
in AjaxComponentEventRequestHandler.handle the lines

boolean handled = element
  .triggerContextEvent(parameters.getEventType(),
parameters.getEventContext(), callback);

if (!handled)
 ...

the parameters.getEventContext() does contain my specified context
parameters, but
 the eventhandler is not called.

I also created a new tapestry project with almost the same approach and it
works.
Now i'm even more confused ;), because it should work.

I quess the problem of our project is somekind of side effect(s). But i
don't know
how to find them


Kind regards
Diego


On Tue, Oct 20, 2015 at 4:16 PM, Diego Socaceti <socac...@gmail.com> wrote:

> Hi Thiago,
>
> unfortunately the context is not empty. I checked the request URL in chrome
> dev-tools and it contains the context parameters. I debugged the
> in AjaxComponentEventRequestHandler.handle the lines
>
> boolean handled = element
>   .triggerContextEvent(parameters.getEventType(),
> parameters.getEventContext(), callback);
>
> if (!handled)
> throw new TapestryException(String.format("Request event '%s' (on
> component %s) was not handled; you must provide a matching event handler
> method in the component or in one of its containers.",
> parameters.getEventType(), element.getCompleteId()), element,
>                     null);
>
>
>
> On Tue, Oct 20, 2015 at 2:55 PM, Thiago H de Paula Figueiredo <
> thiag...@gmail.com> wrote:
>
>> On Tue, 20 Oct 2015 06:30:34 -0200, Diego Socaceti <socac...@gmail.com>
>> wrote:
>>
>> Hi all,
>>>
>>
>> Hi!
>>
>> The event handler is not called, but an tapestry exception is thrown
>>>    "Request event 'autosearchinputchanged' (on component
>>> report/Detail:formcontent.mintautocompletesearch.autosearchfield) was not
>>> handled; you must provide a matching event handler method in the
>>> component or in one of its containers."
>>>
>>
>> As the error message describes, Tapestry thinks there's no matching event
>> handler method.
>>
>> But i don't understand, what i did wrong. I'm using tapestry-5.4-beta-37.
>>> Is it wrong to use final EventContext eventContext and RequestParameter
>>> together?
>>>
>>
>> It shouldn't be. By any chance your context is null or empty?
>>
>> --
>> Thiago H. de Paula Figueiredo
>> Tapestry, Java and Hibernate consultant and developer
>> http://machina.com.br
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
>> For additional commands, e-mail: users-h...@tapestry.apache.org
>>
>>
>

Reply via email to