Yes, the problems came with the work for component queueing. I guess at some point someone will be able to reproduce the problem in a quickstart and we will be able to debug and fix it. Until then use the better solution (EnclosureContainer).
Martin Grigorov Freelancer. Available for hire! Wicket Training and Consulting https://twitter.com/mtgrigorov On Wed, Jun 24, 2015 at 1:10 PM, Guillaume Smet <[email protected]> wrote: > On Wed, Jun 24, 2015 at 11:57 AM, Martin Grigorov <[email protected]> > wrote: > > > EnclosureContainer FTW! > > > > P.S. I know the above is not very useful but I'm preaching against > > (Inline)Enclosure for few years now :-) > > > > Yeah, we only use it for very simple cases and we use EnclosureContainer > for complex cases but most of our cases are simple and we have hundreds of > them in our code. I would really prefer not having to get rid of them! > > There definitely is something fishy with enclosures and Wicket 7 as all our > issues with 7 are related to this. It worked quite well with 6. > > -- > Guillaume >
