On Thursday, June 18, 2015 04:01:43 PM Thiago H de Paula Figueiredo wrote:
> On Thu, 18 Jun 2015 14:47:51 -0300, Casey Link <ca...@outskirtslabs.com>
> wrote:
>
> > Hi again,
>
> Hi!
>
> > Request event 'remove' (on component mypackage/MyPage) was not
> > handled; you must provide a matching event handler method in the
> > component or in one of its containers.
> > Object onRemoveItem(Long id) {
> > Object onAddCourseModule(Long id) {
>
> Your event handlers are not matching the event names, so they don't
> actually handle the event. For a "remove" event, the event handler method
> name should be "onRemove" (or any method annotated with
> @OnEvent("remove"). The context of the EventLink must also match the event
> handler method parameters.
Ugh, sorry. That was a failure on my part to correctly write the example code
for the email.
I doubled checked, and the event handlers method names do match the EventLink
names, and the contexts do match.
Like I said, the event handlers work fine on a normal page refresh, but only
when I do the "add" and "remove" on the _same_ item without a page refresh in
between do I experience the issue.
I'm not sure what Tapestry is doing in the background, but do I need to do
something to tell Tapestry "Hey, there's a new possible item context that can
be called for the event!"?
What's strange, is I can "add" on A, then "remove" on B and it works (showing
that the handler exists and works!), but if I "remove" on A instead, it blows
up :\
Casey
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
