Re: [Wicket-user] IBehavior#rendered() is called twice when a component that has that behavior is rendered via AJAX.

Okay. For 2.0 we can have detach(Component component).. or maybe componentDetached(Component component), and we can call the cleanup() from there. I wouldn't mind. But what to do for 1.2? One solution would be to call cleanup() from AbstractBehavior.detachModel(), the only thing that bothers me

Re: [Wicket-user] IBehavior#rendered() is called twice when a component that has that behavior is rendered via AJAX.

im not sure why we have detachModel() as opposed to detach() maybe we should just add detach(), it seems logical to me-IgorOn 10/17/06, Matej Knopp <[EMAIL PROTECTED]> wrote:Well, as far as I can see there's only detachModels in IBehavior. Is this the place?-MatejIgor Vaynberg wrote:> why not do t

Re: [Wicket-user] IBehavior#rendered() is called twice when a component that has that behavior is rendered via AJAX.

Well, as far as I can see there's only detachModels in IBehavior. Is this the place? -Matej Igor Vaynberg wrote: > why not do the cleanup in detach() ? > > -Igor > > On 10/17/06, *Matej Knopp* <[EMAIL PROTECTED] > > wrote: > > Well, it seems like a bug, the ques

Re: [Wicket-user] IBehavior#rendered() is called twice when a component that has that behavior is rendered via AJAX.

why not do the cleanup in detach() ?-IgorOn 10/17/06, Matej Knopp <[EMAIL PROTECTED]> wrote: Well, it seems like a bug, the question is how to fix it?The problem is that rendered() should be called after component isrendered. But we do call it even after header is rendered, because weneed to do som

Re: [Wicket-user] IBehavior#rendered() is called twice when a component that has that behavior is rendered via AJAX.

Well, it seems like a bug, the question is how to fix it? The problem is that rendered() should be called after component is rendered. But we do call it even after header is rendered, because we need to do some cleanup there. So for 2.0 I think we need something like IBehavior.cleanup() - where

Re: [Wicket-user] IBehavior#rendered() is called twice when a component that has that behavior is rendered via AJAX.

yes its a bug, please file it-igorOn 10/16/06, Caleb Land <[EMAIL PROTECTED]> wrote: On 10/16/06, Caleb Land < [EMAIL PROTECTED]> wrote: I'm using Wicket 2.0The IBehavior#rendered() method is called twice when a component that has that behavior is rendered via AJAX.  When rendering the component t

Re: [Wicket-user] IBehavior#rendered() is called twice when a component that has that behavior is rendered via AJAX.

On 10/16/06, Caleb Land <[EMAIL PROTECTED]> wrote: I'm using Wicket 2.0The IBehavior#rendered() method is called twice when a component that has that behavior is rendered via AJAX.  When rendering the component though the normal process (not ajax) it is only called once. Here are the two places it'

[Wicket-user] IBehavior#rendered() is called twice when a component that has that behavior is rendered via AJAX.

I'm using Wicket 2.0The IBehavior#rendered() method is called twice when a component that has that behavior is rendered via AJAX.  When rendering the component though the normal process (not ajax) it is only called once. Here are the two places it's getting called:The AjaxRequestTarget#respondCompo