Our application periodically gets these errors, where wicket say the component 
could not be found.

Take this example.

1) There is a delete link on the page.
2) The user clicks the delete button
3) They get the "delete button" component not found error.

The intriguing part is that the item is actually deleted.

This makes me think it could be a double click error.
i.e. the item is delete and the js has another click call queued up but the 
page changes before it comes through.

Is this possible? If so how do I prevent it?



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Reply via email to