The Genuiini wrote
>
> Hi again,
>
> I am still very interested in this inline enclosure problem. Really, there
> is no proper fix for it yet? What makes it complicated to resolve? I have
> read and browsed those java codes, they are quite easy locate via list of
> changes in WICKET-3422 ("Simplified visibility control of Enclosures in
> Ajax requests"), but of course the system is not trivial...
>
> By the way, to catch the picture, the 'variation.zip' in WICKET-3947 is
> good starting point! I have ported it to wicket 1.4.19 and added also
> code&page where workaround have been used.
>
> BR T.G.
>
I put a small patch in JIRA. It is more a workaround than a real fix. It
should give some insight too.
Real problem is that InlineEnclosure is a sort of hybrid between auto and
non-auto component. For InlineEnclosure to be able to function it would
have to be a non auto component with state. This kind of defeats the
purpose of original feature. I tried to keep the patch limited to
InlineEnclosure. Reason for this is to limit any more special cases in the
wicket core.
regards Arni
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Current-state-of-art-Inline-Enclosure-does-not-work-properly-when-using-wicket-extend-and-wicket-chi-tp4361670p4411419.html
Sent from the Forum for Wicket Core developers mailing list archive at
Nabble.com.
