fine by me -igor
On Fri, Mar 28, 2008 at 6:55 AM, Johan Compagner <[EMAIL PROTECTED]> wrote: > hmm > So the problem is that AjaxRequestTargets gets a component that is already > removed > at the time it wants to render it. > > What is the harm in fixing that? That it just ignores such components (maybe > with a warning in the log) > > johan > > > > > On Fri, Mar 28, 2008 at 2:07 PM, Federico Fanton <[EMAIL PROTECTED]> wrote: > > > On Fri, 28 Mar 2008 12:56:44 +0100 > > "Martijn Dashorst" <[EMAIL PROTECTED]> wrote: > > > > > You could replace the original ajax request target with a new one: > > > > > > AjaxRequestTarget newAjax = new AjaxRequestTarget(getPage()); > > > getRequestCycle().setRequestTarget(newAjax); > > > newAjax.addComponent(table); > > > > I see, but I can't confidently replace the target that way, since there > > could be _other_ components being updated, unrelated to the table.. I'm > > sorry, I wasn't clear previously :( > > Would it be a Bad Thing to add a protected > > AjaxRequestTarget.getMarkupToIdComponents() ? > > Many thanks for your time! > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
