i thought that was how it worked...they should be removed after render.
unless there is some weird case where autocomponents participate in event
handling, but i dont think that shuold happen...
-igor
On 10/3/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> auto components like the header container or auto links leak now in to the
> page
> because all those auto components ids are appended with the page auto
> index
> This is quite a problem for the current autoAdd method implementation:
>
>
> if (get(component.getId()) != null){
> this.remove(component);
> }
>
> that is a bit of a problem if the id of the auto add component is not
> stable
> over request
>
> So the header component is constantly added over and over again and never
> being removed
>
> I fixed this by removing the above code and immedianlty after calling
> render
> just remove the component again.
>
> Is this a problem yes or no? All unit test run fine. But i don't know why
> we
> didn't do that at the first place because that seems to be like the right
> implementation any way.
>
> johan
>
