sorry, i try to be more specific. after moving to wicket 6.10.0, it fails in
two different cases:

case 1: when adding this behavior:

autoComplete.add(new AjaxFormComponentUpdatingBehavior("onKeyUp") {
        protected void onUpdate(final AjaxRequestTarget target) {

without it, it works fine. this code works fine up to wicket 6.9.1.

case 2: no behaviors at all, still to be determined the problematic point;
just multiple auto-completes on the view and wicket-ajax-debug complaining
many times with output "ERROR: Cannot find element with id: null" (not clear
yet it this has to be with the problem in the auto-complete, but these
errors where not happening before in wicket 6.9.1).


View this message in context:
Sent from the Users forum mailing list archive at

To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to