Oh, that sucks. That's VERY misleading because I can override respond and I
have the AjaxRequestTarget or call AjaxRequestTarget.get() and get a valid
object. Doesn't really make much sense that a different pipeline would be
used. I guess I'll have to come up with a better solution using
WicketAjaxEvent.
Thanks for your help!
On Fri, Mar 7, 2008 at 10:57 PM, Matej Knopp <[EMAIL PROTECTED]> wrote:
> The autocomplete component doesn't use the wicket ajax pipeline so
> that ajaxrequesttarget methods will not work for request invoked by
> the autocomplete behavior.
>
> -Matej
>
> On Sat, Mar 8, 2008 at 4:50 AM, Andrew Berman <[EMAIL PROTECTED]> wrote:
> > Hello,
> >
> > If I have the following code:
> >
> > textField.add(new AbstractAutoCompleteBehavior() {
> > /**
> > *
> > */
> > private static final long serialVersionUID = 1L;
> >
> > @Override
> > protected void onRequest(final String input,
> > RequestCycle requestCycle) {
> > }
> >
> > @Override
> > protected void respond(AjaxRequestTarget target) {
> > target.appendJavascript("alert(\"hello\");");
> > }
> > });
> >
> > When the page renders, the textfield is calling this event and I see
> the
> > response in the Wicket debug box, but the response is never being
> parsed and
> > the alert never shows up. Am I missing something here? I tested
> using an
> > AjaxEventBehavior with onkeypress and it works great. The only problem
> is
> > that I have no way of getting the text typed into the text field, which
> is
> > why I used the auto complete stuff. Any thoughts?
> >
> > Thanks for your help!
> >
>
>
>
> --
> Resizable and reorderable grid components.
> http://www.inmethod.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
