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]
