What problem exactly would this solve? Detaching logic is not exactly trivial and I fail to see any benefit in complicating it with Component itself being detachable.
-Matej On Wed, May 6, 2009 at 2:19 PM, Martijn Dashorst <[email protected]> wrote: > It is also trivial to implement a stop for endless recursion. Still > fail to see the problem. > > Martijn > > On Wed, May 6, 2009 at 2:10 PM, Frank van Lankvelt > <[email protected]> wrote: >> could it be so that you can use a Component as a model object? E.g. in a >> Model or CompoundPropertyModel? >> A detachable Component would trivially lead to recursion in this case. >> >> cheers, Frank >> >> On Wed, May 6, 2009 at 12:28 PM, Martijn Dashorst < >> [email protected]> wrote: >> >>> I always assumed that Component implements IDetachable but today found >>> out that it doesn't. >>> >>> A Component clearly is detachable, it has a detach() method. Is there >>> some reason why Component shouldn't implement IDetachable? >>> >>> Martijn >>> >> > > > > -- > Become a Wicket expert, learn from the best: http://wicketinaction.com > Apache Wicket 1.3.5 is released > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. >
