On Tue, Jul 23, 2013 at 6:44 PM, Andrew Geery <[email protected]>wrote:
> Just to make sure I'm understanding this correctly, it should be enough to
> simply override updateAjaxAttributes on AjaxButton and specify a channel
> that does not have ACTIVE behavior, like this:
>
> @Override
> protected void updateAjaxAttributes(AjaxRequestAttributes
> attributes) {
> super.updateAjaxAttributes(attributes);
> attributes.setChannel(new AjaxChannel("MyChannel",
> AjaxChannel.Type.DROP));
> }
>
The default channel type is QUEUE, so it should work by default.
I cannot say why it doesn't in your case.
>
> Thanks
> Andrew
>
>
> On Tue, Jul 23, 2013 at 3:46 AM, Martin Grigorov <[email protected]
> >wrote:
>
> > HI,
> >
> > Unless you use AjaxChannel.ACTIVE on the AjaxButton you should not
> > experience this behavior.
> > It should work exactly as you expect it.
> > Try to put some debug statements with an AjaxCallListener - print to
> > console in onBefore() and onBeforeSend(). Add this listener to both
> > components - the field and the button.
> >
> >
> > On Tue, Jul 23, 2013 at 5:03 AM, Andrew Geery <[email protected]
> > >wrote:
> >
> > > I have a form that is submitted with an AjaxButton. One of the fields
> in
> > > the form uses an AjaxFormComponentUpdatingBehavior to update the
> > > server-side state when a value in the field changes (i.e., it fires
> > > onchange). If the user changes the field with
> > > the AjaxFormComponentUpdatingBehavior associated with it and then
> clicks
> > > the submit button, the behavior updates the field server side, but the
> > ajax
> > > button doesn't submit the form. The user has to click the submit
> button
> > a
> > > second time to submit the form. Is there a way to get the two ajax
> > > behaviors to fire consecutively, rather than forcing the user to click
> > > twice?
> > >
> > > Thanks
> > > Andrew
> > >
> >
>
