It seems like 1.4.4 will throw the error, as you say
"for *any* missing child declared inside enclosure's markup"
but unfortunately it appears to throw it even if the child is available
by a component resolver.
Version 1.4.2 does not throw an error if the child is found via the
component resolver mechanism but 1.4.5 does (not sure about intermediate
versions 1.4.3 & 1.4.4), seemingly breaking the fix that was made in
1.4.2 that allowed the component resolver mechanism to work really well
within enclosures.
> >>>>> i think you guys misunderstand.
> >>>>>
> >>>>> i believe what we are talking about here is the requirement for
> >>>>> presence of components *other* then the component specified by
> >>>>> enclosure's child attribute.
> >>>>>
> >>>>> essentially if i do this:
> >>>>>
> >>>>> add(new webmarkupcontainer("container").setvisible(false));
> >>>>> and have this in my markup:
> >>>>> <div wicket:id="container"><div wicket:id="foo"/></div>
> >>>>>
> >>>>> wicket will not throw an error even though i never added the
"foo"
> >>>>> component to my component hierarchy because as soon as it
> >>>>> determins
> >>>>> that the container div is not visible it will skip over until
the
> >>>>> closing tag.
> >>>>>
> >>>>> the enclosures, however, as of 1.4.4 *will* throw an error for
> >>>>> *any*
> >>>>> missing child declared inside enclosure's markup *even though*
the
> >>>>> enclosure has been determined as hidden.
> >>>>>
> >>>>> hope this clears it up somewhat
> >>>>>
> >>>>> -igor
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
