It seems it is just me who prefers to avoid the usage of auto-components (i.e. magic) in my projects.
I'm going to link all open tickets with this problem and close all but one of them. On Tue, Jun 18, 2013 at 9:54 AM, martin.dilger <martin.dil...@googlemail.com > wrote: > Just to give my 3 pens, > I agree with Igor too, <wicket:enclosure/> is really handy in most cases, I > would strongly disagree to remove it. We use it a lot in our projects and > rarely have problems with it. And if I think of the impact it would have > for > our projects to refactor everything to use EnclosureContainer instead... > > The Problem <wicket:enclosure/> solves is not something I want to be > reflected in code, it´s far more handy to just handle that in the markup. > If > there are problems with the <wicket:enclosure/>-Tag, we should solve them. > > > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Deprecating-wicket-enclosure-tp4659572p4659578.html > Sent from the Forum for Wicket Core developers mailing list archive at > Nabble.com. >
