Thanks, Martin. I ended up using WebApplication#newAjaxRequestTarget() approach because AjaxFeedbackPanelUpdater approach requires me to know all forms that can be displayed in the page ahead of time and modify their onSubmit code.
On Mon, Aug 20, 2012 at 3:01 PM, Martin Grigorov <mgrigo...@apache.org> wrote: > https://github.com/procrastinativedeveloper/ToolsClasses/blob/master/src/main/java/com/utils/wicket/ajax/AjaxFeedbackPanelUpdater.java > is all you need. > > in your AjaxButton#onSubmit(ART target) { > target.addListener(new AjaxFeedbackPanelUpdater()); > } > > Or override WebApplication#newAjaxRequestTarget() and add it for each > and every ART. > > On Mon, Aug 20, 2012 at 11:56 PM, Alec Swan <alecs...@gmail.com> wrote: >> IRequestCycleListener was added in 1.5.x. Is there anything else I can >> do in 1.4.x? >> >> On Mon, Aug 20, 2012 at 12:15 PM, Bertrand Guay-Paquet >> <ber...@step.polymtl.ca> wrote: >>> Hi, >>> >>> I haven't used 1.4 much so I'm not sure it exists there. Maybe you could add >>> a IRequestCycleListener to your app via getRequestCycleListeners() which >>> adds the feedback panel in onRequestHandlerResolved? In that method, check >>> if the handler type is an AjaxRequestTarget and add your feedback panel to >>> it. >>> >>> >>> On 20/08/2012 11:45 AM, Alec Swan wrote: >>>> >>>> It seems that I cannot access ART from the component that is not >>>> updated by that ART because that component is not rendered during the >>>> lifecycle of that ART. >>>> >>>> Here is the problem description: >>>> >>>> 1. A page is rendered with a feedback panel and a form >>>> 2. The form is later submitted via AJAX and does not add any components to >>>> ART >>>> >>>> How in step 1 can I make sure that feedback panel is updated when form >>>> is submitted in step 2? >>>> >>>> Thanks, >>>> >>>> Alec >>>> >>>> On Mon, Aug 20, 2012 at 9:38 AM, Tibor Blénessy <blene...@gmail.com> >>>> wrote: >>>>> >>>>> You can access current ART associated with request by calling static >>>>> AjaxRequestTarget.get() >>>>> >>>>> Tibor >>>>> >>>>> On Mon, Aug 20, 2012 at 5:10 PM, Alec Swan <alecs...@gmail.com> wrote: >>>>>> >>>>>> Thoughts, anybody? >>>>>> >>>>>> On Sun, Aug 19, 2012 at 1:07 PM, Alec Swan <alecs...@gmail.com> wrote: >>>>>>> >>>>>>> The main problem I am facing is that in Wicket 1.4.x I can't figure >>>>>>> out how to access ART from the component that was not added to this >>>>>>> ART, e.g. during ajax form submission. >>>>>>> >>>>>>> I tried to add AjaxFormSubmitBehavior to every Form child of the page >>>>>>> but that overrode those form ajax-submit functionality and basically >>>>>>> broke them all. Now I am thinking about adding an onclick behavior >>>>>>> which will add my component to ART to every AjaxSubmitLink child of >>>>>>> the page. But this seems to be pretty ugly. >>>>>>> >>>>>>> Thoughts? >>>>>>> >>>>>>> Thanks, >>>>>>> >>>>>>> Ale >>>>>>> >>>>>>> On Fri, Aug 17, 2012 at 4:22 PM, Alec Swan <alecs...@gmail.com> wrote: >>>>>>>> >>>>>>>> Hello, >>>>>>>> >>>>>>>> Thank you for the link. I used your code to register an >>>>>>>> ART.addListener(new AjaxFeedbackPanelUpdater()) when the page is >>>>>>>> created, but it does not get called when the form is submitted and >>>>>>>> hence it never adds the FeedbackPanel to ART of form submission. >>>>>>>> >>>>>>>> Where should I add this listener? >>>>>>>> >>>>>>>> Thanks, >>>>>>>> >>>>>>>> Alec >>>>>>>> >>>>>>>> On Wed, Aug 15, 2012 at 4:14 PM, procrastinative.developer >>>>>>>> <procrastinative.develo...@gmail.com> wrote: >>>>>>>>> >>>>>>>>> Hello Alec, >>>>>>>>> Could you take a look on this: >>>>>>>>> >>>>>>>>> >>>>>>>>> https://github.com/procrastinativedeveloper/ToolsClasses/blob/master/src/main/java/com/utils/wicket/ajax/AjaxFeedbackPanelUpdater.java >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> View this message in context: >>>>>>>>> http://apache-wicket.1842946.n4.nabble.com/Add-page-feedback-to-every-AjaxRequestTarget-tp4651257p4651262.html >>>>>>>>> Sent from the Users forum mailing list archive at Nabble.com. >>>>>>>>> >>>>>>>>> --------------------------------------------------------------------- >>>>>>>>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >>>>>>>>> For additional commands, e-mail: users-h...@wicket.apache.org >>>>>>>>> >>>>>> --------------------------------------------------------------------- >>>>>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >>>>>> For additional commands, e-mail: users-h...@wicket.apache.org >>>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >>>>> For additional commands, e-mail: users-h...@wicket.apache.org >>>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >>>> For additional commands, e-mail: users-h...@wicket.apache.org >>>> >>>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >>> For additional commands, e-mail: users-h...@wicket.apache.org >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> > > > > -- > Martin Grigorov > jWeekend > Training, Consulting, Development > http://jWeekend.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
