Hi!
Is it a bug that wicket requires a field which is in an enclosure
which is then not visible?
wicket:enclosure child=switch
select wicket:id=combo/select !-- this will be required (if
it is required) even though the switch is hidden --
wicket:container wicket:id=switch/
/wicket:enclosure
no it is not a bug. your hierarchy has to match the markup even if
things are not visible.
-igor
On Thu, May 7, 2009 at 4:19 AM, Martin Makundi
martin.maku...@koodaripalvelut.com wrote:
Hi!
Is it a bug that wicket requires a field which is in an enclosure
which is then not visible?
no it is not a bug. your hierarchy has to match the markup even if
things are not visible.
That was pseudocode.. don't mind the hierarchy. It's all about the
enclosure only. So I gather it is a bug. It does not throw exception,
the problem is just that an element hidden (only via enclosure) is
ah, that is different and that should be fixed in latest versions i believe.
-igor
On Thu, May 7, 2009 at 9:26 AM, Martin Makundi
martin.maku...@koodaripalvelut.com wrote:
no it is not a bug. your hierarchy has to match the markup even if
things are not visible.
That was pseudocode.. don't
