Hi,
But it looks like that in this case the visitChilder is performed during
render, and it still won't find stuff added by autoAdd.
It is not a very robust design if the behaviour of autoAdd/visitChilder
would require some kind of component-hierarchy fine-tuning. This kind
of approach might work with static-kind-of applications, but at least
for us, the content in applications is very dynamic and interface like
IComponentResolver has been very handy.
Just a wild guess here - maybe the processing of IComponentResolver stuff
was done earlier in beta3 than in beta4. Not getting this fixed can be pretty
annoying
for us - we have a couple of hundreds of pages done with wicket which rely
on this.
We could of course try to step back in time with svn to see which change
has broken this, but I don't know how much sense it will make unless
developers are not going to admit that this is a problem.
Ari S.
----- Original Message -----
From: "Matej Knopp" <[EMAIL PROTECTED]>
To: <users@wicket.apache.org>
Sent: Wednesday, October 17, 2007 2:15 PM
Subject: Re: VisitChildren + IComponentResolver broken in beta 4?
It depends on when you call the visitChildren method. The idea is that
resolved components are on page only during page render. Otherwise
they are removed from page.
-Matej
On 10/17/07, Juha Alatalo <[EMAIL PROTECTED]> wrote:
In the JIRA issue following was commented:
"This doesn't seem to be a bug in Wicket. In fact, the bug was that it
worked before. ..."
This new "fix" is kind of a show stopper for us. What actually is the
idea of the componentResolver? Functions like visitChildren works for
normally added component. Shouldn't those functions work also for
components that are added using IComponentResolver as long as those are
visible?
- Juha
Juha Alatalo wrote:
> https://issues.apache.org/jira/browse/WICKET-1077
>
> - Juha
>
> Matej Knopp wrote:
>> Please create a JIRA entry and assign the example to it.
>>
>> Thanks.
>>
>> -Matej
>>
>> On 10/15/07, Juha Alatalo <[EMAIL PROTECTED]> wrote:
>>> Hi,
>>>
>>> If the components are added on the page using ComponentResolver,
>>> visitChildren() method seems to be working incorrectly. Created
>>> following example which works in beta 3 but not in beta 4.
>>>
>>> http://download.syncrontech.com/public/VisitChildrenExample.zip
>>>
>>> - Juha
>>>
>>> ---------------------------------------------------------------------
>>> 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]
>>
>
> ---------------------------------------------------------------------
> 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]
---------------------------------------------------------------------
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]
