You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@wicket.apache.org by The Genuiini <ge...@dnainternet.net> on 2012/02/09 08:35:07 UTC

Again Inline Enclosure does not ... wicket:extend and wicket:child and workaround

Hi again,

has anyone tested the functionality of workaround given in https://issues.apache.org/jira/browse/WICKET-3947? It helps with one bug, but is it sure it not create other problems?

BR. T.G.

Re: Again Inline Enclosure does not ... wicket:extend and wicket:child and workaround

Posted by Martin Grigorov <mg...@apache.org>.

Hi,

I'd recommend you to not use InlineEnclosure if it causes you troubles.
Just introduce WebMarkupContainer instead and override its
onConfigure() to set its visibility depending on its child visibility.
Additionally you'll have to update the WMC in Ajax requests when the
child has to be updated but it will be more reliable in long term.

On Thu, Feb 9, 2012 at 9:35 AM, The Genuiini <ge...@dnainternet.net> wrote:
> Hi again,
>
> has anyone tested the functionality of workaround given in https://issues.apache.org/jira/browse/WICKET-3947? It helps with one bug, but is it sure it not create other problems?
>
> BR. T.G.
>
>
>

-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com